Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 18811

Summary: install problem with texinfo
Product: Gentoo Linux Reporter: Peter Kullnigg <peter>
Component: [OLD] Core systemAssignee: Seemant Kulleen (RETIRED) <seemant>
Status: RESOLVED DUPLICATE    
Severity: major CC: peter
Priority: High    
Version: 1.4_rc2   
Hardware: x86   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description Peter Kullnigg 2003-04-05 14:55:43 UTC
Hy,




I just wanted to install gentoo on my new linux-machine(Athlon-xp 1ghz) and set 
the CFlags to -march=athlon-xp -=2 -pipe




and the bootstrap.sh script stopped at the installation of texinfo




the only way to get the installation running was to set the CFlags to 
-mcpu=athlon-xp -02 -pipe




The problem in known in the Forums, but I didn't saw a Bugzilla entry, so I 
created it.




greetz




Peter
Comment 1 Seemant Kulleen (RETIRED) gentoo-dev 2003-04-12 07:48:42 UTC
do you have a link to the forums thread?
Comment 2 Daniel Robbins (RETIRED) gentoo-dev 2003-04-18 22:15:25 UTC
I can't replicate this with texinfo-4.5.
Comment 3 Ralph Jones 2003-04-22 01:30:42 UTC
It is still happening with the latest gentoo installation (1.4_rc4).  Do you have a workaround so 
that I can run bootstrap without falling back to another arch flag? (eg. force bootstrap.sh to use 
the more recent texinfo). 
 
One of the threads is: 
http://forums.gentoo.org/viewtopic.php?p=291299 
Comment 4 Arthur Chan 2003-04-24 01:59:38 UTC
drobbins mentioned he couldn't replicate that problem with texinfo 4-5, but as for me, I keep getting errors about texinfo-4.5 being a corrupt ebuild.  i'm running a ~x86 system right now though.
Comment 5 Alan Chandler 2003-05-15 07:48:05 UTC
I also have the same problem - using athlon-xp at texinfo-4.5 

see thread at http://forums.gentoo.org/viewtopic.php?t=54046
for more info on error message and my CFLAGS
Comment 6 Seemant Kulleen (RETIRED) gentoo-dev 2003-06-02 07:52:34 UTC
hmm, seems like a kernel thing

the workaround is to change -march to athlon instead of athlon-xp

*** This bug has been marked as a duplicate of 20173 ***