On 03/05/2011 08:27 PM, David C. Rankin wrote:

On 03/05/2011 08:04 PM, Baho Utot wrote:

...

I am trying to build kdebase

SVN checkout of revision 1223901 -- Complete

, which resluts in this error

[ 48%] Building CXX object kioslave/man/CMakeFiles/kio_man-module.dir/kio_man.cpp.o Linking CXX shared module kio_man.so [ 48%] Built target kio_man-module [ 48%] Generating kmanpart.moc Scanning dependencies of target libkmanpart-module [ 48%] Building CXX object kioslave/man/CMakeFiles/libkmanpart-module.dir/kmanpart.cpp.o Linking CXX shared module libkmanpart.so [ 48%] Built target libkmanpart-module [ 48%] Generating mount_xdr.c file `mount_xdr.c' already exists and may be overwritten make[2]: *** [kioslave/nfs/mount_xdr.c] Error 1 make[1]: *** [kioslave/nfs/CMakeFiles/kio_nfs-module.dir/all] Error 2 make: *** [all] Error 2 Aborting...

Baho,

2 thoughts:

(1) Try rebuilding kdelibs and then kdebase?

(2) Try deleting the trinity-kdebase/src directory and forcing a new download (or you could try 'svn cleanup' in trinity-kdebase/src/kdebase?

I built kdebase yesterday and didn't have a problem. I'll go try it again and let you know. If you are building in an archroot, this is the type of dependency/module issue I ran into. Give me 15 minutes and I'll report back.

Are you on i686 or x86_64. (IIRC it's i686)

Darn,

I don't know what it is. I just tried rebuilding dbus-qt3 and I got:

then mv -f ".deps/connection.Tpo" ".deps/connection.Plo"; else rm -f ".deps/connection.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/opt/qt/include -DDBUS_API_SUBJECT_TO_CHANGE=1 -march=x86-64 -mtune=generic -O2 -pipe -MT connection.lo -MD -MP -MF .deps/connection.Tpo -c ../qt3/connection.cpp -fPIC -DPIC -o .libs/connection.o In file included from ../qt3/connection.cpp:169:0: ../qt3/connection.moc:12:2: error: #error "The header file 'connection.h' doesn't include <QObject>." ../qt3/connection.moc:19:1: error: 'QT_BEGIN_MOC_NAMESPACE' does not name a type ../qt3/connection.moc:53:39: error: 'const QMetaObject DBusQt::Connection::staticMetaObject' is not a static member of 'class DBusQt::Connection' ../qt3/connection.moc:53:39: error: variable 'const QMetaObject DBusQt::Connection::staticMetaObject' has initializer but incomplete type ../qt3/connection.moc:55:7: error: 'qt_meta_data_DBusQt__Connection' was not declared in this scope ../qt3/connection.moc:62:20: error: prototype for 'const QMetaObject* DBusQt::Connection::metaObject() const' does not match any in class 'DBusQt::Connection' ../qt3/connection.h:40:5: error: candidate is: virtual QMetaObject* DBusQt::Connection::metaObject() const ../qt3/connection.moc:67:58: error: no 'void* DBusQt::Connection::qt_metacast(const char*)' member function declared in class 'DBusQt::Connection' ../qt3/connection.moc:75:50: error: 'int DBusQt::Connection::qt_metacall' is not a static member of 'class DBusQt::Connection' ../qt3/connection.moc:75:37: error: incomplete type 'QMetaObject' used in nested name specifier ../qt3/connection.moc:75:59: error: expected primary-expression before 'int' ../qt3/connection.moc:75:68: error: expected primary-expression before 'void' ../qt3/connection.moc:75:77: error: initializer expression list treated as compound expression ../qt3/connection.moc:76:1: error: expected ',' or ';' before '{' token make[2]: *** [connection.lo] Error 1 make[2]: Leaving directory `/home/david/tbld/dbus-qt3/src/dbus-qt3-0.62/qt3' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/david/tbld/dbus-qt3/src/dbus-qt3-0.62' make: *** [all] Error 2 Aborting...

Something is going on?

Serghei -- what did you break :)

