errored out on 7.b. Installing the Sources. Code Listing 4: Changing the kernel source symlink It wouldn
errored out on 7.b. Installing the Sources. Code Listing 4: Changing the kernel source symlink It wouldnt allow me to do this b/c for some reason the sources never hit properly. # rm /usr/src/linux # cd /usr/src # ln -s linux-2.6.12.2-pa2 linux I tried an emerge sync, then an emerge --uDv. It didnt work.
Hmm??? USE="symlink" emerge hppa-sources? man ln? Also, the version there is only an *example*, you need to adjust it to actual version installed (2.6.14.3_p0 is the latest stable). @GDP - why don't we update the handbook with info about USE="symlink", like in http://www.gentoo.org/doc/en/kernel-upgrade.xml? This has nothing to do with release, reassigning.
i will go ahead with the USE flag, thanks for the advice. yeah, i understand also that was an *example* i already ensured it was pointing to the kernel that i untared in /usr/src thanks mike
I have now noticed that the failure is actually after the maual kernel configuration where the emerge pciuils. i have failure with both emerge pciutils, and the following make menuconfig. also the old failure that i noticed was when i used the USE="-doc" i will try again and double check all of my work. mike
(In reply to comment #3) > I have now noticed that the failure is actually after the maual kernel > configuration where the emerge pciuils. > > i have failure with both emerge pciutils, and the following make menuconfig. > > also the old failure that i noticed was when i used the USE="-doc" i will try > again and double check all of my work. Please, don't clutter this bug with irrelevant comments. Besides, I don't really understand a word from the above. File a separate bug about pciutils, a separate bug about kernel compilation issues and be sure to include emerge --info, actual error messages and steps to reproduce the problem. This bug is about documenting USE="symlink" in Gentoo Handbook. Thanks.
(In reply to comment #4) > Please, don't clutter this bug with irrelevant comments. Uh? Who's cluttering this bug? You are. > Besides, I don't really understand a word from the above. You've made this very obvious. > This bug is about documenting USE="symlink" in Gentoo Handbook. No, it's not. You changed it without reading Michael's comments. Michael has already mentioned that he had checked that the symlink was ok and the problem with emerging pciutils is a clear indication that something else must have gone wrong. USE="-doc" emerge hppa-sources does work on a clean install USE="-doc symlink" emerge hppa-sources would make sure the symlink is properly created indeed. emerge pciutils and make menuconfig should definitely work. Michael, please provide us with more info about what goes wrong. Any error messages? The output of emerge --info and dmesg might help us as well. You may want to check with the guys in #gentoo-hppa on freenode.
(In reply to comment #5) > (In reply to comment #4) > > Please, don't clutter this bug with irrelevant comments. > Uh? Who's cluttering this bug? You are. > > > Besides, I don't really understand a word from the above. > You've made this very obvious. Could you please try to explain what the original reporter is talking about? Am I correct when I assume that he's having some issues with emerging pciutils and that it complains about something under /usr/src/linux? Is this really a documentation issue?
(In reply to comment #6) > Is this really a documentation issue? Probably not, but without more info, I can neither help Michael nor reassign (to hppa?) nor mark as invalid.
if you're having trouble with pciutils on hppa, file a new bug report ... i can emerge it just fine on my hppa boxes as for the original issue, there isnt any real information as to *what* didnt work
(In reply to comment #8) > if you're having trouble with pciutils on hppa, file a new bug report ... i can > emerge it just fine on my hppa boxes > > as for the original issue, there isnt any real information as to *what* didnt > work >
