| View previous topic :: View next topic |
| Author |
Message |
Deranger
Veteran
Joined: 26 Aug 2004
Posts: 1215
|
 Posted: Sun Nov 28, 2004 11:34 pm Post subject: |
 |
|
...And newest GRUB compiles too 
[ EDIT ] ...or not  |
|
| Back to top |
|
 |
rjw8703
Apprentice
Joined: 14 Aug 2004
Posts: 246
Location: Auburn, Al
|
| Posted: Tue Nov 30, 2004 1:34 am Post subject: |
|
|
| Are all of the problems solved? |
|
| Back to top |
|
|
hielvc
Advocate
Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca
|
|
| Back to top |
|
|
XyryX
n00b
Joined: 24 Nov 2004
Posts: 10
|
| Posted: Tue Nov 30, 2004 2:03 am Post subject: |
|
|
Woot..
Ok Finally got everything compiled and booted and working..
New Nitro box is working sweetly.. But I have noticed a few errors I probably need to fix sooner rather than later..
In my log I get the following:
| Code: |
Nov 30 12:49:18 Fenix-Server evdev: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:18 Fenix-Server modprobe: FATAL: Error inserting evdev (/lib/modules/2.6.9-nitro4/kernel/drivers/input/evdev.ko): Invalid module format
Nov 30 12:49:19 Fenix-Server chipreg: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:19 Fenix-Server mtdcore: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:19 Fenix-Server ichxrom: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:19 Fenix-Server modprobe: WARNING: Error inserting chipreg (/lib/modules/2.6.9-nitro4/kernel/drivers/mtd/chips/chipreg.ko): Invalid module format
Nov 30 12:49:19 Fenix-Server modprobe: WARNING: Error inserting mtdcore (/lib/modules/2.6.9-nitro4/kernel/drivers/mtd/mtdcore.ko): Invalid module format
Nov 30 12:49:19 Fenix-Server modprobe: FATAL: Error inserting ichxrom (/lib/modules/2.6.9-nitro4/kernel/drivers/mtd/maps/ichxrom.ko): Invalid module format
Nov 30 12:49:19 Fenix-Server uhci_hcd: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:19 Fenix-Server modprobe: FATAL: Error inserting uhci_hcd (/lib/modules/2.6.9-nitro4/kernel/drivers/usb/host/uhci-hcd.ko): Invalid module format
Nov 30 12:49:20 Fenix-Server uhci_hcd: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: FATAL: Error inserting uhci_hcd (/lib/modules/2.6.9-nitro4/kernel/drivers/usb/host/uhci-hcd.ko): Invalid module format
Nov 30 12:49:20 Fenix-Server snd: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd (/lib/modules/2.6.9-nitro4/kernel/sound/core/snd.ko): Invalid module format
Nov 30 12:49:20 Fenix-Server snd_seq_device: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd_seq_device (/lib/modules/2.6.9-nitro4/kernel/sound/core/seq/snd-seq-device.ko): Invalid m$
Nov 30 12:49:20 Fenix-Server snd_rawmidi: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd_rawmidi (/lib/modules/2.6.9-nitro4/kernel/sound/core/snd-rawmidi.ko): Invalid module form$
Nov 30 12:49:20 Fenix-Server snd_mpu401_uart: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd_mpu401_uart (/lib/modules/2.6.9-nitro4/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko): I$
Nov 30 12:49:20 Fenix-Server gameport: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting gameport (/lib/modules/2.6.9-nitro4/kernel/drivers/input/gameport/gameport.ko): Invalid modul$
Nov 30 12:49:20 Fenix-Server snd_page_alloc: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd_page_alloc (/lib/modules/2.6.9-nitro4/kernel/sound/core/snd-page-alloc.ko): Invalid modul$
Nov 30 12:49:20 Fenix-Server snd_timer: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd_timer (/lib/modules/2.6.9-nitro4/kernel/sound/core/snd-timer.ko): Invalid module format
Nov 30 12:49:20 Fenix-Server snd_pcm: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd_pcm (/lib/modules/2.6.9-nitro4/kernel/sound/core/snd-pcm.ko): Invalid module format
Nov 30 12:49:20 Fenix-Server snd_ac97_codec: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: WARNING: Error inserting snd_ac97_codec (/lib/modules/2.6.9-nitro4/kernel/sound/pci/ac97/snd-ac97-codec.ko): Invalid m$
Nov 30 12:49:20 Fenix-Server snd_intel8x0: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:20 Fenix-Server modprobe: FATAL: Error inserting snd_intel8x0 (/lib/modules/2.6.9-nitro4/kernel/sound/pci/snd-intel8x0.ko): Invalid module format
Nov 30 12:49:21 Fenix-Server parport: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:21 Fenix-Server modprobe: WARNING: Error inserting parport (/lib/modules/2.6.9-nitro4/kernel/drivers/parport/parport.ko): Invalid module format
Nov 30 12:49:21 Fenix-Server parport_pc: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:21 Fenix-Server modprobe: FATAL: Error inserting parport_pc (/lib/modules/2.6.9-nitro4/kernel/drivers/parport/parport_pc.ko): Invalid module for$
Nov 30 12:49:21 Fenix-Server gameport: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:21 Fenix-Server ns558: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:21 Fenix-Server modprobe: WARNING: Error inserting gameport (/lib/modules/2.6.9-nitro4/kernel/drivers/input/gameport/gameport.ko): Invalid modul$
Nov 30 12:49:21 Fenix-Server modprobe: FATAL: Error inserting ns558 (/lib/modules/2.6.9-nitro4/kernel/drivers/input/gameport/ns558.ko): Invalid module format
Nov 30 12:49:22 Fenix-Server gameport: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:22 Fenix-Server analog: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:22 Fenix-Server modprobe: WARNING: Error inserting gameport (/lib/modules/2.6.9-nitro4/kernel/drivers/input/gameport/gameport.ko): Invalid modul$
Nov 30 12:49:22 Fenix-Server modprobe: FATAL: Error inserting analog (/lib/modules/2.6.9-nitro4/kernel/drivers/input/joystick/analog.ko): Invalid module form$
Nov 30 12:49:22 Fenix-Server ehci_hcd: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:22 Fenix-Server uhci_hcd: version magic '2.6.9-nitro4 preempt PENTIUM4 gcc-3.3' should be '2.6.9-nitro4 preempt PENTIUM4 gcc-3.4'
Nov 30 12:49:25 Fenix-Server eth0: link up, 100Mbps, full-duplex, lpa 0x45E1
Nov 30 12:49:26 Fenix-Server dhcpcd[8650]: DHCP_NAK server response received
Nov 30 12:49:29 Fenix-Server sshd[8813]: Server listening on :: port 22.
Nov 30 12:49:29 Fenix-Server sshd[8813]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.
|
Now its a web server so is any of that important ?? |
|
| Back to top |
|
|
hielvc
Advocate
Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca
|
| Posted: Tue Nov 30, 2004 2:36 am Post subject: |
|
|
Thats strange, taking a wild guess its like part of kernel was compiled with gcc-3.3 and the rest with gcc-3.4.3. Run " gcc-config -l " and then select gcc-3.4.3, " gcc-config < 3.4.3s number>"., mount /boot and "make clean && make && modules_install install" .
_________________
An A-Z Index of the Linux BASH command line |
|
| Back to top |
|
|
urfage
n00b
Joined: 05 Sep 2004
Posts: 49
|
| Posted: Tue Nov 30, 2004 2:45 am Post subject: |
|
|
Fixing the GRUB problem:
Change lines 56 and 57 in /usr/portage/sys-boot/grub/grub-0.95.20040823.ebuild from:
| Code: |
has_pie && CC="${tc-getCC} `test_flag -fno-pic` `test_flag -nopie`"
has_ssp && CC="${tc-getCC} `test_flag -fno-stack-protector`"
|
to this:
| Code: |
has_pie && CC="${CC} `test_flag -fno-pic` `test_flag -nopie`"
has_ssp && CC="${CC} `test_flag -fno-stack-protector`"
|
For more commentary check out bug #70111. |
|
| Back to top |
|
|
Deranger
Veteran
Joined: 26 Aug 2004
Posts: 1215
|
| Posted: Tue Nov 30, 2004 6:56 am Post subject: |
|
|
| hielvc wrote: | If your quick  |
Haha, very true! FFS people, bootstrap, bootstrap ... while it passes! |
|
| Back to top |
|
|
XyryX
n00b
Joined: 24 Nov 2004
Posts: 10
|
| Posted: Tue Nov 30, 2004 7:17 am Post subject: |
|
|
Ok.. I did the gcc-config fix where you create a link to /usr/lib/gcc and then recompiled the kernel.. That fixed 99% of the errors I posted above..
Now I get the following error.. Only in logs mind you..
| Code: |
Dec 1 06:11:09 Fenix-Server ichxrom ichxrom_init_one(): Unable to register resource 0xff000000-0xffffffff - kernel bug?
Dec 1 06:11:09 Fenix-Server CFI: Found no ichxrom device at location zero
Dec 1 06:11:09 Fenix-Server JEDEC: Found no ichxrom device at location zero
<<removed the other thousand repeats in here btw.. All done in less than a second at boot..>>
Dec 1 06:11:09 Fenix-Server modprobe: FATAL: Error inserting ichxrom (/lib/modules/2.6.9-nitro4/kernel/drivers/mtd/maps/ichxrom.ko): No such device
|
Anybody know what that message refers to ??? |
|
| Back to top |
|
|
taskara
Advocate
Joined: 10 Apr 2002
Posts: 3763
Location: Australia
|
| Posted: Wed Dec 01, 2004 12:59 am Post subject: |
|
|
hey,
if this guide is supposed to be for 2004.3, then there is no linux-headers to remove (stage1 comes with no linux-headers).
Also, in your make.conf you have accept_keywords="~x86"
is it possible for you to include a list of apps that need to be ~x86 for package.keywords in the howto, so that people don't get a fully ~x86 system?
also, perhaps you can include gcc 3.4 in the howto for 2004.3?
good work
_________________
Kororaa install method - have Gentoo up and running quickly and easily, fully automated with an installer! |
|
| Back to top |
|
|
Deranger
Veteran
Joined: 26 Aug 2004
Posts: 1215
|
| Posted: Wed Dec 01, 2004 7:37 am Post subject: |
|
|
| taskara wrote: | hey,
if this guide is supposed to be for 2004.3, then there is no linux-headers to remove (stage1 comes with no linux-headers).
Also, in your make.conf you have accept_keywords="~x86"
is it possible for you to include a list of apps that need to be ~x86 for package.keywords in the howto, so that people don't get a fully ~x86 system?
also, perhaps you can include gcc 3.4 in the howto for 2004.3?
good work |
Yeah, this has been discussed but looks like ali3nx hasn't edited tutorial, maybe he should.
Well, this guide is meant to be for those who are building bleeding edge box and therefor ACCEPT_KEYWORDS="~arch" are default, so it pulls GCC 3.4.3 automatically. |
|
| Back to top |
|
|
taskara
Advocate
Joined: 10 Apr 2002
Posts: 3763
Location: Australia
|
| Posted: Wed Dec 01, 2004 7:59 am Post subject: |
|
|
| Oktane wrote: | | taskara wrote: | hey,
if this guide is supposed to be for 2004.3, then there is no linux-headers to remove (stage1 comes with no linux-headers).
Also, in your make.conf you have accept_keywords="~x86"
is it possible for you to include a list of apps that need to be ~x86 for package.keywords in the howto, so that people don't get a fully ~x86 system?
also, perhaps you can include gcc 3.4 in the howto for 2004.3?
good work |
Yeah, this has been discussed but looks like ali3nx hasn't edited tutorial, maybe he should.
Well, this guide is meant to be for those who are building bleeding edge box and therefor ACCEPT_KEYWORDS="~arch" are default, so it pulls GCC 3.4.3 automatically. |
righto, fair enough.
cheers
_________________
Kororaa install method - have Gentoo up and running quickly and easily, fully automated with an installer! |
|
| Back to top |
|
|
Hobbit_HK
n00b
Joined: 11 Nov 2004
Posts: 54
Location: Israel
|
| Posted: Wed Dec 01, 2004 6:26 pm Post subject: |
|
|
| [Imago] wrote: | @CompNerd
@Hobbit_HK
i agree it should be added.But atm this doesnt work during bootstraping. See Bug #72596
|
Weird.. Worked for me... I've enabled the locales flags in package.use and it worked...
| Code: |
echo "sys-libs/glibc userlocales" >> /etc/portage/package.use
nano -w /etc/locales.build
|
No mroe 100 locales... just my 4
_________________
- Hobbit HK 
Don't use stage1\2 tarballs
Do a stage1 install from a stage3 tarball |
|
| Back to top |
|
|
D1g1talS0ul
n00b
Joined: 24 Feb 2004
Posts: 9
Location: whereis me
|
| Posted: Thu Dec 02, 2004 6:14 pm Post subject: |
|
|
My system was spitting out the following error during bootstrap.sh
| Quote: |
checking sysdep dirs... sysdeps/i386/elf linuxthreads/sysdeps/unix/sysv/linux/i386 linuxthreads/sysdeps/unix/sysv/linux linuxthreads/sysdeps/pthread sysdeps/pthread linuxthreads/sysdeps/unix/sysv linuxthreads/sysdeps/unix linuxthreads/sysdeps/i386/i686 linuxthreads/sysdeps/i386 libidn/sysdeps/unix sysdeps/unix/sysv/linux/i386 sysdeps/unix/sysv/linux sysdeps/gnu sysdeps/unix/common sysdeps/unix/mman sysdeps/unix/inet sysdeps/unix/sysv/i386 sysdeps/unix/sysv sysdeps/unix/i386 sysdeps/unix sysdeps/posix sysdeps/i386/i686/fpu sysdeps/i386/i686 sysdeps/i386/i486 sysdeps/i386/fpu sysdeps/i386 sysdeps/wordsize-32 sysdeps/ieee754/ldbl-96 sysdeps/ieee754/dbl-64 sysdeps/ieee754/flt-32 sysdeps/ieee754 sysdeps/generic/elf sysdeps/generic
checking for a BSD-compatible install... /bin/install -c
checking whether ln -s works... yes
checking for i686-pc-linux-gnu-gcc... gcc
checking for suffix of object files... configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
!!! ERROR: sys-libs/glibc-2.3.4.20041102 failed.
!!! Function glibc_do_configure, Line 606, Exitcode 1
!!! failed to configure glibc
!!! If you need support, post the topmost build error, NOT this status message.
|
I found another thread that helped me fix the problem by deleting /usr/bin/gcc and ln -s /usr/i686-pc-linux-gnu/gcc-bin/3.4/gcc /usr/bin/gcc
Does anyone know if this will cause adverse side affects or other errors as I progress further down ali3nx's "The sooper dooper spectacular bootstrap-bugfixed oneliner magic"? I'm using an older boot CD that supports reiser4. I figure I came across this issue because I didn't use a gentoo 2004.3 live CD. |
|
| Back to top |
|
|
ali3nx
l33t
Joined: 21 Sep 2003
Posts: 722
Location: Winnipeg, Canada
|
| Posted: Sat Dec 04, 2004 2:14 am Post subject: |
|
|
i've decided it's time to come out of my mid winter hybernation and update the tut once again. onliner updated for the gcc-config bug.
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper! |
|
| Back to top |
|
|
ali3nx
l33t
Joined: 21 Sep 2003
Posts: 722
Location: Winnipeg, Canada
|
| Posted: Sat Dec 04, 2004 4:07 am Post subject: |
|
|
Added a network config section, cleaned up lots of code examples to better reflect 2004.3 and more grammar and spelling edits 
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper! |
|
| Back to top |
|
|
sgtrock
Tux's lil' helper
Joined: 21 Feb 2003
Posts: 87
|
| Posted: Mon Dec 06, 2004 2:21 am Post subject: |
|
|
ali3nx:
Is gentoo.eliteitminds.com supposed to be where the tutorial is kept? DNS keeps complaining that it doesn't exist.
TIA, |
|
| Back to top |
|
|
ali3nx
l33t
Joined: 21 Sep 2003
Posts: 722
Location: Winnipeg, Canada
|
| Posted: Mon Dec 06, 2004 5:53 am Post subject: |
|
|
| sgtrock wrote: | ali3nx:
Is gentoo.eliteitminds.com supposed to be where the tutorial is kept? DNS keeps complaining that it doesn't exist.
TIA, |
Thats my gentoo mirror subdomain which has been without a host for some time. I'm expecting a dual 3.0 xeon in the coming week for a mirror host. So with regards to your question.. no but you can replace that url with any other suitable official gentoo linux mirror.
_________________
Compiling Gentoo since version 1.4
Thousands of Gentoo Installs Completed
Emerged on every continent but Antarctica
Compile long and Prosper! |
|
| Back to top |
|
|
hielvc
Advocate
Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca
|
| Posted: Tue Dec 07, 2004 5:11 am Post subject: |
|
|
ali3nx for a very interesting read which negates doing a stage1 and bootstrap as buggy read rac's post here A more robust installation method also semi hinted at by robmoss here GCC 3.4.3 is upon us! on pg 3
To sumurise | Code: |
tar xjvpf stage3<your version>
<put in your USE flags and CFLAGS>
emerge -C linux-headers && emerge linux26-headers && emerge glibc binutils gcc && emerge -e system |
_________________
An A-Z Index of the Linux BASH command line
Last edited by hielvc on Wed Dec 08, 2004 2:49 am; edited 1 time in total |
|
| Back to top |
|
|
Deranger
Veteran
Joined: 26 Aug 2004
Posts: 1215
|
| Posted: Wed Dec 08, 2004 12:59 pm Post subject: |
|
|
ali3nx, I am not sure if you are aware of this, but here it goes:
Within the new ~x86 baselayout, hostnames/domainnames are no longer set by /etc/hostname or /etc/{nis|dns}domainname. Proper way to set hostnames/domainnames are /etc/conf.d/hostname and /etc/conf.d/domainname... |
|
| Back to top |
|
|
rjw8703
Apprentice
Joined: 14 Aug 2004
Posts: 246
Location: Auburn, Al
|
| Posted: Wed Dec 08, 2004 1:59 pm Post subject: |
|
|
To sumurise Code:
tar xjvpf stage3<your version>
<put in your USE flags and CFLAGS>
emerge -C linux-headers && emerge linux26-headers && emerge glibc binutils gcc && emerge -e system
Don't you need to do an emerge --sync in there someplace? |
|
| Back to top |
|
|
Deranger
Veteran
Joined: 26 Aug 2004
Posts: 1215
|
| Posted: Wed Dec 08, 2004 3:18 pm Post subject: |
|
|
| rjw8703 wrote: | To sumurise Code:
tar xjvpf stage3<your version>
<put in your USE flags and CFLAGS>
emerge -C linux-headers && emerge linux26-headers && emerge glibc binutils gcc && emerge -e system
Don't you need to do an emerge --sync in there someplace? |
Of course, after you have chrooted, just like handbook and this guide says...
I tried that rac's method and it works very well. I grabbed generic x86 stage3ball, boostrapped as usual, then did emerge -e system twice... |
|
| Back to top |
|
|
kimchi_sg
Advocate
Joined: 26 Nov 2004
Posts: 2969
|
| Posted: Wed Dec 08, 2004 3:29 pm Post subject: |
|
|
| rjw8703 wrote: | To sumurise Code:
tar xjvpf stage3<your version>
<put in your USE flags and CFLAGS>
emerge -C linux-headers && emerge linux26-headers && emerge glibc binutils gcc && emerge -e system
Don't you need to do an emerge --sync in there someplace? |
Expand the tarball and mount the proc filesystem into /mnt/gentoo/proc before chrooting into /mnt/gentoo and doing all the emerges.
If sticking more closely to the handbook, right before chrooting one would d/l the latest snapshot of the portage tree, expand it to /mnt/gentoo/usr, then do a emerge sync right after chrooting. It's supposed to save time doing emerge sync, i suppose.
Sounds like time for yet another tuitorial edit...  |
|
| Back to top |
|
|
l0tus_
n00b
Joined: 03 Nov 2004
Posts: 22
|
| Posted: Wed Dec 08, 2004 9:30 pm Post subject: |
|
|
| Oktane wrote: | | ... I grabbed generic x86 stage3ball, boostrapped as usual, then did emerge -e system twice... |
why do u emerge -e system twise? |
|
| Back to top |
|
|
Deranger
Veteran
Joined: 26 Aug 2004
Posts: 1215
|
| Posted: Wed Dec 08, 2004 9:48 pm Post subject: |
|
|
| l0tus_ wrote: | | Oktane wrote: | | ... I grabbed generic x86 stage3ball, boostrapped as usual, then did emerge -e system twice... |
why do u emerge -e system twise? |
To ensure toolchain's completeness |
|
| Back to top |
|
|
hielvc
Advocate
Joined: 19 Apr 2002
Posts: 2805
Location: Oceanside, Ca
|
| Posted: Thu Dec 09, 2004 2:48 am Post subject: |
|
|
rac's point was that because of problems with some functions in portage
that bootstrapping and then emerge system left some packages in libo. And as most
observers here have noticed the constant battles with circular dependencies and
broken ebuilds can drive you batty. So instead of doing a bootstrap you | Code: |
emerge --oneshot glibc binutils gcc > for a regular, non ~x86
<Do this for ~x86 if you want nptl>
emerge -C linux-headers && emerge --oneshot linux26-headers && emerge --oneshot glibc binutils gcc
<Then both groups do this>
emerge system -e |
The first line replaces bootstrap. Its is building your toolchain. Then by
running "emerge -e system" rebuilds your toolchain and everything else to a
twice built toolchain and your USE and CFLAGES. Now you can do it a third or
fourth time like robmoss, but rob is running total bleeding edge and
testing each a every package he installs to see if it works as the manual says.
So he has to make certain that there are no other fudge factors when something fails.
So the new super duper one liner would look like this. | Code: |
env-update && source /etc/profile && emerge --oneshot --nodeps gcc-config && emerge linux26-headers && emerge --oneshot glibc binutils gcc && emerge -e system && emerge syslog-ng xinetd grub hotplug coldplug vixie-cron reiserfsprogs reiser4progs sysfsutils udev dhcpcd && emerge --nodeps acpid ntp && rc-update add syslog-ng default && rc-update add net.eth0 default && rc-update add vixie-cron default && rc-update add xinetd default && rc-update add sshd default && rc-update add hotplug default && rc-update add coldplug default && rc-update add acpid default |
EDIT:1 FIxing my normal screw ups like leaving out -e
2 As Oktane said USE="-* build bootstrap" is not needed..
_________________
An A-Z Index of the Linux BASH command line
Last edited by hielvc on Thu Dec 09, 2004 6:02 pm; edited 1 time in total |
|
| Back to top |
|
|
|
Documentation, Tips & Tricks
