Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
revdep-rebuild/gcc problem after latest sync (SOLVED)
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Duplicate Threads
View previous topic :: View next topic  
Author Message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 700
Location: Columbus, OH

PostPosted: Sun Jun 18, 2006 7:19 am    Post subject: revdep-rebuild/gcc problem after latest sync (SOLVED) Reply with quote

I just did a sync this morning, portage got updated to 2.1, but ever since then revdep-rebuild keeps wanting to rebuild gcc. I let it rebuild it once, but then I ran revdep-rebuild again and it insists that the same files are broken. Here's the broken files:

Code:
Checking dynamic linking consistency...
  broken /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-w3c-dom.la (requires /usr/lib/libgcj.la)
  broken /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-xml-sax.la (requires /usr/lib/libgcj.la)
  broken /usr/lib/python2.4/site-packages/_lcms.la (requires /usr/lib/liblcms.la)
 done.
  (/root/.revdep-rebuild.3_rebuild)


And here's how gcc is built:

Code:
Calculating dependencies... done!
[ebuild   R   ] sys-devel/gcc-3.4.6-r1  USE="doc fortran gcj nls objc -bootstrap -boundschecking -build -gtk -hardened -ip28 -ip32r10k -multislot -nocxx -nopie -nossp -vanilla" 0 kB


Any suggestions on what I can do to fix this? It's actually looking for libgcj.la in the wrong place...it's actually in /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/, not /usr/lib. I guess I COULD make a symlink but that's an ugly hack and I want to fix it properly. As far as lcms goes...it's not installed and the USE flag is off.


Last edited by Akaihiryuu on Thu Jul 06, 2006 2:56 pm; edited 1 time in total
Back to top
View user's profile Send private message
edomaur
n00b
n00b


Joined: 19 Sep 2002
Posts: 73
Location: Switzerland

PostPosted: Sun Jun 18, 2006 8:34 am    Post subject: Reply with quote

I have a problem like yours.

This is the full error stack i got :

Code:
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:38:16: gc.h: No such file or directory
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:42: error: syntax error before "word"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:42: warning: type defaults to `int' in declaration of `word'
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:42: warning: data definition has no type or storage class
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:43: error: syntax error before "signed_word"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:43: warning: type defaults to `int' in declaration of `signed_word'
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:43: warning: data definition has no type or storage class
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:46:22: gc_typed.h: No such file or directory
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:60: error: syntax error before "mask"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:60: warning: function declaration isn't a prototype
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:62: error: syntax error before "mask"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:62: warning: function declaration isn't a prototype
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:66: error: syntax error before "mask"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:67: warning: function declaration isn't a prototype
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: In function `__objc_gc_setup_array':
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:68: error: `type' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:68: error: (Each undeclared identifier is reported only once
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:68: error: for each function it appears in.)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:76: error: `mask' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:76: error: `offset' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: At top level:
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:95: error: syntax error before "mask"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:96: warning: function declaration isn't a prototype
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: In function `__objc_gc_setup_struct':
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:101: error: `type' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:123: error: `offset' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:133: warning: implicit declaration of function `GC_set_bit'
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:133: error: `mask' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: At top level:
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:155: error: syntax error before "mask"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:156: warning: function declaration isn't a prototype
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: In function `__objc_gc_setup_union':
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:163: error: `type' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:172: error: `offset' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:172: warning: type defaults to `int' in declaration of `__v'
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:175: error: `mask' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: At top level:
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:184: error: syntax error before "mask"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:185: warning: function declaration isn't a prototype
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: In function `__objc_gc_type_description_from_type':
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:190: error: `type' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:218: error: `mask' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c: In function `__objc_generate_gc_type_description':
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:291: error: `GC_bitmap' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:291: error: syntax error before "mask"
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:308: error: `mask' undeclared (first use in this function)
/var/tmp/portage/gcc-3.4.6-r1/work/gcc-3.4.6/libobjc/gc.c:336: warning: implicit declaration of function `GC_make_descriptor'
make[2]: *** [gc_gc.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/gcc-3.4.6-r1/work/build/i686-pc-linux-gnu/libobjc'
make[1]: *** [all-target-libobjc] Error 2
make[1]: Leaving directory `/var/tmp/portage/gcc-3.4.6-r1/work/build'
make: *** [profiledbootstrap] Error 2

!!! ERROR: sys-devel/gcc-3.4.6-r1 failed.
Call stack:
  ebuild.sh, line 1539:   Called dyn_compile
  ebuild.sh, line 939:   Called src_compile
  ebuild.sh, line 1248:   Called toolchain_src_compile
  toolchain.eclass, line 24:   Called gcc_src_compile
  toolchain.eclass, line 1464:   Called gcc_do_make
  toolchain.eclass, line 1338:   Called die