On 03/05/2011 10:01 PM, David C. Rankin wrote:

On 03/05/2011 08:27 PM, David C. Rankin wrote:

...

On 03/05/2011 08:04 PM, Baho Utot wrote:

...

I am trying to build kdebase

SVN checkout of revision 1223901 -- Complete

, which resluts in this error

[ 48%] Building CXX object kioslave/man/CMakeFiles/kio_man-module.dir/kio_man.cpp.o Linking CXX shared module kio_man.so [ 48%] Built target kio_man-module [ 48%] Generating kmanpart.moc Scanning dependencies of target libkmanpart-module [ 48%] Building CXX object kioslave/man/CMakeFiles/libkmanpart-module.dir/kmanpart.cpp.o Linking CXX shared module libkmanpart.so [ 48%] Built target libkmanpart-module [ 48%] Generating mount_xdr.c file `mount_xdr.c' already exists and may be overwritten make[2]: *** [kioslave/nfs/mount_xdr.c] Error 1 make[1]: *** [kioslave/nfs/CMakeFiles/kio_nfs-module.dir/all] Error 2 make: *** [all] Error 2 Aborting...

Baho,

2 thoughts:

(1) Try rebuilding kdelibs and then kdebase?

(2) Try deleting the trinity-kdebase/src directory and forcing a new download (or you could try 'svn cleanup' in trinity-kdebase/src/kdebase?

I built kdebase yesterday and didn't have a problem. I'll go try it again and

let you know. If you are building in an archroot, this is the type of dependency/module issue I ran into. Give me 15 minutes and I'll report back.

Are you on i686 or x86_64. (IIRC it's i686)

Darn,

I don't know what it is. I just tried rebuilding dbus-qt3 and I got:

     then mv -f ".deps/connection.Tpo" ".deps/connection.Plo"; else rm -f

".deps/connection.Tpo"; exit 1; fi g++ -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -I/opt/qt/include -DDBUS_API_SUBJECT_TO_CHANGE=1 -march=x86-64 -mtune=generic -O2 -pipe -MT connection.lo -MD -MP -MF .deps/connection.Tpo -c ../qt3/connection.cpp -fPIC -DPIC -o .libs/connection.o In file included from ../qt3/connection.cpp:169:0: ../qt3/connection.moc:12:2: error: #error "The header file 'connection.h' doesn't include<QObject>." ../qt3/connection.moc:19:1: error: 'QT_BEGIN_MOC_NAMESPACE' does not name a type ../qt3/connection.moc:53:39: error: 'const QMetaObject DBusQt::Connection::staticMetaObject' is not a static member of 'class DBusQt::Connection' ../qt3/connection.moc:53:39: error: variable 'const QMetaObject DBusQt::Connection::staticMetaObject' has initializer but incomplete type ../qt3/connection.moc:55:7: error: 'qt_meta_data_DBusQt__Connection' was not declared in this scope ../qt3/connection.moc:62:20: error: prototype for 'const QMetaObject* DBusQt::Connection::metaObject() const' does not match any in class 'DBusQt::Connection' ../qt3/connection.h:40:5: error: candidate is: virtual QMetaObject* DBusQt::Connection::metaObject() const ../qt3/connection.moc:67:58: error: no 'void* DBusQt::Connection::qt_metacast(const char*)' member function declared in class 'DBusQt::Connection' ../qt3/connection.moc:75:50: error: 'int DBusQt::Connection::qt_metacall' is not a static member of 'class DBusQt::Connection' ../qt3/connection.moc:75:37: error: incomplete type 'QMetaObject' used in nested name specifier ../qt3/connection.moc:75:59: error: expected primary-expression before 'int' ../qt3/connection.moc:75:68: error: expected primary-expression before 'void' ../qt3/connection.moc:75:77: error: initializer expression list treated as compound expression ../qt3/connection.moc:76:1: error: expected ',' or ';' before '{' token make[2]: *** [connection.lo] Error 1 make[2]: Leaving directory `/home/david/tbld/dbus-qt3/src/dbus-qt3-0.62/qt3' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/david/tbld/dbus-qt3/src/dbus-qt3-0.62' make: *** [all] Error 2 Aborting...

