Can't emerge certain KDE3.4.0_rc1 apps

[nightfrost]

but I'm compiling kdemultimedia again, this time with really plain use-flags. Hey! It just finnished and it compiled fine! (To bad there are no optimizations though...)

Really plain USE-flags? Sorry, but I don't understand, what do USE-flags have to do with compile problems?

And the last time I tried, it made really no difference at all which CFLAGS/CXXFLAGS/LDFLAGS I used for compiling the trouble-makeing-KDE-package, what's why I thought, it can only be a problem with gcc itself, or the compile-flags gcc got compiled with.

Ah, sorry sorry! Of course I don't mean use-flags but CFLAGS/CXXFLAGS/LDFLAGS. I recompiled the toolchain with

Code: Select all

CFLAGS="-march=pentium4 -O2 -pipe -fomit-frame-pointer"
CXXFLAGS="${CFLAGS}"

and then tried to recompile kdemultimedia with

Code: Select all

CFLAGS="-march=pentium4 -mtune=pentium4 -O2 -pipe -fomit-frame-pointer -ftracer -fforce-addr"
CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden -fvisibility=hidden"
LDFLAGS="-Wl,-O1"

Since that failed, I tried to compile kdemultimedia with the same set of compile-flags as I used for the toolchain and it compiled fine. Whereas, before the toolchain recompile| kdemultimedia wouldn't compile no matter what.

[nightfrost]

OK; problem returned when compiling kdeaddons

Code: Select all

.libs/base.o(.text+0x4b56): In function `Base::setProperty(unsigned int, QString const&, QString const&)':
: undefined reference to `Db::put(DbTxn*, Dbt*, Dbt*, unsigned int)'
.libs/base.o(.text+0x4b69): In function `Base::setProperty(unsigned int, QString const&, QString const&)':
: undefined reference to `Db::sync(unsigned int)'
.libs/base.o(.text+0x4ba0): In function `Base::setProperty(unsigned int, QString const&, QString const&)':
: undefined reference to `Dbt::~Dbt()'
.libs/base.o(.text+0x4bb8): In function `Base::setProperty(unsigned int, QString const&, QString const&)':
: undefined reference to `Dbt::~Dbt()'
collect2: ld returned 1 exit status
make[4]: *** [noatun_oblique.la] Error 1
make[4]: Leaving directory `/var/tmp/portage/kdeaddons-3.4.0_rc1/work/kdeaddons-3.4.0/noatun-plugins/oblique'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/var/tmp/portage/kdeaddons-3.4.0_rc1/work/kdeaddons-3.4.0/noatun-plugins/oblique'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/var/tmp/portage/kdeaddons-3.4.0_rc1/work/kdeaddons-3.4.0/noatun-plugins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/kdeaddons-3.4.0_rc1/work/kdeaddons-3.4.0'
make: *** [all] Error 2

!!! ERROR: kde-base/kdeaddons-3.4.0_rc1 failed.
!!! Function kde_src_compile, Line 166, Exitcode 2
!!! died running emake, kde_src_compile:make
!!! If you need support, post the topmost build error, NOT this status message.

There's a lot more of that undefined reference-business... This was compiled with really non-agessive flags... darnit! I thought I had it working now...

[llsardonicll]

I'm currently using gcc-3.4.3.20050110..tried switching to gcc-3.3.4 and it didn't help.
My entire toolchain is compiled with
CFLAGS="-O2 -march=athlon-xp -fomit-frame-pointer -pipe"

[llsardonicll]

Still no idea on how to get around this.
The packages compile just fine on my other machine, same cxxflags as my main machine.
Only thing i see that could make a diffrence is it's strictly x86

[Master One]

Well, just an update for those, who care:

After taking some time to study the gcc onlinedocs, I reverted to the following save set of flags for my IBM ThinkPad T42p:

Code: Select all

CFLAGS="-O2 -march=pentium-m -pipe -fforce-addr -fomit-frame-pointer -fweb"
CXXFLAGS="${CFLAGS} -fvisibility-inlines-hidden"
LDFLAGS="-Wl,-O1"

The clue is, these few flags most likely will give a much better results, than the formerly used stacked "insane" flags.
I now see the sense of going -O2 instead of -O3, at least one of the "insane" flags had questionable results (-fprefetch-loop-arrays -> "These options may generate better or worse code"), and one definitely broke libs without error on compile (-fvisibility=hidden -> only to be used by developers, at least for now).

I compiled my whole system with these save set of flags, started right from the beginning with Bob P's fabulous installation method, and at the moment I am emerging KDE 3.3.2-r1 (I keep staying on the stable side now, and let others do the KDE3.4.0_rc1 testing).

This time everything looks alright.

[llsardonicll]

Something Odd...
I masked rc1 and started to recompile beta2, since it worked well.
Now, beta2 fails to compile with the exact same errors as rc1.
Nothing was changed except to update kde from beta2 to rc1.
Hmm...

[Master One]

Something Odd... I masked rc1 and started to recompile beta2, since it worked well. Now, beta2 fails to compile with the exact same errors as rc1. Nothing was changed except to update kde from beta2 to rc1. Hmm...

You probably have used a compile flag, that broke libs without failure on compile, so you have to check your flags, and recompile the whole system (this is what I have done, and it solved the problem).

[llsardonicll]

that's a very good possability. Just to test I downloaded konstruct and had it build a 3.4rc1 in my home directory. Every KDE component compiled flawlessly. It did build it's own /home version of glib, and xine... and it does seem that all my compile errors are multimedia related (kdemultimedia-kfile-plugins, juk, and kdeaddons-kfile-plugins)

[irf2003]

-fvisibility=hidden, is your problem, remove it from your CXXFLAGS
hth
happy gentooing