I'm now trying without Objective C support, perhaps it is that.
_________________
Antoine Boegli
Back to top
View user's profile Send private message
edomaur
n00b
n00b


Joined: 19 Sep 2002
Posts: 73
Location: Switzerland

PostPosted: Sun Jun 18, 2006 10:04 am    Post subject: Reply with quote

Well... Turning off the "objc" flag does it for me.
_________________
Antoine Boegli
Back to top
View user's profile Send private message
samo
Guru
Guru


Joined: 13 Mar 2004
Posts: 443

PostPosted: Sun Jun 18, 2006 10:23 am    Post subject: Reply with quote

I have a similar problem like Akaihiryuu. When I run revdep-rebuild it always re-install gcc. The USE-flag objc is already deactivated.
Code:
Checking dynamic linking consistency...
  broken /usr/lib/avifile-0.7/ac3pass.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/ac3pass.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/audiodec.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/audiodec.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/ffmpeg.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/ffmpeg.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/mad_audiodec.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/mad_audiodec.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/mp3lame_audioenc.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/mp3lame_audioenc.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/mp3lamebin_audioenc.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/mp3lamebin_audioenc.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/mpeg_audiodec.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/mpeg_audiodec.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/osmjpeg.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/osmjpeg.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/vorbis_audio.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/vorbis_audio.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/win32.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/win32.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/avifile-0.7/xvid4.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/avifile-0.7/xvid4.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-w3c-dom.la (requires /usr/lib/libgcj.la)
  broken /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-xml-sax.la (requires /usr/lib/libgcj.la)
  broken /usr/lib/libaviplay.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/libaviplay.la (requires /usr/lib/libaviplayavcodec.la)
  broken /usr/lib/libk3bcore.la (requires /usr/lib/libk3bdevice.la)
  broken /usr/lib/libk3bcore.la (requires /usr/kde/3.4/lib/libkio.la)
  broken /usr/lib/libk3bcore.la (requires /usr/kde/3.4/lib/libkdeui.la)
  broken /usr/lib/libk3bcore.la (requires /usr/kde/3.4/lib/libkdesu.la)
  broken /usr/lib/libk3bcore.la (requires /usr/kde/3.4/lib/libkwalletclient.la)
  broken /usr/lib/libk3bcore.la (requires /usr/kde/3.4/lib/libkdecore.la)
  broken /usr/lib/libk3bcore.la (requires /usr/kde/3.4/lib/libDCOP.la)
  broken /usr/lib/libk3bcore.la (requires /usr/kde/3.4/lib/libkdefx.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/lib/libk3bdevice.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/kde/3.4/lib/libkio.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/kde/3.4/lib/libkdeui.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/kde/3.4/lib/libkdesu.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/kde/3.4/lib/libkwalletclient.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/kde/3.4/lib/libkdecore.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/kde/3.4/lib/libDCOP.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/kde/3.4/lib/libkdefx.la)
  broken /usr/lib/libk3bplugin.la (requires /usr/lib/libsamplerate.la)
  broken /usr/lib/libk3bproject.la (requires /usr/lib/libk3bdevice.la)
  broken /usr/lib/libk3bproject.la (requires /usr/kde/3.4/lib/libkio.la)
  broken /usr/lib/libk3bproject.la (requires /usr/kde/3.4/lib/libkdeui.la)
  broken /usr/lib/libk3bproject.la (requires /usr/kde/3.4/lib/libkdesu.la)
  broken /usr/lib/libk3bproject.la (requires /usr/kde/3.4/lib/libkwalletclient.la)
  broken /usr/lib/libk3bproject.la (requires /usr/kde/3.4/lib/libkdecore.la)
  broken /usr/lib/libk3bproject.la (requires /usr/kde/3.4/lib/libDCOP.la)
  broken /usr/lib/libk3bproject.la (requires /usr/kde/3.4/lib/libkdefx.la)
  broken /usr/lib/libk3bproject.la (requires /usr/lib/libsamplerate.la)
  broken /usr/lib/libk3btools.la (requires /usr/lib/libk3bdevice.la)
  broken /usr/lib/libk3btools.la (requires /usr/kde/3.4/lib/libkio.la)
  broken /usr/lib/libk3btools.la (requires /usr/kde/3.4/lib/libkdeui.la)
  broken /usr/lib/libk3btools.la (requires /usr/kde/3.4/lib/libkdesu.la)
  broken /usr/lib/libk3btools.la (requires /usr/kde/3.4/lib/libkwalletclient.la)
  broken /usr/lib/libk3btools.la (requires /usr/kde/3.4/lib/libkdecore.la)
  broken /usr/lib/libk3btools.la (requires /usr/kde/3.4/lib/libDCOP.la)
  broken /usr/lib/libk3btools.la (requires /usr/kde/3.4/lib/libkdefx.la)
  broken /usr/lib/libodbcinstQ.la (requires /usr/lib/libodbcinst.la)
  broken /usr/lib/libodbcinstQ.la (requires /usr/lib/libodbc.la)
  broken /usr/lib/libqavm.la (requires /usr/lib/libaviplayavformat.la)
  broken /usr/lib/libqavm.la (requires /usr/lib/libaviplayavcodec.la)
 done.
