Summary: | Building binutils might require texinfo and flex | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Rabbe Fogelholm <rabbe> |
Component: | Prefix Support | Assignee: | Gentoo non-Linux Team <alt> |
Status: | VERIFIED LATER | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Other | ||
URL: | http://www.gentoo.org/proj/en/gentoo-alt/prefix/bootstrap-solaris.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rabbe Fogelholm
2007-04-08 21:02:07 UTC
I am following the "Gentoo Prefixed Portage Bootstrap Process for Solaris" paper a second time, after messing up on my first attempt. This time I am building the Gentoo software as an unprivileged user. I can confirm that sys-devel/flex must be emerged before binutils this time as well. As for texinfo there is no new information this time, since I have preinstalled Gnu texinfo from a binary package prior to the entire prefixed portage bootstrap exercise. I changed the bootstrap to install binutils-2.16.1 initially, because that one doesn't need texinfo. I added flex to the instructions before binutils. Thanks! I think maybe there can be robustness problems with specifying a particular version such as binutils-2.16. I haven't made any in-depth investigation, but I would like to contribute this observation: Some weeks ago my "prefix portage" installation became broken; all of a sudden I could no longer emerge new versions of anything. It appeared to be a Python-related problem and I could not find an easy way to fix it. So I decided to run through the entire bootstrapping sequence again. At step 1.8 (of the May 7, 2007 version of the guide) it says to emerge binutils-2.16*. This did not succeed, it terminated with a low-level error that I did not capture unfortunately. I then tried to just do 'emerge --oneshot --nodeps sys-devel/binutils', which successfully gave me a 2.17 version. There is of course the risk that my system is somehow different from a clean Solaris10 system since I have already bootstrapped the "prefix gentoo" once. It would be good to try and repeat the bootstrap procedure on a clean system and see if the binutils-2.16 problem is really an issue. I don't have the resources to do that right now though. I'll rebootstrap on Solaris 10/x86 using the manual and see what happens. flex is emerged before binutils texinfo is emerged between two binutils emerges. Last time this worked for me. Good to hear. Myself I can't test, I don't have access to Solaris machines anymore. |