View previous topic :: View next topic |
Author |
Message |
syrex314 n00b
Joined: 29 Jul 2003 Posts: 25
|
Posted: Fri Jan 21, 2005 6:10 am Post subject: libstdc++-v3 emerge fails |
|
|
On a G3, I went to emerge libstdc++-v3-3.3.4, and it fails every time:
Code: |
eabi.S: Assemblyer messages:
eabi.S:255: Error: operand out of range (6 is not between 0 and 1)
eabi.S:255: Error: missing operand
|
Any ideas? Should I submit a bug report? |
|
Back to top |
|
|
sirlark Guru
Joined: 25 Oct 2004 Posts: 306 Location: Limerick, Ireland
|
Posted: Fri Jan 21, 2005 12:14 pm Post subject: is this a libtool problem? |
|
|
Just a shot in the dark here, but are you trying to emerge it to fix compilation bugs relating to libtool?
If so you want to run the fix_libtool_file.sh script like so
fix_libtool_files 3.3.4
where 3.3.4 is your old gcc version _________________ Adopt an unanswered post today |
|
Back to top |
|
|
syrex314 n00b
Joined: 29 Jul 2003 Posts: 25
|
Posted: Sat Jan 22, 2005 1:02 am Post subject: |
|
|
No, I'm re-emerging everything (emerge -e world) because I wanted to change some CFLAGS (went from -O2 to -O3 and added -mpowerpc-gfxopt) and have those changes affect my whole system.
I tried putting =sys-lib/libstdc++-v3-3.3.4 in /etc/portage/package.mask to try to get emerge to pick an older version (3.3.3-r1) in hopes that would work, but placing that line in my package.mask does not seem to make a difference, and emerge -e world still tries 3.3.4. |
|
Back to top |
|
|
syrex314 n00b
Joined: 29 Jul 2003 Posts: 25
|
Posted: Sat Jan 22, 2005 4:19 am Post subject: oops... |
|
|
...turns out I should have had sys-libs in my package.mask instead of sys-lib... we'll see if 3.3.3-r1 works. |
|
Back to top |
|
|
|