| View previous topic :: View next topic |
| Author |
Message |
ElCondor
Guru
Joined: 10 Apr 2002
Posts: 520
Location: Vienna, Austria, Europe
|
 Posted: Sat Sep 28, 2002 1:02 pm Post subject: Portage behavior changes? |
 |
|
a few months ago, gnome2 became available and emerge -pu world showed that gnome1.4 blocks gnome. some weeks later, this blocking vanished. since 1 or 2 weeks, emerge -pu world shows only new programs, and displays nothing to be updated!
Okay, I'm trying an emerge -u world now, including gnome1.4 to gnome2 and about a total of 70 new packages, but already one of the first packages (gail) failed due to missing files.
Is it possible that something got terribly broken somewhere in these changes? how can a block vanish? how can there only be new packages though they are installed and to be updated?
* ElCondor pasa *
_________________
Here I am the victim of my own choices and I'm just starting! |
|
| Back to top |
|
 |
pjp
Administrator
Joined: 16 Apr 2002
Posts: 20067
|
| Posted: Sat Sep 28, 2002 6:26 pm Post subject: |
|
|
Which version of portage?
_________________
Quis separabit? Quo animo? |
|
| Back to top |
|
|
ElCondor
Guru
Joined: 10 Apr 2002
Posts: 520
Location: Vienna, Austria, Europe
|
| Posted: Sat Sep 28, 2002 9:46 pm Post subject: |
|
|
I've got portage 2.0.37 currently. here more funny samples:
| Code: | PHIEPS root # emerge -pu imagemagick
These are the packages that I would merge, in order.
Calculating dependencies ...done!
[ebuild N ] app-text/ghostscript-7.05.5
[ebuild N ] media-gfx/imagemagick-5.4.7-r2
|
whereas | Code: |
PHIEPS root # emerge -p imagemagick
These are the packages that I would merge, in order.
Calculating dependencies ...done!
[ebuild U ] media-gfx/imagemagick-5.4.7-r2
|
When I do an emerge -u imagemagick ghostscript is being emerged as shown in the first query.
This happens with every installed package. I don't quite get the point what's happening here ..
* ElCondor pasa *
_________________
Here I am the victim of my own choices and I'm just starting! |
|
| Back to top |
|
|
delta407
Bodhisattva
Joined: 23 Apr 2002
Posts: 2876
Location: Chicago, IL
|
| Posted: Sat Sep 28, 2002 10:00 pm Post subject: |
|
|
That was fixed in Portage 2.0.38.
_________________
I don't believe in witty sigs. |
|
| Back to top |
|
|
ElCondor
Guru
Joined: 10 Apr 2002
Posts: 520
Location: Vienna, Austria, Europe
|
| Posted: Sat Sep 28, 2002 11:05 pm Post subject: |
|
|
I tried to upgrade portage, but dev-lang/python-2.2.1-r4 failed with | Code: | make: *** [sharedmods] Error 139
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line -125, Exitcode 2
!!! Parallel make failed
|
I'll give it another try in a few days .. or maybe with the next patchlevel of python.
* ElCondor pasa *
_________________
Here I am the victim of my own choices and I'm just starting! |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Sat Sep 28, 2002 11:11 pm Post subject: |
|
|
| ElCondor wrote: | | I tried to upgrade portage, but dev-lang/python-2.2.1-r4 failed with [code]make: *** [sharedmods] Error 139 |
Oh, no. That's not good. My research for this thread found that error 139 from make is basically gcc segfaulting out from under you.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
ElCondor
Guru
Joined: 10 Apr 2002
Posts: 520
Location: Vienna, Austria, Europe
|
| Posted: Sun Sep 29, 2002 8:39 am Post subject: |
|
|
| rac wrote: | | Oh, no. That's not good. My research found that error 139 from make is basically gcc segfaulting out from under you. |
That's not exactly what I wanted to hear .. but thanks for the info 
I compiled a binary python-package on another server and installed it, compiled about 40 packages without a problem afterwards, then liprep-0.16.1 failed again with error 139. Since the error is reproduceable for certain packages, at last it seems to be a software-problem. I will recompile gcc and check if the problem is gone then 
* ElCondor pasa *
_________________
Here I am the victim of my own choices and I'm just starting! |
|
| Back to top |
|
|
R-II
n00b
Joined: 02 Sep 2002
Posts: 30
|
| Posted: Sun Sep 29, 2002 4:16 pm Post subject: |
|
|
I got precisely the same error trying to update to python-2.2.1-r4
I suppose if the problem doesn't remedy itself in the next ebuild, I'll have to start to worry.. |
|
| Back to top |
|
|
dtun3Z
n00b
Joined: 30 Apr 2002
Posts: 63
|
| Posted: Sun Sep 29, 2002 6:46 pm Post subject: |
|
|
i got the same error as you when i tried to upgrade from gcc 2.95.x to gcc 3.2. But the upgrade went B0RK,BØRK,BORK(!) and i could not emerge python.
I dont know if there are any tricks to get passed this, and i tried to find a solution, so i installed Gentoo 1.4-pre.
_________________
Best regards
Christer Gundersen / dizzy tun3Z
http://dtz.cjb.net |
|
| Back to top |
|
|
tgnb
Apprentice
Joined: 16 Apr 2002
Posts: 208
Location: New York, NY
|
| Posted: Sun Sep 29, 2002 7:23 pm Post subject: yep |
|
|
getting the same error with python-2.2.1-r4
CFLAGS="-march=i686 -O3 -pipe"
gcc-2.95.3-r7
Pentium 4
didnt have any other problems on this box so far.. only this version of python wont emerge.
gcc -shared build/temp.linux-i686-2.2/mpzmodule.o -L/usr/local/lib -lgmp -o build/lib.linux-i686-2.2/mpz.so
make: *** [sharedmods] Error 139
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line -125, Exitcode 2
!!! Parallel make failed |
|
| Back to top |
|
|
corporate_gadfly
n00b
Joined: 21 Sep 2002
Posts: 29
|
| Posted: Mon Sep 30, 2002 4:12 pm Post subject: |
|
|
| rac wrote: | | ElCondor wrote: | | I tried to upgrade portage, but dev-lang/python-2.2.1-r4 failed with [code]make: *** [sharedmods] Error 139 |
Oh, no. That's not good. My research for this thread found that error 139 from make is basically gcc segfaulting out from under you. |
Hi rac,
However, for some people just emerging gmp once before you emerge python is sufficient to fix the exact same problem. See this bug report. In other words, all is not lost (if the fix works for you) |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Mon Sep 30, 2002 6:16 pm Post subject: |
|
|
| corporate_gadfly wrote: | | However, for some people just emerging gmp once before you emerge python is sufficient to fix the exact same problem. See this bug report. In other words, all is not lost (if the fix works for you) |
Thanks for pointing this out. Anyone have a clue as to why this would cause GCC to fall down? That seems like a pretty drastic reaction.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
tgnb
Apprentice
Joined: 16 Apr 2002
Posts: 208
Location: New York, NY
|
| Posted: Tue Oct 01, 2002 1:16 am Post subject: hmm |
|
|
Some people are suggesting that this is a hardware problem.
Not ruling this out 100%, I do want to note that this gentoo install is on brand new hardware. It is running without a flaw so far other than this error during the python upgrade. This coupled with the fact that others are having the same problem witht the same build of python however makes it seem that this may not be hardware related.
Emerging gmp before python did not fix this issue for me btw.
Unmerging gpm, then emerging python and then re-emerging gpm did the trick as some people in the bug report have done. |
|
| Back to top |
|
|
R-II
n00b
Joined: 02 Sep 2002
Posts: 30
|
| Posted: Tue Oct 01, 2002 11:59 pm Post subject: |
|
|
remerging gmp beforehand seems to have solved the problem. That nasty python-killing-gcc bug has halted my update at step 3 three times now  |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Oct 02, 2002 12:02 am Post subject: |
|
|
I'm really glad people solved this, and I'm still curious as to why this would cause GCC to segfault, or what else could be causing a 139 from make.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
tgnb
Apprentice
Joined: 16 Apr 2002
Posts: 208
Location: New York, NY
|
| Posted: Thu Oct 10, 2002 12:16 am Post subject: im glad too |
|
|
| I have the same problem again with the new ebuild of python. I suppose i will follow the same steps again to fix the problem, but I am still also curious as to why this is happening in the first place. I dont seem to be having any other trouble on this machine, running apache, mysql etc and compiling otherthings without a problem just like before. |
|
| Back to top |
|
|
Mandr4ke
Apprentice
Joined: 25 Jul 2002
Posts: 214
Location: Chicago, IL
|
| Posted: Tue Dec 17, 2002 9:34 pm Post subject: |
|
|
hmm i seem to be getting this excat same problem.. although i just did a fresh 1.2 install and emerge wouldn't even work cause python wasn't working.. i think everything is just royally fucked up at the moment.. a few months ago i installed 1.2 without a hitch a couple times.. compiled everything for source and everything was rock stable and ran so great... well after getting a little to buily and emerging everything.. eheh i wanted to start over and make a nice fresh system.. so i try the 1.4 kept getting segmentation faults .. build errors all the time.. i couldn't even get it bootstrapped without playing with everything for 2-3 days.. so i say fuck it i'll go back to 1.2 and now 1.2 is just fucked to hell.. i can't even get the bootstrap to work on 1.2 casue portage errors out with perl scripts errors..
i don't know what to do anymore.. hehe |
|
| Back to top |
|
|
iKiddo
Guru
Joined: 27 Jun 2002
Posts: 341
Location: Europe?
|
| Posted: Tue Dec 17, 2002 9:53 pm Post subject: |
|
|
| Now that does sound like a hardware issue. If the lockups seem to occur at random, try checking your memory/cpu etc. Also make sure your not overclocking your machine, as emerging from source seems to be taking a lot more resources than 'regular' stress tests. |
|
| Back to top |
|
|
tgnb
Apprentice
Joined: 16 Apr 2002
Posts: 208
Location: New York, NY
|
| Posted: Wed Dec 18, 2002 2:10 pm Post subject: hmm |
|
|
i agree that Mandr4ke's problems sound far mor severe and could be hardware related.
However, the others who are only experiencing this weird problem and can work around it by unmerging gmp before upgrading python and then re-emerging gmp dont seem to have a hardware problem.
I'm happy this workaround exists although it'd be nice to fix the actual problem. |
|
| Back to top |
|
|
Mandr4ke
Apprentice
Joined: 25 Jul 2002
Posts: 214
Location: Chicago, IL
|
| Posted: Wed Dec 18, 2002 7:57 pm Post subject: Re: hmm |
|
|
| tgnb wrote: | i agree that Mandr4ke's problems sound far mor severe and could be hardware related.
However, the others who are only experiencing this weird problem and can work around it by unmerging gmp before upgrading python and then re-emerging gmp dont seem to have a hardware problem.
I'm happy this workaround exists although it'd be nice to fix the actual problem. |
Well this is the crazy thing.. i've had a great 1.2 build going for the past 4-5 months now.. compiled everything from stage 1... it was rock stable.. upgraded was running KDE with nvidia, had quake 3 Linux running bad ass... I was totally in love with gentoo and it was kicking ass... then i decided after doing so many emerges and just installing to much shit i didn't need or use ... i wanted to start over fresh...
well thats when everything when to shit.. i first tried the 1.4 and figured i'd upgrade.. i started over fresh wipping all my paritions clean.. but emerge was just going crazy to all hell, and bin utils was failling on emerge in the bootstrap.. groff.. so i said to hell with it.. and grabed my 1.2 cd since i never had a single problem with it.. now portage can't emerge when install from 1.2 cd.. or any stage of tarballs from 1.2 either.. i guess the version of portage from 1.2 is not compitable anymore which is dam retarded.. it should at least let you upgrade. full support should not just be killed like that... you can rsync and get the packages but anytime after that trying to emerge just gives out python scripts errors.. you can't do anything not bootstrap, emerge nothing works.. so i tried 1.4 again several times.. it just seems like everything in portage and gentoo has gone to shit.. i'm so dam frusteratted... i even ran cpu, ram stress tests.. and my computer is perfectly fine.. i've upgraded, downgraded bio's too.. and still nada.. and now i'm so dam sorry i deleted my perfectly working gentoo system casue now i'll never get it back again.. or this working again.. it just doesn't want to work..  |
|
| Back to top |
|
|
Mandr4ke
Apprentice
Joined: 25 Jul 2002
Posts: 214
Location: Chicago, IL
|
| Posted: Wed Dec 18, 2002 8:04 pm Post subject: |
|
|
| iKiddo wrote: | | Now that does sound like a hardware issue. If the lockups seem to occur at random, try checking your memory/cpu etc. Also make sure your not overclocking your machine, as emerging from source seems to be taking a lot more resources than 'regular' stress tests. |
thats the thing though.. it's not locking up.. it never locks.. it's just erroring out on compiling.. and i never had a single problem with building 1.2 from stage 1.. all the way through.... now it's like nothing works...
I think there just mixing to many dam new packages... they need to make something where it will keeps a profile.. when you build from start.. it needs a predefinded set of packages with versions that is known to not have problems... and will compile only these pre-set versions of each packages for the install and bootstrap and inital system.. after that then you can emerge and update new versions.. of the packages.. and if one isn't working or compitable.. your not stuck till after you have a working system for god's sake!
I mean sorry i'm very frusterated.. but why the hell do we have to come here every dam second to the forums to find workaround for ever little thing.. this should have been setup like this from the start.. and any one thats installing a fresh new install at this time when packages are new and comming out are going to run into a boat load of trouble like this casue that dam emerge always gets the newest build enless it's masked..
i'd still like to find a work around to re-install gcc 2.95 again, but since portage is broken now on 1.2 cd's.. it's a bit confusing.. other then making a new cd's and trying to copy portage after you untar the stage 1.. hmm |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Dec 18, 2002 8:59 pm Post subject: |
|
|
Locking because the end of the thread is better served here.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
|
Portage & Programming
