Bug 105720 – cannot build GNOME, depende on apmd which fails - hardcoded GCC 3.3.5 path

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description Dariusz Wojtas 2005-09-12 12:20:54 UTC]

I have a fresh gentoo installation. (2005.1), after install i synced portage db,
then synced world. And cannot build gnome which depends on apmd.
When it emerges apmd (3.2.1_p4), it searches for GCC 3.3.5, but I have GCC 3.3.6
and build fails.

!!! ERROR: sys-apps/apmd-3.2.1_p4 failed
!!! Function src_compile, Line 41, Exitcode 2

Before it tried to access GCC
i686-pc-linux-gnu-g++:
/usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5-20050130/crtendS.o: No such file or
directory


Reproducible: Always
Steps to Reproduce:
1. make sure you have GCC 3.3.6 (not 3.3.5)
2. try to install ampd 3.2.1_p4

[Comment 1 Daniel Gryniewicz (RETIRED) 2005-09-12 13:58:32 UTC]

This should be fixed by:
fix_libtool_files.sh 3.3.5-20050130

Then re-emerging apmd

[Comment 2 Nick Perkins 2005-09-12 15:14:10 UTC]

Ran fix_libtool_files.sh as described but no fix.

The same error occurs as listed in the bug.

[Comment 3 Dariusz Wojtas 2005-09-13 10:53:54 UTC]

I also tried to run fix_libtool_files.sh with the specified parameters, but it
did not help apmd. Still the same problem with compilation.

[Comment 4 Daniel Gryniewicz (RETIRED) 2005-09-13 13:46:22 UTC]

For what it's worth, you can disable the apm flag and not build apmd, assuming
you don't need APM.  I'm looking further into this bug, but apmd builds fine for me.

[Comment 5 Daniel Gryniewicz (RETIRED) 2005-09-13 13:58:50 UTC]

Could one of you post more of the context of the error?  I cannot reproduce.

[Comment 6 Mr. Bones. (RETIRED) 2005-09-14 18:22:37 UTC]

remerge libtool and try it again.  that should fix it.

[Comment 7 Dariusz Wojtas 2005-09-14 23:12:18 UTC]

OK, this time it merged apmd.
I've synced the portage and tried to
  emerge --update libtool
but it said it's up to date and did not do anything with it.
Then what I did was
  emerge --unmerge libtool
  emerge libtool
  fix_libtool_files.sh 3.3.5-20050130
and then apmd has successfully installed.

The bug can probably be closed, but I just don't know if this is correct
behavior, people can really have troubles with this.
remember that I worked on fresh, 2 days old installation, with synced portage
and updated 'world'.

Works for me now.

[Comment 8 Daniel Gryniewicz (RETIRED) 2005-09-15 08:17:19 UTC]

There was a bug in fix_libtool_files.sh recently, I remember.  I know it was
fixed, but I don't know if it required a bump in libtool.  It's possible that by
re-installing libtool, you got the fixed fix_libtool_files.sh.  At any rate, you
don't need to unmerge to re-emerge the same version, just "emerge libtool" will
re-emerge libtool on top of the existing version.

Thanks for reporting.

[Comment 9 Daniel Gryniewicz (RETIRED) 2005-10-04 09:51:24 UTC]

*** Bug 108086 has been marked as a duplicate of this bug. ***

[Comment 10 Harold Anderson 2005-11-23 03:07:46 UTC]

(In reply to comment #9)
> *** Bug 108086 has been marked as a duplicate of this bug. ***

This is still an issue.  re-emerging libtool and/or running fix_libtool_files.sh
have no effect.  Adding "-apm" to USE variable does work, however.