View previous topic :: View next topic |
Author |
Message |
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2968
|
Posted: Thu Feb 24, 2005 4:43 pm Post subject: |
|
|
firephoto wrote: | ummm ^ ^ ^ ^ up up up read...
No I didn't but I may have emerged -r3 before the ebuild was changed. |
My bad.
Yes, the PATCHLEVEL in the ebuild was bumped without the ebuild version being bumped, I was running -r3 myself without any problems. Upgrade to -r4 also went fine. |
|
Back to top |
|
|
Philantrop Retired Dev
Joined: 21 Dec 2004 Posts: 1130 Location: Germany
|
Posted: Thu Feb 24, 2005 5:27 pm Post subject: |
|
|
Ok, now I have no "as" at all anymore and can't compile anything again. The binaries you provided, kimchi_sg, didn't help either.
How do I get out of this? |
|
Back to top |
|
|
cybertron n00b
Joined: 30 Jan 2004 Posts: 65 Location: Sweden
|
Posted: Thu Feb 24, 2005 5:36 pm Post subject: |
|
|
philatrop:
This is how I have done it ...twice
I downloaded the binaries from this thread and untarred them : tar -xvjf binutils.tar.bz2 -C /
then I masked binutils-version-r3 and r4 then emerge binutils (which would be binutils r1)
hope this helps?! _________________ Gentoo using ~x86 branch
computer: Dell Inspiron 8500
everything working except standby/suspend
for newbie configs for gentoo/slackware: http://www.linuxportalen.info |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Thu Feb 24, 2005 5:46 pm Post subject: |
|
|
Why are you guys untarring things? Is "emerge binutils -k" broke too? |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2968
|
Posted: Thu Feb 24, 2005 6:08 pm Post subject: |
|
|
firephoto wrote: | Why are you guys untarring things? Is "emerge binutils -k" broke too? |
Read the post before yours.
Seems like you have to untar first, then emerge -k the file inside.
Darn, I feel like a guy who wants a fire in his house so that he can try out his fire extinguisher. |
|
Back to top |
|
|
Philantrop Retired Dev
Joined: 21 Dec 2004 Posts: 1130 Location: Germany
|
Posted: Thu Feb 24, 2005 6:15 pm Post subject: |
|
|
Well, I downloaded the binaries, too, but "as" (nor any other of the binutils) doesn't seem to be usable. Neither before nor after untarring the binaries.
Now any ideas would be appreciated. |
|
Back to top |
|
|
firephoto Veteran
Joined: 29 Oct 2003 Posts: 1612 Location: +48° 5' 23.40", -119° 48' 30.00"
|
Posted: Thu Feb 24, 2005 6:17 pm Post subject: |
|
|
So if binutils is broke then "emerge" doesn't work? I thought it just broke compiling? |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2968
|
Posted: Thu Feb 24, 2005 6:18 pm Post subject: |
|
|
Philantrop wrote: | Well, I downloaded the binaries, too, but "as" (nor any other of the binutils) doesn't seem to be usable. Neither before nor after untarring the binaries.
Now any ideas would be appreciated. |
Wait, did you emerge -C binutils before untarring? |
|
Back to top |
|
|
Philantrop Retired Dev
Joined: 21 Dec 2004 Posts: 1130 Location: Germany
|
Posted: Thu Feb 24, 2005 6:23 pm Post subject: |
|
|
kimchi_sg wrote: | Philantrop wrote: | Well, I downloaded the binaries, too, but "as" (nor any other of the binutils) doesn't seem to be usable. Neither before nor after untarring the binaries.
Now any ideas would be appreciated. |
Wait, did you emerge -C binutils before untarring? |
No, I didn't. Excuse me for being cautious now: Should I? |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2968
|
Posted: Thu Feb 24, 2005 6:44 pm Post subject: |
|
|
Philantrop wrote: | No, I didn't. Excuse me for being cautious now: Should I? |
Yes, emerge -C binutils will clear away the old, sick as. |
|
Back to top |
|
|
bobbens n00b
Joined: 17 Feb 2005 Posts: 16 Location: Barcelona
|
Posted: Thu Feb 24, 2005 6:48 pm Post subject: |
|
|
kimchi_sg wrote: | Philantrop wrote: | No, I didn't. Excuse me for being cautious now: Should I? |
Yes, emerge -C binutils will clear away the old, sick as. |
I got it to work without removing them, just untarred into / and emerged them, worked perfectly too. _________________ -bobbens
Registered Linux user number #376329 |
|
Back to top |
|
|
Philantrop Retired Dev
Joined: 21 Dec 2004 Posts: 1130 Location: Germany
|
Posted: Thu Feb 24, 2005 6:53 pm Post subject: |
|
|
kimchi_sg wrote: | Philantrop wrote: | No, I didn't. Excuse me for being cautious now: Should I? |
Yes, emerge -C binutils will clear away the old, sick as. |
Ok, that didn't help either. That's what I did so far:
1. Emerge the broken -r3 binutils.
2. Recovered by untarring the -r2 binaries provided in this thread. (Yes, firephoto, emerge still works but I just want to get a working installation and untarring simply did the job.). Masked r3.
3. Emerge the broken -r4 binutils. "as" doesn't segfault anymore but simply isn't visible to the compiler anymore. Got very, very angry.
4. Tried to recover by untarring the binaries you promoted, kimchi. (Yes, all to /)
5. emerge -C binutils. emerge binutils (after masking -r4)
Result: "as" can't be found *at all* anymore (the following is from binutils' config.log):
configure:1908: gcc -o conftest -march=athlon-xp -O2 -pipe conftest.c 1>&5
gcc: installation problem, cannot exec `as': No such file or directory
configure:1905: fatal error: error closing -: Broken pipe
compilation terminated. |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2968
|
Posted: Thu Feb 24, 2005 7:10 pm Post subject: |
|
|
Philantrop wrote: | Got very, very angry. |
That remark is uncalled for. We are all just trying to find a solution, and in no way am I trying to pass myself off as The Binutils Guru.
There is a risk whenever you set ACCEPT_KEYWORDS="~x86", and this bug is just one example. It is the cruel reality and has to be accepted as such. |
|
Back to top |
|
|
Philantrop Retired Dev
Joined: 21 Dec 2004 Posts: 1130 Location: Germany
|
Posted: Thu Feb 24, 2005 7:15 pm Post subject: |
|
|
kimchi_sg wrote: | Philantrop wrote: | Got very, very angry. |
That remark is uncalled for. We are all just trying to find a solution, and in no way am I trying to pass myself off as The Binutils Guru.
There is a risk whenever you set ACCEPT_KEYWORDS="~x86", and this bug is just one example. It is the cruel reality and has to be accepted as such. |
No, kimchi. Once I can easily write it off like that but twice in a row is a bit much. I goof up once in a while, too. But this is the worst QA I've ever seen. And I've seen really bad QA since that's the major part of my job. If I was the guy behind this second round of broken binutils I would step down. As simple as that. They're too important. And unless you're the guy who released r3 and r4 this remark is not about you.
I'm not here to rant about that. I'm now simply trying to get my problem resolved and I'm still thankful for any suggestion. And I'm glad you're trying to help. |
|
Back to top |
|
|
Syylk n00b
Joined: 22 Jun 2004 Posts: 37 Location: Roma (IT)
|
Posted: Thu Feb 24, 2005 7:26 pm Post subject: |
|
|
My experience with this.
Got bit by the bug, and started worrying if my cardiovascular system was up to the task of "~x86"!
Since I update quite often (once every three/four days or so), I had the binutils-r1 bin package lying around. I masked the -r3 and -r4 ones, and issued Code: | emerge -1 -k /usr/portage/packages/All/binutils-2.15.92.0.2-r1 | Besides emerge righteously complaining about the path, I had back my "as" working in no time, and now I'm updating world happily again.
Ah, for statistic reasons, I have an AthlonXP 2500+, so the bug doesn't hit only P4 users...
HTH
-- Francesco |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2968
|
Posted: Fri Feb 25, 2005 12:18 am Post subject: |
|
|
Philantrop wrote: | No, kimchi. Once I can easily write it off like that but twice in a row is a bit much. I goof up once in a while, too. But this is the worst QA I've ever seen. And I've seen really bad QA since that's the major part of my job. If I was the guy behind this second round of broken binutils I would step down. |
Ah, but you are only half right here. The developers are not guilty of bad QA so far.
They depend on bug reports to see if their patch changes have fixed the problem. As I said in this post,
Quote: | I feel like a guy who wants a fire in his house so that he can try out his fire extinguisher. |
And I'm sure the devs are too. They have tested -r4 "in-house" to the best of their ability. And as with all things ~x86, users' bug reports are the only way they can accurately gauge whether the fix works on any hardware or software combination other than theirs. We are not like Redhat or Mandrake, which have large corps of in-house engineers and testers to zap out any bugs. Most (all?) of our developers do not work on a full-time basis, and have limited hardware resources to test patches.
As far as we can tell from the initial comments in the bug report, this breakage of binutils was caused by a increment in the PATCHLEVEL in the -r3 ebuild, causing a broken GCC 4.0 compatibility patch to be applied. The reasonable step would be for them to modify that patch, and if it tested okay on their hardware, to release it into CVS. This they have done.
As cybertron said in this post,
cybertron wrote: | philatrop:
This is how I have done it ...twice
I downloaded the binaries from this thread and untarred them : tar -xvjf binutils.tar.bz2 -C /
then I masked binutils-version-r3 and r4 then emerge binutils (which would be binutils r1) |
In other words, it seems to be working on his systems, but not on yours.
Please feedback to the bug report if you have not done so, so that the devs may re-open this bug. To reiterate, the developers are not guilty of bad QA at this point, as the process is still not over, and we are now at the "testing" stage.
P.S. In case I made myself sound like a quack by advising you to unmerge the old binutils first, here is where I got the idea. |
|
Back to top |
|
|
Sipi Guru
Joined: 03 Apr 2003 Posts: 406 Location: Hungary
|
Posted: Fri Feb 25, 2005 11:50 am Post subject: |
|
|
Well, you do not has as anymore...
Well, do did not follow my advice...
Now, you should try the other thiongs in that post. It looks like you have the old env files on your system, so, these points to nonexistant places, directories to find as.
Please, try the unmerge, or at least try to delete the settings from the env.d dir (and env-update and source /etc/profile).
It WILL work if you do understand what and why to do. If not, just try to do it. It works, I promise.
BTW: you stated that it is a big mistake to make the error twice.
Khm... So, you tried to install an ~x86 package again without FEATURES="maketest"? I tried it, and it failed again.
So, maybe there are steps which _you_ can do to avoid problems, not just for the developers...
Regards,
Sipi |
|
Back to top |
|
|
jeremy whiting Apprentice
Joined: 25 May 2004 Posts: 159 Location: UT
|
Posted: Fri Feb 25, 2005 12:52 pm Post subject: |
|
|
Hi, same problem here, after I got -r3 emerge keeps complaining that "as" segfaults, so I did
download binutils from site listed above,
mask -r3 and -r4...
Code: | tar -jxvf binutils-....bz2 -C / |
and now
dies with
Code: | configure: creating ./config.status
config.status: creating .gdbinit
config.status: creating Makefile
config.status: creating doc/Makefile
config.status: creating po/Makefile.in
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing default commands
!!! ERROR: sys-devel/binutils-2.15.92.0.2-r1 failed.
!!! Function src_compile, Line 84, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.
|
any ideas are very welcome. did I miss a step somewhere or something?[/code] |
|
Back to top |
|
|
dentharg Guru
Joined: 10 Aug 2004 Posts: 438 Location: /poland/wroclaw
|
Posted: Fri Feb 25, 2005 1:14 pm Post subject: |
|
|
Hmm.. I did almost the same as you. I unmerged binutils and then *emerged* binary package, downloaded from the site, not untarred it.
Everything works fine. |
|
Back to top |
|
|
zaanpenguin Apprentice
Joined: 01 Jul 2003 Posts: 203
|
Posted: Fri Feb 25, 2005 2:00 pm Post subject: |
|
|
Last update:
ftp://ftp.ruled.org/pub/Gentoo now contains 'real' binary packages made with quickpkg and an updated README on how to install them.
Have fun. _________________ Staying crunchy even in milk! |
|
Back to top |
|
|
lenk Apprentice
Joined: 08 Mar 2004 Posts: 211
|
Posted: Fri Feb 25, 2005 5:44 pm Post subject: |
|
|
This is quite unbelievable, r3 broken fair enough. Why didn't the dev hard mask the r4 until they know it works? _________________ E6300 Gigabyte GA-965P-DS3 2GB Corsair 320GB Seagate 7200.10 XFX 7600GT Gentoo
Dell M1330 T7500 2GB 160GB 13.3" WXGA Gentoo
Sharp Zaurus SL-C760 Cacko ROM 1.21b / pdaXrom 1.10rc5 512MB CF + 512MB SD
Sun Ultra5 Gentoo |
|
Back to top |
|
|
UncleOwen Veteran
Joined: 27 Feb 2003 Posts: 1493 Location: Germany, Hamburg
|
Posted: Fri Feb 25, 2005 7:06 pm Post subject: |
|
|
Because some people kept yelling "We need a fix ASAP". Well, you get what you deserve. |
|
Back to top |
|
|
vetienne n00b
Joined: 18 May 2004 Posts: 17 Location: France
|
Posted: Fri Feb 25, 2005 9:33 pm Post subject: |
|
|
Philantrop, I had exactly the same problem as you (No more as ). I have also dowload last r4 and untar it with no succes. It appears that the directory bin under /usr/x86_64-pc-linux-gnu (replace with your gcc config) doesn't exist.
I have just recreate it. In this directory there"s a symlink to each file in /usr/x86_64-pc-linux-gnu/binutils/2/15.0.92
I have had manually those symlink and gcc works again.
After that i reemerge binutils r1 and everythings seems ok (the emerge as delete the sumlink and replace it with the real file ). Something should have change between the 2 versions and with the different manipulation something has break.
Hopes it could help you. |
|
Back to top |
|
|
JKT7 n00b
Joined: 05 Sep 2004 Posts: 16
|
Posted: Sat Feb 26, 2005 5:57 am Post subject: |
|
|
Thank you vetienne, that worked for me.
I had the same problem as everyone else - I got the borked -r3 version. Here's what I did to attempt to fix it.
Downloaded the binutils tar from ftp://ftp.ruled.org/pub/Gentoo/ and ran these commands
Code: | # tar xvjf x86-binutils-2.15.92.0.2-r4.tbz2 -C /
# env-update
# source /etc/profile
# emerge ="binutils-2.15.92.0.2-r1" |
That worked and got me a running system. Next I went and upgraded to -r4
That's where things started to get messed up again. I had the no "as" problem as others posted before. I tried the same code as above again:
Code: | # tar xvjf x86-binutils-2.15.92.0.2-r4.tbz2 -C /
# env-update
# source /etc/profile
# emerge ="binutils-2.15.92.0.2-r1" |
with no luck.
Here's where vetienne's fix comes in (change i686-pc-linux-gnu to whatever your system uses):
Code: | # cd /usr/i686-pc-linux-gnu/
# mkdir bin
# cd bin
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/addr2line addr2line
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/ar ar
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/as as
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/c++filt c++filt
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/gprof gprof
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/ld ld
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/nm nm
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/objcopy objcopy
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/objdump objdump
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/ranlib ranlib
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/readelf readelf
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/size size
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/stri stri
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/strings srings
# ln -sf /usr/i686-pc-linux-gnu/binutils-bin/2.15.92.0.2/strip strip |
After that, I could emerge -r1 again:
Code: | # emerge ="binutils-2.15.92.0.2-r1" |
I do not dare attempt an upgrade to -r4 again... I'm staying with -r1
Anyway, I've been running unstable for about a year and a half and I usually update world once a day. Obviously, I have had my fair share of system failures because of that (although that's part of the fun of running ~x86 if you ask me, teaches me more about my system when I read about how to fix it). This one was definitely the worst. Thanks to everyone who helped fix it! |
|
Back to top |
|
|
kimchi_sg Advocate
Joined: 26 Nov 2004 Posts: 2968
|
Posted: Sat Feb 26, 2005 6:04 am Post subject: |
|
|
JKT7 wrote: | I do not dare attempt an upgrade to -r4 again... I'm staying with -r1 |
Do this command to mask binutils version -r4:
Code: | echo ">=sys-devel/binutils-2.15.92.0.2-r3" >> /etc/portage/package.mask |
Otherwise, things will be messed up again when you do your next emerge -uDv world. |
|
Back to top |
|
|
|