I use kde 3.5 and not 3.4. I want to re-install the packages, but I don't know which.
Code:
gentoo linux # equery b ac3pass.la
[ Searching for file(s) ac3pass.la in *... ]
gentoo linux # equery b audiodec.la
[ Searching for file(s) audiodec.la in *... ]
gentoo linux # equery b ffmpeg.la
[ Searching for file(s) ffmpeg.la in *... ]
gentoo linux # equery b mad_audiodec.la
[ Searching for file(s) mad_audiodec.la in *... ]
gentoo linux #
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 700
Location: Columbus, OH

PostPosted: Sun Jun 18, 2006 11:01 am    Post subject: Reply with quote

I fixed part of it...the lcms one was being caused by some orphaned files that didn't belong to any installed package that needed deleted. I'm still having the problem caused by the other two. I found a temporary workaround, but not a permament solution. There has to be a better solution...

ln -s /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libgcj.la /usr/lib/libgcj.la
Back to top
View user's profile Send private message
samo
Guru
Guru


Joined: 13 Mar 2004
Posts: 443

PostPosted: Sun Jun 18, 2006 11:26 am    Post subject: Reply with quote

Did you manually delete the file /usr/lib/python2.4/site-packages/_lcms.la?
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 700
Location: Columbus, OH

PostPosted: Sun Jun 18, 2006 4:10 pm    Post subject: Reply with quote

Yes, that's how I fixed that...I used equery and found that it didn't belong to any packages, so I just deleted those files and revdep-rebuild isn't complaining about that anymore. But it's still complaining about the files in /usr/lib/gcc/i686-pc-linux-gnu/3.4.6. libgcj.la is there, just for some reason revdep-rebuild is saying it should be in /usr/lib for some strange reason.
Back to top
View user's profile Send private message
Gergan Penkov
Veteran
Veteran


Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)

PostPosted: Sun Jun 18, 2006 4:30 pm    Post subject: Reply with quote

this thread and this one, probably someone should post a bug about this gcc-problem as this pops up now and then, I personally don't have la-s anymore on my system, so for me the problem is non-existent :)
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 700
Location: Columbus, OH

PostPosted: Sun Jun 18, 2006 4:40 pm    Post subject: Reply with quote

Ok, I read that thread and it basically says to delete the .la files and then run revdep-rebuild...but *which* .la files do I delete? I read the whole thing and the included bug report and it's not really clear what I should do.
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 700
Location: Columbus, OH

PostPosted: Sun Jun 18, 2006 4:42 pm    Post subject: Reply with quote

Ok, I read that thread and it basically says to delete the .la files and then run revdep-rebuild...but *which* .la files do I delete? I read the whole thing and the included bug report and it's not really clear what I should do. Does it mean to delete the two .la files that revdep is complaining about? They are looking for libgcj.la in the wrong location. But if I delete those, I don't think revdep will do anything, and it could break gcc...
Back to top
View user's profile Send private message
Gergan Penkov
Veteran
Veteran


Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)

PostPosted: Sun Jun 18, 2006 5:08 pm    Post subject: Reply with quote

In fact it could not break gcc, it could break eventually some package, which links to gcj-libraries and uses the la-s to load the .so-objects (don't know if such package exists, only kde uses this obsolete method for dynamically loading of so-s), the second possible problem could be if some package build system is incorrectly written to look for and link to la-s, but I again haven't heard of any packages, which use the gcc java libraries in such way so it should not be dengerous. As I said I'm running a completely la-free system for some time now and don't have any problems (well I don't use kde).
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack
Back to top
View user's profile Send private message
samo
Guru
Guru


Joined: 13 Mar 2004
Posts: 443

PostPosted: Sun Jun 18, 2006 6:13 pm    Post subject: Reply with quote

Ok, I deleted some libs. Now revdep-rebuild looks also like this:
Code:
Checking dynamic linking consistency...
  broken /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-w3c-dom.la (requires /usr/lib/libgcj.la)
  broken /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-xml-sax.la (requires /usr/lib/libgcj.la)
done.
Back to top
View user's profile Send private message
Gergan Penkov
Veteran
Veteran


Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)

PostPosted: Sun Jun 18, 2006 6:19 pm    Post subject: Reply with quote

I meant that the la-s should be deleted and not libraries, delete these or move them somewhere (if something breaks you could always copy them back):
Code:
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-w3c-dom.la
/usr/lib/gcc/i686-pc-linux-gnu/3.4.6/lib-org-xml-sax.la

and run revdep-rebuild.
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 700
Location: Columbus, OH

PostPosted: Sun Jun 18, 2006 7:39 pm    Post subject: Reply with quote

My workaround was to edit those two .la files and change the reference to /usr/lib/libgcj.la to /usr/lib/gcc/i686-pc-linux-gnu/3.4.6/libgcj.la...this is what it should be, but I don't know why it was different. Perhaps a bug in the gcc ebuild? Anyway, now that these files are pointed at the correct location of libgcj.la, revdep-rebuild doesn't complain anymore.
Back to top
View user's profile Send private message
Gergan Penkov
Veteran
Veteran


Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)