Something is going on?

Serghei -- what did you break :)

I believe that the cmake build is regenerating kioslave/nfs/mount_xdr.c. [ 48%] Building CXX object kioslave/man/CMakeFiles/libkmanpart-module.dir/kmanpart.cpp.o Linking CXX shared module libkmanpart.so [ 48%] Built target libkmanpart-module [ 48%] Generating mount_xdr.c Scanning dependencies of target kio_nfs-module

The file is in the svn tree should it be ? What regenerates mount_xdr.c?

When I rm kioslave/nfs/mount_xdr.c in my build script (PKGBUILD) the build completes without error. Can someone if they have time look at this?

Thanks

On 03/06/2011 09:03 AM, Serghei Amelian wrote:

On Sunday 06 March 2011 16:33:32 Baho Utot wrote:

...

The file is in the svn tree should it be ? What regenerates mount_xdr.c?

When I rm kioslave/nfs/mount_xdr.c in my build script (PKGBUILD) the build completes without error. Can someone if they have time look at this?

As i recomended hundreds times, PLEASE use out-of-source mode. Otherwise you will run in strange troubles, mixing sources with generated files.

Baho,

Since Arch downloads (or svn updates) the code on each build, but then builds in the same 'src' dir, sometimes you just have to delete 'src' ($srcdir).

I keep a clean copy of the svn tree under ~/arch/trinity and I put the pkgbuilds under ~/tblds/<module name>. When I run into problems like this, I just:

sudo rm -r ~/tblds/kdebase/src/kdebase cp -a ~/arch/trinity/kdebase ~/tblds/kdebase/src/kdebase

Then do makepkg -s again.

Last night before going to bed, I kicked off 2 (i686 builds) and an (x86_64) build. All 3 built everything from tqtinterface -> kdegraphics without error.

On 03/06/2011 01:59 PM, Baho Utot wrote:

Won't work for me as I am building in a clean chroot. I always build in a clean chroot as to advoid unwanted dependencies The clean chroot gives me a set/group of packages that will work on any Arch system as the linked dependencies are controlled.... no surprises.

I am going to try a couple of other methods.

1. creating a build directory and building it from there
2. do a svn co, clean, update create source packages then build the binaries from that.

I should be able to rsync my build system and PKGBUILDs here shortly.

Great,

Let me know if you get them all working in the archroot. I ran into build problems like you are experiencing and I wasn't experienced enough with the archroot to figure them out so I switched to virtualbox. I haven't had any issues with virtualbox since.

The difficulty I had with archroot was -- it was just to damn difficult to tell what was installed from a package standpoint. I use pacman '-Q' and 'Qql' a lot to make sure I know what I have. Trying to do that through makechrootpkg was incredibly frustrating :)

I was able to get the first few packages done in the archroot (IIRC through arts), but then I lost the dependency battle. The cmake fixes in Trinity may have fixed that. If I get a few extra minutes tonight, I'll try the archroot again. That way we can compare notes.

If you have an extra 15G available on your drive, then I would also suggest you setup Arch in Virtualbox. You get the same clean environment, but you also have full control and all the tools you would normally use available.

I have put the package list for my vbox install (pacman -Q) on the server at:

http://www.3111skyline.com/dl/dt/trinity/arch/dev/vboxpkglist.txt

If you decide to go this route, here is my current disk usage in the VM (with full trinity source, separate build dirs (full) for qt3 -> kdegraphics and binaries with a full Trinity install:

[17:00 trinity-64:/opt/qt/include/tqt] # df -h Filesystem Size Used Avail Use% Mounted on udev 10M 160K 9.9M 2% /dev /dev/sda3 5.3G 3.2G 1.9G 63% / shm 509M 0 509M 0% /dev/shm /dev/sda4 9.9G 3.6G 5.9G 38% /home /dev/sda1 99M 21M 74M 22% /boot

On Sunday 06 March 2011 21:52:31 Baho Utot wrote: [...]

I am new around here so I am not versed in the build methods. If I understand what you are saying here is that I need to build it from a separate build directory with cmake "calling the source from there"

Yes, you right.