View previous topic :: View next topic |
Author |
Message |
Blademan Developer
Joined: 05 Oct 2002 Posts: 116
|
Posted: Mon Jan 20, 2003 6:58 am Post subject: emerge silo-1.2.6 fails Exitcode 2 |
|
|
OK, so I managed to get going. Silo on the emerge system during install fails as follows:
Code: | dd if=/dev/zero of=first.b bs=4 count=1 seek=127
dd: opening `/dev/zero':No such file or directory
make[1]:**** [first.b] Error 1
make[1]:*** Waiting for unfinished jobs....
strip fd
make[1]:***Waiting for unfinished jobs....
strip ieee32.b
make[1]: Leaving drectory `/var/tmp/portage/silo-1.2.6/worl/silo-1.2.6/first'
make: *** [all] Error 1
!!! Error: sys-apps/silo-1.2.6 failed
!!! Function src_compile, Line 1, Exitcode 2
!!! (no error message) |
My make.conf is:
Code: | CHOST=sparc-unknown-linux-gnu
CFLAGS="-mcpu=ultrasparc -mtune=ultrasparc -O3 -pipe -fomit-frame-pointer"
or
CFLAGS"-mcpu=v8 -mtune=v9 -O2 -pipe
same CXXFLAGS, or "-O2 -pipe"
ACCEPT_KEYWORDS="sparc"
MAKEOPTS="-j3" |
This is on a U60, 868MB ram |
|
Back to top |
|
|
Kumba Developer
Joined: 16 Jul 2002 Posts: 393 Location: Sigma 957
|
Posted: Wed Jan 22, 2003 8:31 pm Post subject: |
|
|
It appears the error is due to your filesystem lacking a zero device, /dev/zero, which is being used by silo.
Run "ls -l /dev" first to see if /dev/zero already exists, and is a "character" device, mode 666 (crw-rw-rw-) with major 1 and minor 5. It should look like this:
Code: | crw-rw-rw- 1 root root 1, 5 Dec 31 1969 zero |
If it doesn't exist, you might try executing the following commands to fix it (although devfsd should create /dev/zero)
Code: | cd /dev
mknod --mode=666 zero c 1 5 |
Run "ls -l" afterwards to see if /dev/zero was successfully created, and then try silo again.
--Kumba _________________ "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic |
|
Back to top |
|
|
Blademan Developer
Joined: 05 Oct 2002 Posts: 116
|
Posted: Thu Jan 23, 2003 12:04 am Post subject: |
|
|
Kumba,
Thank you. That seemed to make silo happy and silo-1.2.6 merged.
Should this be submitted to bugs.gentoo? I say that because this was during a clean install. I used:
1.1a iso
1.4_rc2 stage2 tarball
new filesystems
Thanks,
Joe |
|
Back to top |
|
|
Kumba Developer
Joined: 16 Jul 2002 Posts: 393 Location: Sigma 957
|
Posted: Thu Jan 23, 2003 7:12 am Post subject: |
|
|
I dunno, I'd check your kernel configuration. Gentoo uses devfs to populate the /dev directory with a device tree. Check to see if you added the following in your kernel config:
Code: | [*] /dev file system support (EXPERIMENTAL)
[*] Automatically mount at boot |
By mounting it at boot, the kernel itself should create basic entries like null, zero, and so on. I don't know too much about devfs, so I could be off on this, but that may be the cause of your problem.
--Kumba _________________ "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic |
|
Back to top |
|
|
Blademan Developer
Joined: 05 Oct 2002 Posts: 116
|
Posted: Tue Jan 28, 2003 5:20 pm Post subject: |
|
|
FYI, this is during the initial install. Where/what file should I check the kernel config? |
|
Back to top |
|
|
Kumba Developer
Joined: 16 Jul 2002 Posts: 393 Location: Sigma 957
|
Posted: Wed Jan 29, 2003 7:12 pm Post subject: |
|
|
Hmm, during the initial install?...Odd. I dunno about that. All I know is the kernel, if told to, will mount a partially filled /dev on boot. devfsd fills in the rest of the /dev entries (most are symlinks to devices the kernel already setup). Maybe this is a bug? I installed linux on my sparc system many months ago, and I didn't have a problem then. Of course, at that time, I used a debian netboot image to get everything setup as a chroot environment, and then just straight booted off the drive once all was complete.
--Kumba _________________ "The past tempts us, the present confuses us, the future frightens us. And our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic |
|
Back to top |
|
|
peaceful Apprentice
Joined: 06 Jun 2003 Posts: 287 Location: Utah
|
Posted: Fri May 14, 2004 10:46 pm Post subject: Same Problem |
|
|
I encountered the exact same problem -- no /dev/zero.
This was using a tftp/netboot image from 2004.1.
Creating /dev/zero with the 'mknod' command fixed it -- thanks! (I never would have figured that out). |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|