I've struggeled to compile trinity (tqinterface, kdelibs, kdebase) from scratch on my gentoo box using the latest svn. However I've got it compiled but I'm not quite sure if everything is good. Could you please post some kind of a howto, including dependencies issues. the obsolete documentation on the kde website won't do.
Trinity starts up fine however my problem is that the kdesktop seems to give up on X11 after starting up:
[Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007f8c58c39495 in raise () from /lib/libc.so.6 #6 0x00007f8c58c3a8c0 in abort () from /lib/libc.so.6 #7 0x00007f8c58c74ac7 in ?? () from /lib/libc.so.6 #8 0x00007f8c58c7a056 in ?? () from /lib/libc.so.6 #9 0x00007f8c58c7edec in free () from /lib/libc.so.6 #10 0x00007f8c5a56cf34 in ?? () from /usr/lib/libxcb.so.1 #11 0x00007f8c5a56d32c in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #12 0x00007f8c5a7c8beb in _XReply () from /usr/lib/libX11.so.6 #13 0x00007f8c5a7ad982 in XInternAtom () from /usr/lib/libX11.so.6 #14 0x00007f8c568a0e90 in KBackgroundManager::KBackgroundManager(QWidget*, KWinModule*) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #15 0x00007f8c568950df in KDesktop::initRoot() () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #16 0x00007f8c568946d1 in KDesktop::KDesktop(bool, bool) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #17 0x00007f8c568757b0 in kdemain () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #18 0x00007f8c56b278c8 in kdeinitmain () from /opt/kde-3.5.12/lib/kde3/kdesktop.so #19 0x0000000000408f17 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #20 0x000000000040a426 in handle_launcher_request(int) () #21 0x000000000040ad86 in handle_requests(int) () #22 0x000000000040c8da in main ()
Maybe a howto will point to my mistake. Otherwise any help would be very much apprechiated.
Best Regards Nicolas
Have you seen the wiki for developers?
http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild
Just a few minutes ago I added information to the wiki from my build notes.
Hi Darrell,
no I didn't since the wiki pages were mostly empty all the time ;). The multi core build issue advice is very helpful. I'll give it a try by tomorrow.
Thanks, Nico
-----Ursprüngliche Nachricht----- Von: "Darrell Anderson" humanreadable@yahoo.com Gesendet: Oct 1, 2010 10:21:53 PM An: trinity-devel@lists.pearsoncomputing.net Betreff: Re: [trinity-devel] question about building trinity from scratch
I've struggeled to compile trinity (tqinterface, kdelibs, kdebase) from scratch on my gentoo box using the latest svn. However I've got it compiled but I'm not quite sure if everything is good. Could you please post some kind of a howto, including dependencies issues. the obsolete documentation on the kde website won't do.
Trinity starts up fine however my problem is that the kdesktop seems to give up on X11 after starting up:
[Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007f8c58c39495 in raise () from /lib/libc.so.6 #6 0x00007f8c58c3a8c0 in abort () from /lib/libc.so.6 #7 0x00007f8c58c74ac7 in ?? () from /lib/libc.so.6 #8 0x00007f8c58c7a056 in ?? () from /lib/libc.so.6 #9 0x00007f8c58c7edec in free () from /lib/libc.so.6 #10 0x00007f8c5a56cf34 in ?? () from /usr/lib/libxcb.so.1 #11 0x00007f8c5a56d32c in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #12 0x00007f8c5a7c8beb in _XReply () from /usr/lib/libX11.so.6 #13 0x00007f8c5a7ad982 in XInternAtom () from /usr/lib/libX11.so.6 #14 0x00007f8c568a0e90 in KBackgroundManager::KBackgroundManager(QWidget*, KWinModule*) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #15 0x00007f8c568950df in KDesktop::initRoot() () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #16 0x00007f8c568946d1 in KDesktop::KDesktop(bool, bool) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #17 0x00007f8c568757b0 in kdemain () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #18 0x00007f8c56b278c8 in kdeinitmain () from /opt/kde-3.5.12/lib/kde3/kdesktop.so #19 0x0000000000408f17 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #20 0x000000000040a426 in handle_launcher_request(int) () #21 0x000000000040ad86 in handle_requests(int) () #22 0x000000000040c8da in main ()
Maybe a howto will point to my mistake. Otherwise any help would be very much apprechiated.
Best Regards Nicolas
Have you seen the wiki for developers?
http://trinity.pearsoncomputing.net/wiki/bin/view/Developers/HowToBuild
Just a few minutes ago I added information to the wiki from my build notes.
___________________________________________________________ GRATIS: Spider-Man 1-3 sowie 300 weitere Videos! Jetzt kostenlose Movie-FLAT freischalten! http://movieflat.web.de
hi,
first of all I'd like to say how much I apprechiate you folks taking up the task of maintaining and keeping kde 3.5x spirit alive! I love this desktop and would be very happy to see new versions without the kde4.x bloat overhead.
I've struggeled to compile trinity (tqinterface, kdelibs, kdebase) from scratch on my gentoo box using the latest svn. However I've got it compiled but I'm not quite sure if everything is good. Could you please post some kind of a howto, including dependencies issues. the obsolete documentation on the kde website won't do.
Trinity starts up fine however my problem is that the kdesktop seems to give up on X11 after starting up:
[Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007f8c58c39495 in raise () from /lib/libc.so.6 #6 0x00007f8c58c3a8c0 in abort () from /lib/libc.so.6 #7 0x00007f8c58c74ac7 in ?? () from /lib/libc.so.6 #8 0x00007f8c58c7a056 in ?? () from /lib/libc.so.6 #9 0x00007f8c58c7edec in free () from /lib/libc.so.6 #10 0x00007f8c5a56cf34 in ?? () from /usr/lib/libxcb.so.1 #11 0x00007f8c5a56d32c in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #12 0x00007f8c5a7c8beb in _XReply () from /usr/lib/libX11.so.6 #13 0x00007f8c5a7ad982 in XInternAtom () from /usr/lib/libX11.so.6 #14 0x00007f8c568a0e90 in KBackgroundManager::KBackgroundManager(QWidget*, KWinModule*) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #15 0x00007f8c568950df in KDesktop::initRoot() () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #16 0x00007f8c568946d1 in KDesktop::KDesktop(bool, bool) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #17 0x00007f8c568757b0 in kdemain () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #18 0x00007f8c56b278c8 in kdeinitmain () from /opt/kde-3.5.12/lib/kde3/kdesktop.so #19 0x0000000000408f17 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #20 0x000000000040a426 in handle_launcher_request(int) () #21 0x000000000040ad86 in handle_requests(int) () #22 0x000000000040c8da in main ()
Maybe a howto will point to my mistake. Otherwise any help would be very much apprechiated.
Best Regards Nicolas
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
I have seen this exact crash before, and though I had it fixed in SVN revision r1172215 (see http://trinity.pearsoncomputing.net/patches/ for more information on that commit).
I am uncertain as to what nofinal does; is it possible that the Gentoo build set the nofinal option?
There is a simple workaround available, but when implemented Trinity does not export the desktop background to X11.
Tim
Hi Timothy,
thanks for the hint. Explicitly adding --enable-final did the job.
My complete configuration:
./configure --disable-dnssd --without-arts --without-ssl --without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
I have no clue why the debug version fails on gentoo. Do you have any information if the gentoo devs are pulling trinity into there kde-sunset overlay? There has been some talk about this but nothing substancial to my knowledge.
Btw. the HAL dependency should explicitly be checked during the configure process. I got rid of HAL with the xorg 1.8 upgrade and didn't expect trinity needs it. Are you planning to make HAL mandatory in the future?
Nico
-----Ursprüngliche Nachricht----- Von: "Timothy Pearson" kb9vqf@pearsoncomputing.net Gesendet: Oct 2, 2010 12:04:20 AM An: trinity-devel@lists.pearsoncomputing.net Betreff: Re: [trinity-devel] question about building trinity from scratch
hi,
first of all I'd like to say how much I apprechiate you folks taking up the task of maintaining and keeping kde 3.5x spirit alive! I love this desktop and would be very happy to see new versions without the kde4.x bloat overhead.
I've struggeled to compile trinity (tqinterface, kdelibs, kdebase) from scratch on my gentoo box using the latest svn. However I've got it compiled but I'm not quite sure if everything is good. Could you please post some kind of a howto, including dependencies issues. the obsolete documentation on the kde website won't do.
Trinity starts up fine however my problem is that the kdesktop seems to give up on X11 after starting up:
[Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007f8c58c39495 in raise () from /lib/libc.so.6 #6 0x00007f8c58c3a8c0 in abort () from /lib/libc.so.6 #7 0x00007f8c58c74ac7 in ?? () from /lib/libc.so.6 #8 0x00007f8c58c7a056 in ?? () from /lib/libc.so.6 #9 0x00007f8c58c7edec in free () from /lib/libc.so.6 #10 0x00007f8c5a56cf34 in ?? () from /usr/lib/libxcb.so.1 #11 0x00007f8c5a56d32c in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #12 0x00007f8c5a7c8beb in _XReply () from /usr/lib/libX11.so.6 #13 0x00007f8c5a7ad982 in XInternAtom () from /usr/lib/libX11.so.6 #14 0x00007f8c568a0e90 in KBackgroundManager::KBackgroundManager(QWidget*, KWinModule*) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #15 0x00007f8c568950df in KDesktop::initRoot() () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #16 0x00007f8c568946d1 in KDesktop::KDesktop(bool, bool) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #17 0x00007f8c568757b0 in kdemain () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #18 0x00007f8c56b278c8 in kdeinitmain () from /opt/kde-3.5.12/lib/kde3/kdesktop.so #19 0x0000000000408f17 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #20 0x000000000040a426 in handle_launcher_request(int) () #21 0x000000000040ad86 in handle_requests(int) () #22 0x000000000040c8da in main ()
Maybe a howto will point to my mistake. Otherwise any help would be very much apprechiated.
Best Regards Nicolas
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
I have seen this exact crash before, and though I had it fixed in SVN revision r1172215 (see http://trinity.pearsoncomputing.net/patches/ for more information on that commit).
I am uncertain as to what nofinal does; is it possible that the Gentoo build set the nofinal option?
There is a simple workaround available, but when implemented Trinity does not export the desktop background to X11.
Tim
___________________________________________________________ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
Great!
The HAL to udev port is on the Trinity to-do list. It is possible that 3.5.13 will remove HAL dependency; it depends on how many developers contribute to the next release cycle, as the bug tracker is overflowing with open bugs.
Tim
Hi Timothy,
thanks for the hint. Explicitly adding --enable-final did the job.
My complete configuration:
./configure --disable-dnssd --without-arts --without-ssl --without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
I have no clue why the debug version fails on gentoo. Do you have any information if the gentoo devs are pulling trinity into there kde-sunset overlay? There has been some talk about this but nothing substancial to my knowledge.
Btw. the HAL dependency should explicitly be checked during the configure process. I got rid of HAL with the xorg 1.8 upgrade and didn't expect trinity needs it. Are you planning to make HAL mandatory in the future?
Nico
-----Ursprüngliche Nachricht----- Von: "Timothy Pearson" kb9vqf@pearsoncomputing.net Gesendet: Oct 2, 2010 12:04:20 AM An: trinity-devel@lists.pearsoncomputing.net Betreff: Re: [trinity-devel] question about building trinity from scratch
hi,
first of all I'd like to say how much I apprechiate you folks taking up the task of maintaining and keeping kde 3.5x spirit alive! I love this desktop and would be very happy to see new versions without the kde4.x bloat overhead.
I've struggeled to compile trinity (tqinterface, kdelibs, kdebase) from scratch on my gentoo box using the latest svn. However I've got it compiled but I'm not quite sure if everything is good. Could you please post some kind of a howto, including dependencies issues. the obsolete documentation on the kde website won't do.
Trinity starts up fine however my problem is that the kdesktop seems to give up on X11 after starting up:
[Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007f8c58c39495 in raise () from /lib/libc.so.6 #6 0x00007f8c58c3a8c0 in abort () from /lib/libc.so.6 #7 0x00007f8c58c74ac7 in ?? () from /lib/libc.so.6 #8 0x00007f8c58c7a056 in ?? () from /lib/libc.so.6 #9 0x00007f8c58c7edec in free () from /lib/libc.so.6 #10 0x00007f8c5a56cf34 in ?? () from /usr/lib/libxcb.so.1 #11 0x00007f8c5a56d32c in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #12 0x00007f8c5a7c8beb in _XReply () from /usr/lib/libX11.so.6 #13 0x00007f8c5a7ad982 in XInternAtom () from /usr/lib/libX11.so.6 #14 0x00007f8c568a0e90 in KBackgroundManager::KBackgroundManager(QWidget*, KWinModule*) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #15 0x00007f8c568950df in KDesktop::initRoot() () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #16 0x00007f8c568946d1 in KDesktop::KDesktop(bool, bool) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #17 0x00007f8c568757b0 in kdemain () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #18 0x00007f8c56b278c8 in kdeinitmain () from /opt/kde-3.5.12/lib/kde3/kdesktop.so #19 0x0000000000408f17 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #20 0x000000000040a426 in handle_launcher_request(int) () #21 0x000000000040ad86 in handle_requests(int) () #22 0x000000000040c8da in main ()
Maybe a howto will point to my mistake. Otherwise any help would be very much apprechiated.
Best Regards Nicolas
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
I have seen this exact crash before, and though I had it fixed in SVN revision r1172215 (see http://trinity.pearsoncomputing.net/patches/ for more information on that commit).
I am uncertain as to what nofinal does; is it possible that the Gentoo build set the nofinal option?
There is a simple workaround available, but when implemented Trinity does not export the desktop background to X11.
Tim
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
Hi Tim,
ok! There is no rush to switch to udev right now. Fixing major issues has priority.
Nico
-----Ursprüngliche Nachricht----- Von: "Timothy Pearson" kb9vqf@pearsoncomputing.net Gesendet: Oct 2, 2010 7:31:51 PM An: trinity-devel@lists.pearsoncomputing.net Betreff: Re: [trinity-devel] question about building trinity from scratch
Great!
The HAL to udev port is on the Trinity to-do list. It is possible that 3.5.13 will remove HAL dependency; it depends on how many developers contribute to the next release cycle, as the bug tracker is overflowing with open bugs.
Tim
Hi Timothy,
thanks for the hint. Explicitly adding --enable-final did the job.
My complete configuration:
./configure --disable-dnssd --without-arts --without-ssl --without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
I have no clue why the debug version fails on gentoo. Do you have any information if the gentoo devs are pulling trinity into there kde-sunset overlay? There has been some talk about this but nothing substancial to my knowledge.
Btw. the HAL dependency should explicitly be checked during the configure process. I got rid of HAL with the xorg 1.8 upgrade and didn't expect trinity needs it. Are you planning to make HAL mandatory in the future?
Nico
-----Ursprüngliche Nachricht----- Von: "Timothy Pearson" kb9vqf@pearsoncomputing.net Gesendet: Oct 2, 2010 12:04:20 AM An: trinity-devel@lists.pearsoncomputing.net Betreff: Re: [trinity-devel] question about building trinity from scratch
hi,
first of all I'd like to say how much I apprechiate you folks taking up the task of maintaining and keeping kde 3.5x spirit alive! I love this desktop and would be very happy to see new versions without the kde4.x bloat overhead.
I've struggeled to compile trinity (tqinterface, kdelibs, kdebase) from scratch on my gentoo box using the latest svn. However I've got it compiled but I'm not quite sure if everything is good. Could you please post some kind of a howto, including dependencies issues. the obsolete documentation on the kde website won't do.
Trinity starts up fine however my problem is that the kdesktop seems to give up on X11 after starting up:
[Thread debugging using libthread_db enabled] [KCrash handler] #5 0x00007f8c58c39495 in raise () from /lib/libc.so.6 #6 0x00007f8c58c3a8c0 in abort () from /lib/libc.so.6 #7 0x00007f8c58c74ac7 in ?? () from /lib/libc.so.6 #8 0x00007f8c58c7a056 in ?? () from /lib/libc.so.6 #9 0x00007f8c58c7edec in free () from /lib/libc.so.6 #10 0x00007f8c5a56cf34 in ?? () from /usr/lib/libxcb.so.1 #11 0x00007f8c5a56d32c in xcb_wait_for_reply () from /usr/lib/libxcb.so.1 #12 0x00007f8c5a7c8beb in _XReply () from /usr/lib/libX11.so.6 #13 0x00007f8c5a7ad982 in XInternAtom () from /usr/lib/libX11.so.6 #14 0x00007f8c568a0e90 in KBackgroundManager::KBackgroundManager(QWidget*, KWinModule*) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #15 0x00007f8c568950df in KDesktop::initRoot() () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #16 0x00007f8c568946d1 in KDesktop::KDesktop(bool, bool) () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #17 0x00007f8c568757b0 in kdemain () from /opt/kde-3.5.12/lib/libkdeinit_kdesktop.so #18 0x00007f8c56b278c8 in kdeinitmain () from /opt/kde-3.5.12/lib/kde3/kdesktop.so #19 0x0000000000408f17 in launch(int, char const*, char const*, char const*, int, char const*, bool, char const*, bool, char const*) () #20 0x000000000040a426 in handle_launcher_request(int) () #21 0x000000000040ad86 in handle_requests(int) () #22 0x000000000040c8da in main ()
Maybe a howto will point to my mistake. Otherwise any help would be very much apprechiated.
Best Regards Nicolas
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
I have seen this exact crash before, and though I had it fixed in SVN revision r1172215 (see http://trinity.pearsoncomputing.net/patches/ for more information on that commit).
I am uncertain as to what nofinal does; is it possible that the Gentoo build set the nofinal option?
There is a simple workaround available, but when implemented Trinity does not export the desktop background to X11.
Tim
Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02
___________________________________________________________ WEB.DE DSL Doppel-Flat ab 19,99 €/mtl.! Jetzt auch mit gratis Notebook-Flat! http://produkte.web.de/go/DSL_Doppel_Flatrate/2
Is there any documentation notes we can add to the wiki about "--enable-final"? How about "--disable-rpath"?
Darrell
--- On Sat, 10/2/10, Nicolas Kalkhof nkalkhof@web.de wrote:
From: Nicolas Kalkhof nkalkhof@web.de Subject: Re: [trinity-devel] question about building trinity from scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 6:35 AM Hi Timothy,
thanks for the hint. Explicitly adding --enable-final did the job.
My complete configuration:
./configure --disable-dnssd --without-arts --without-ssl --without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
disable-rpath disables the hard coding of library paths within built libraries and binaries, instead relying on standard library search paths to locate needed library files.
I do not know what enable-final does.
Tim
Is there any documentation notes we can add to the wiki about "--enable-final"? How about "--disable-rpath"?
Darrell
--- On Sat, 10/2/10, Nicolas Kalkhof nkalkhof@web.de wrote:
From: Nicolas Kalkhof nkalkhof@web.de Subject: Re: [trinity-devel] question about building trinity from scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 6:35 AM Hi Timothy,
thanks for the hint. Explicitly adding --enable-final did the job.
My complete configuration:
./configure --disable-dnssd --without-arts --without-ssl --without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
When is disable-rpath necessary? I never used that option, but if there are times when that is necessary or advisable, then something should be in the wiki.
Darrell
--- On Sat, 10/2/10, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] question about building trinity from scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 2:13 PM disable-rpath disables the hard coding of library paths within built libraries and binaries, instead relying on standard library search paths to locate needed library files.
I do not know what enable-final does.
Tim
Is there any documentation notes we can add to the
wiki about
"--enable-final"? How about "--disable-rpath"?
Darrell
--- On Sat, 10/2/10, Nicolas Kalkhof nkalkhof@web.de
wrote:
From: Nicolas Kalkhof nkalkhof@web.de Subject: Re: [trinity-devel] question about
building trinity from
scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 6:35 AM Hi Timothy,
thanks for the hint. Explicitly adding
--enable-final did
the job.
My complete configuration:
./configure --disable-dnssd --without-arts
--without-ssl
--without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
Generally, whenever there is a local copy already available on the system of a library that is to be be compiled. In that case, it prevents the final binaries and libraries from referencing the custom library that exists in a custom location on your system.
Also, it is used when linking libraries that exist in the build directory, to avoid the relinking process at the end of the build.
Tim
When is disable-rpath necessary? I never used that option, but if there are times when that is necessary or advisable, then something should be in the wiki.
Darrell
--- On Sat, 10/2/10, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] question about building trinity from scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 2:13 PM disable-rpath disables the hard coding of library paths within built libraries and binaries, instead relying on standard library search paths to locate needed library files.
I do not know what enable-final does.
Tim
Is there any documentation notes we can add to the
wiki about
"--enable-final"? How about "--disable-rpath"?
Darrell
--- On Sat, 10/2/10, Nicolas Kalkhof nkalkhof@web.de
wrote:
From: Nicolas Kalkhof nkalkhof@web.de Subject: Re: [trinity-devel] question about
building trinity from
scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 6:35 AM Hi Timothy,
thanks for the hint. Explicitly adding
--enable-final did
the job.
My complete configuration:
./configure --disable-dnssd --without-arts
--without-ssl
--without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
not having --disable-rpath is a bad thing to do. without it, configure will practically hard-link all the libraries... Which is never good.
On Sat, Oct 2, 2010 at 17:09, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
Generally, whenever there is a local copy already available on the system of a library that is to be be compiled. In that case, it prevents the final binaries and libraries from referencing the custom library that exists in a custom location on your system.
Also, it is used when linking libraries that exist in the build directory, to avoid the relinking process at the end of the build.
Tim
When is disable-rpath necessary? I never used that option, but if there are times when that is necessary or advisable, then something should be in the wiki.
Darrell
--- On Sat, 10/2/10, Timothy Pearson kb9vqf@pearsoncomputing.net wrote:
From: Timothy Pearson kb9vqf@pearsoncomputing.net Subject: Re: [trinity-devel] question about building trinity from scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 2:13 PM disable-rpath disables the hard coding of library paths within built libraries and binaries, instead relying on standard library search paths to locate needed library files.
I do not know what enable-final does.
Tim
Is there any documentation notes we can add to the
wiki about
"--enable-final"? How about "--disable-rpath"?
Darrell
--- On Sat, 10/2/10, Nicolas Kalkhof nkalkhof@web.de
wrote:
From: Nicolas Kalkhof nkalkhof@web.de Subject: Re: [trinity-devel] question about
building trinity from
scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 6:35 AM Hi Timothy,
thanks for the hint. Explicitly adding
--enable-final did
the job.
My complete configuration:
./configure --disable-dnssd --without-arts
--without-ssl
--without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
On Saturday 02 October 2010 22:13:55 Timothy Pearson wrote: [...]
I do not know what enable-final does.
http://developer.kde.org/documentation/other/developer-faq.html
--enable-final: Concatenates all .cpp files into one big .all_cpp.cpp file, and compiles it in one go, instead of compiling each .cpp file on its own. This makes the whole compilation much faster, and often leads to better optimised code, but it also requires much more memory. And it often results in compilation errors when headers included by different source files clash one with the other, or when using c static functions with the same name in different source files. This is a good thing to do at packaging time, but of course not for developers, since a change in one file means recompiling everything.
Tim
disable-rpath disables the hard coding of library paths within built
correct. It's needed on gentoo boxes obviously to compile the kdebase code. However the old kde 3.5.10 did fine without it. As for the --enable-final switch...good question. I've never used the switch with kde 3.x builds before.
Would be interesting to know why this is needed on gentoo.
Nico
libraries and binaries, instead relying on standard library search paths to locate needed library files.
I do not know what enable-final does.
-----Ursprüngliche Nachricht----- Von: "Timothy Pearson" kb9vqf@pearsoncomputing.net Gesendet: Oct 2, 2010 9:13:55 PM An: trinity-devel@lists.pearsoncomputing.net Betreff: Re: [trinity-devel] question about building trinity from scratch
disable-rpath disables the hard coding of library paths within built libraries and binaries, instead relying on standard library search paths to locate needed library files.
I do not know what enable-final does.
Tim
Is there any documentation notes we can add to the wiki about "--enable-final"? How about "--disable-rpath"?
Darrell
--- On Sat, 10/2/10, Nicolas Kalkhof nkalkhof@web.de wrote:
From: Nicolas Kalkhof nkalkhof@web.de Subject: Re: [trinity-devel] question about building trinity from scratch To: trinity-devel@lists.pearsoncomputing.net Date: Saturday, October 2, 2010, 6:35 AM Hi Timothy,
thanks for the hint. Explicitly adding --enable-final did the job.
My complete configuration:
./configure --disable-dnssd --without-arts --without-ssl --without-xinerama --disable-rpath --enable-final --prefix=/opt/kde-3.5.12
___________________________________________________________ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: https://produkte.web.de/go/demail02