PostPosted: Sun Jun 18, 2006 8:52 pm    Post subject: Reply with quote

well this is also a solution :)
I don't know what the devs intend to or have done for gcc>4.0, as they have nuked the libstdc++.la but for these will they stay or not, I could not check as I nuke the la-s through the portage itself so they don't have the chance to appear at all :), but probably you should post a bug report.
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack
Back to top
View user's profile Send private message
Akaihiryuu
l33t
l33t


Joined: 08 May 2003
Posts: 700
Location: Columbus, OH

PostPosted: Sun Jun 18, 2006 11:08 pm    Post subject: Reply with quote

Yeah, because those .la files are part of the gcc-3.4.6 package...and so is libgcj.la, and they point at the *wrong* location for it. It's definitely a bug. I think there was a recent change to revdep-rebuild or portage that brought the problem out, it's probably been there all along and just wasn't noticed until now.
Back to top
View user's profile Send private message
Will Scarlet
Apprentice
Apprentice


Joined: 19 Mar 2004
Posts: 238

PostPosted: Wed Jun 21, 2006 4:52 pm    Post subject: Reply with quote

Well just to add my 2c:

I found this bug https://bugs.gentoo.org/show_bug.cgi?id=125728 which seems to fit this issue. I don't know what la files do or don't do, so I wont argue whether they're necessary or not. For myself I just did an ln as suggested earlier. It's not a perfect fix, but it works. The only thing I'll have to remember is to remove this link once the bug is fixed.

Hope this help... :wink:
Back to top
View user's profile Send private message
unixj
Tux's lil' helper
Tux's lil' helper


Joined: 18 Jul 2003
Posts: 134

PostPosted: Mon Jun 26, 2006 3:40 am    Post subject: Reply with quote

Gergan Penkov wrote:
well this is also a solution :)
I don't know what the devs intend to or have done for gcc>4.0, as they have nuked the libstdc++.la but for these will they stay or not, I could not check as I nuke the la-s through the portage itself so they don't have the chance to appear at all :), but probably you should post a bug report.


Gergan, sorry to be dense but how do I nuke the la's through portage? They are unnecessary?
Back to top
View user's profile Send private message
Gergan Penkov
Veteran
Veteran


Joined: 17 Jul 2004
Posts: 1464
Location: das kleinste Kuhdorf Deutschlands :)

PostPosted: Mon Jun 26, 2006 4:39 am    Post subject: Reply with quote

https://bugs.gentoo.org/show_bug.cgi?id=90744#c8
Well there could be problems, and I don't know if kde still uses them for so-loading (I have read here and there and seen problems here on the forums, when the la-s are broken), but everything except kde should work just fine without them. The la-s are libtool-archives, which are used mainly by the compilation and are created in this time.
From what I have heard (I am not completely sure), they were used earlier for so-loading just as kde still does, in the times the kernel and the gnu-tools were not ready for this, I could not really remember or I simply didn't care at this time :)
And the second problem could be as in the bug, spanky has said static building of big packages, but I really don't care about this as I hardly could imagine anyone except mozilla or OO building their binaries static :) and this does not concern my system :lol:
_________________
"I knew when an angel whispered into my ear,
You gotta get him away, yeah
Hey little bitch!
Be glad you finally walked away or you may have not lived another day."
Godsmack
Back to top
View user's profile Send private message
desultory
Administrator
Administrator


Joined: 04 Nov 2005
Posts: 7820

PostPosted: Sun Feb 18, 2007 10:36 am    Post subject: Reply with quote

This has been discussed in topic: "Persistent revdep-rebuild issues: gcc and libgcj.la".

Moved from Portage & Programming to Duplicate Threads.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Duplicate Threads All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum