Mailing List Archive

emerging of silo fails
poseidon ~ # ls -l /etc/make.profile
lrwxrwxrwx 1 root root 62 Sep 12 15:02 /etc/make.profile ->
../usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4
poseidon ~ #

poseidon ~ # cat /proc/cpuinfo
cpu : Fujitsu MB86904
fpu : Lsi Logic/Meiko L64804 or compatible
promlib : Version 3 Revision 2
prom : 2.15
type : sun4m
ncpus probed : 1
ncpus active : 1
BogoMips : 109.36
MMU type : Fujitsu Swift
contexts : 256
nocache total : 1048576
nocache used : 176640
poseidon ~ #
poseidon ~ # gcc -v
Reading specs from /usr/lib/gcc/sparc-unknown-linux-gnu/3.4.6/specs
Configured with:
/var/tmp/portage/sys-devel/gcc-3.4.6-r2/work/gcc-3.4.6/configure
--prefix=/usr --bindir=/usr/sparc-unknown-linux-gnu/gcc-bin/3.4.6
--includedir=/usr/lib/gcc/sparc-unknown-linux-gnu/3.4.6/include
--datadir=/usr/share/gcc-data/sparc-unknown-linux-gnu/3.4.6
--mandir=/usr/share/gcc-data/sparc-unknown-linux-gnu/3.4.6/man
--infodir=/usr/share/gcc-data/sparc-unknown-linux-gnu/3.4.6/info
--with-gxx-include-dir=/usr/lib/gcc/sparc-unknown-linux-gnu/3.4.6/include/g++-v3
--host=sparc-unknown-linux-gnu --build=sparc-unknown-linux-gnu
--disable-altivec --enable-nls --without-included-gettext
--with-system-zlib --disable-checking --disable-werror
--enable-secureplt --disable-libunwind-exceptions --disable-multilib
--disable-libgcj --enable-languages=c,c++,f77 --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
Thread model: posix
gcc version 3.4.6 (Gentoo 3.4.6-r2 p1.5, ssp-3.4.6-1.0, pie-8.7.10)
poseidon ~ #

Here is the log:

Emerging (1 of 55) sys-boot/silo-1.4.13-r1 to /
* silo-1.4.13-r1.tar.bz2 RMD160 ;-)
...
[ ok ]
* silo-1.4.13-r1.tar.bz2 SHA1 ;-)
...
[ ok ]
* silo-1.4.13-r1.tar.bz2 SHA256 ;-)
...
[ ok ]
* silo-1.4.13-r1.tar.bz2 size ;-)
...
[ ok ]
* checking ebuild checksums ;-)
...
[ ok ]
* checking auxfile checksums ;-)
...
[ ok ]
* checking miscfile checksums ;-)
...
[ ok ]
* checking silo-1.4.13-r1.tar.bz2 ;-)
...
[ ok ]
>>> Unpacking source...
>>> Unpacking silo-1.4.13-r1.tar.bz2 to
/var/tmp/portage/sys-boot/silo-1.4.13-r1/work
* Applying silo-1.4.x-noglibc_time.patch
...
[ ok ]
>>> Source unpacked.
>>> Compiling source in
/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13 ...
make[1]: Entering directory
`/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/common'
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c sdiv.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c rem.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c udiv.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c urem.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c jmp.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c printf.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c console.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9 -o prom.o prom.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c tree.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c stringops2.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c stringops1.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c ffs.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c divdi3.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c udivdi3.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector bin2h.c -o bin2h
make[1]: Leaving directory
`/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/common'
make[1]: Entering directory
`/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/first'
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c first.S -o first.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a ultra.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a generic.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a fd.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -DIMGVERSION='"SILO0.99"' -c
ieee32.S
ld -m elf32_sparc -N -Ttext 0x4000 -o first first.o
nm first | grep -v '*ABS*' | sort > first.map
strip first
ld -m elf32_sparc -N -Ttext 0x4000 -o ultra ultra.o
ld -m elf32_sparc -N -Ttext 0x4000 -o generic generic.o
nm generic | grep -v '*ABS*' | sort > generic.map
nm ultra | grep -v '*ABS*' | sort > ultra.map
strip generic
strip ultra
ld -m elf32_sparc -N -Ttext 0x4000 -o fd fd.o
ld -m elf32_sparc -N -Ttext 0x4000 -o ieee32.b ieee32.o
nm fd | grep -v '*ABS*' | sort > fd.map
nm ieee32.b | grep -v '*ABS*' | sort > ieee32.map
strip fd
strip ieee32.b
elftoaout -o first.b first
chmod 644 ieee32.b
PT 0 Entry: Loadable to 0x4000[0x1d8] from 0x74[0x1d8] align 0x4
PT 1 Entry: unknown
printf 'SILO'0.99 | dd of=first.b bs=8 conv=notrunc seek=3 count=1
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*digit_here.*$/#define DIGIT_OFFSET_TMP 0x\2/p' < first.map > first.h
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*letter_here.*$/#define LETTER_OFFSET_TMP 0x\2/p' < first.map >> first.h
1+0 records in
1+0 records out
8 bytes (8 B) copied, 0.001262 s, 6.3 kB/s
dd if=/dev/zero of=first.b bs=4 count=1 seek=127
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*number_here.*$/#define NUMBER_OFFSET_TMP 0x\2/p' < first.map >> first.h
1+0 records in
1+0 records out
4 bytes (4 B) copied, 0.001248 s, 3.2 kB/s
elftoaout -o ultra.b ultra
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*letter_here.*$/#define ULTRA_LETTER_OFFSET_TMP 0x\2/p' < ultra.map >
ultra.h
PT 0 Entry: Loadable to 0x4000[0x1d4] from 0x74[0x1d4] align 0x4
PT 1 Entry: unknown
printf 'SILO'0.99 | dd of=ultra.b bs=8 conv=notrunc seek=3 count=1
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*number_here.*$/#define ULTRA_NUMBER_OFFSET_TMP 0x\2/p' < ultra.map >>
ultra.h
1+0 records in
1+0 records out
8 bytes (8 B) copied, 0.001249 s, 6.4 kB/s
printf '\340' | dd of=ultra.b bs=1 count=1 seek=7 conv=notrunc
elftoaout -o generic.b generic
1+0 records in
1+0 records out
1 byte (1 B) copied, 0.001257 s, 0.8 kB/s
dd if=/dev/zero of=ultra.b bs=4 count=1 seek=127
PT 0 Entry: Loadable to 0x4000[0x400] from 0x200[0x400] align 0x200
PT 1 Entry: unknown
printf 'SILO'0.99 | dd of=generic.b bs=8 conv=notrunc seek=3 count=1
1+0 records in
1+0 records out
4 bytes (4 B) copied, 0.001247 s, 3.2 kB/s
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*digit_here.*$/#define GENERIC_DIGIT_OFFSET_TMP 0x\2/p' < generic.map >
generic.h
1+0 records in
1+0 records out
8 bytes (8 B) copied, 0.001284 s, 6.2 kB/s
printf '\340' | dd of=generic.b bs=1 count=1 seek=7 conv=notrunc
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*letter_here.*$/#define GENERIC_LETTER_OFFSET_TMP 0x\2/p' < generic.map
>> generic.h
1+0 records in
1+0 records out
1 byte (1 B) copied, 0.001252 s, 0.8 kB/s
dd if=/dev/zero of=generic.b bs=4 count=1 seek=255
sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
.*number_here.*$/#define GENERIC_NUMBER_OFFSET_TMP 0x\2/p' < generic.map
>> generic.h
1+0 records in
1+0 records out
4 bytes (4 B) copied, 0.001243 s, 3.2 kB/s
elftoaout -o fd.b fd
PT 0 Entry: Loadable to 0x4000[0x400] from 0x200[0x400] align 0x200
PT 1 Entry: unknown
printf 'SILO'0.99 | dd of=fd.b bs=8 conv=notrunc seek=3 count=1
1+0 records in
1+0 records out
8 bytes (8 B) copied, 0.001248 s, 6.4 kB/s
printf '\340' | dd of=fd.b bs=1 count=1 seek=7 conv=notrunc
1+0 records in
1+0 records out
1 byte (1 B) copied, 0.001245 s, 0.8 kB/s
dd if=/dev/zero of=fd.b bs=4 count=1 seek=255
1+0 records in
1+0 records out
4 bytes (4 B) copied, 0.001241 s, 3.2 kB/s
make[1]: Leaving directory
`/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/first'
make[1]: Entering directory
`/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/second'
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9
-DIMGVERSION='"SILO0.99"' crt0.S
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -DVERSION='"1.4.13"' -c decomp.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -o malloc.o
../common/malloc.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c bmark.S -o bmark.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c main.c -o main.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c cmdline.c -o cmdline.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c disk.c -o disk.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c file.c -o file.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c misc.c -o misc.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c cfg.c -o cfg.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c strtol.c -o strtol.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c ranges.c -o ranges.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a timer.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9 memory.c
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/iom.c -o fs/iom.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/ext2.c -o fs/ext2.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/isofs.c -o fs/isofs.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/romfs.c -o fs/romfs.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/ufs.c -o fs/ufs.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c mul.S -o mul.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c umul.S -o umul.o
sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
-fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
-DLARGE_RELOC=0x380000 -fno-stack-protector -c ls.c -o ls.o
In file included from /usr/include/asm/bitops.h:14,
from /usr/include/linux/fs.h:26,
from ../include/ufs/ufs_fs.h:36,
from fs/ufs.c:36:
/usr/include/asm/system.h:25: error: redeclaration of enumerator `sun4'
../include/promlib.h:12: error: previous definition of 'sun4' was here
/usr/include/asm/system.h:26: error: redeclaration of enumerator `sun4c'
../include/promlib.h:12: error: previous definition of 'sun4c' was here
/usr/include/asm/system.h:27: error: redeclaration of enumerator `sun4m'
../include/promlib.h:12: error: previous definition of 'sun4m' was here
/usr/include/asm/system.h:28: error: redeclaration of enumerator `sun4d'
../include/promlib.h:12: error: previous definition of 'sun4d' was here
/usr/include/asm/system.h:29: error: redeclaration of enumerator `sun4e'
../include/promlib.h:12: error: previous definition of 'sun4e' was here
/usr/include/asm/system.h:30: error: redeclaration of enumerator `sun4u'
../include/promlib.h:12: error: previous definition of 'sun4u' was here
make[1]: *** [fs/ufs.o] Error 1
make[1]: *** Waiting for unfinished jobs....
make[1]: Leaving directory
`/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/second'
make: *** [all] Error 1
*
* ERROR: sys-boot/silo-1.4.13-r1 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* silo-1.4.13-r1.ebuild, line 36: Called die
*
* (no error message)
* If you need support, post the topmost build error, and the call stack
if relevant.
* A complete build log is located at
'/var/tmp/portage/sys-boot/silo-1.4.13-r1/temp/build.log'.
*

* Messages for package sys-boot/silo-1.4.13-r1:

*
* ERROR: sys-boot/silo-1.4.13-r1 failed.
* Call stack:
* ebuild.sh, line 1654: Called dyn_compile
* ebuild.sh, line 990: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* silo-1.4.13-r1.ebuild, line 36: Called die
*
* (no error message)
* If you need support, post the topmost build error, and the call stack
if relevant.
* A complete build log is located at
'/var/tmp/portage/sys-boot/silo-1.4.13-r1/temp/build.log'.
*
poseidon ~ #

--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
Aggelos wrote:
> poseidon ~ # ls -l /etc/make.profile
> lrwxrwxrwx 1 root root 62 Sep 12 15:02 /etc/make.profile ->
> ../usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4

First, sparc32 isn't supported, so when it breaks, you won't get much help.
Second, the 2.4 kernel is mostly unsupported by Gentoo (not just on sparc), so
you're not going to find a lot of help there, either.

> In file included from /usr/include/asm/bitops.h:14,
> from /usr/include/linux/fs.h:26,

What version of linux-headers are you using?

--
Andrew Gaffney http://dev.gentoo.org/~agaffney/
Gentoo Linux Developer Catalyst/Installer + x86 release coordinator
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/17/2007 03:02 PM Andrew Gaffney wrote the following:
> Aggelos wrote:
>> poseidon ~ # ls -l /etc/make.profile lrwxrwxrwx 1 root root 62 Sep 12
>> 15:02 /etc/make.profile ->
>> ../usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4
>
> First, sparc32 isn't supported, so when it breaks, you won't get much
> help. Second, the 2.4 kernel is mostly unsupported by Gentoo (not just
> on sparc), so you're not going to find a lot of help there, either.
>
>> In file included from /usr/include/asm/bitops.h:14,
>> from /usr/include/linux/fs.h:26,
>
> What version of linux-headers are you using?
>


poseidon ~ # equery l | grep head
sys-kernel/linux-headers-2.4.26-r1
poseidon ~ #


--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/17/2007 03:02 PM Andrew Gaffney wrote the following:
> Aggelos wrote:
>> poseidon ~ # ls -l /etc/make.profile lrwxrwxrwx 1 root root 62 Sep 12
>> 15:02 /etc/make.profile ->
>> ../usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4
>
> First, sparc32 isn't supported, so when it breaks, you won't get much
> help. Second, the 2.4 kernel is mostly unsupported by Gentoo (not just
> on sparc), so you're not going to find a lot of help there, either.

What kernel can boot a sparcstation 5, besides 2.4 (and lower)?
Isn't the size of 2.6 prohibitive?

--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Which version of linux-headers are you running? Can you do an `emerge
- -pv linux-headers` and show the output?

I have no experience with SPARC32, but 2.4 is a fine kernel, and not
wholly different (from a user/administrator perspective) than 2.6. You
have to use devfs instead of udev. .:shrug:.

I know a little about running (Hardened) Gentoo Linux 2.4/2.6 on SPARC64,
although I imagine it's not drastically different for the SPARCStation 5.
So let's start with your kernel-headers version and go from there. Also,
if you could post /usr/src/linux/.config and (if possible) any dmesg
output, that'd be great.



brant williams
FCAA CDCA 20BC 3925 D634 F5C4 7420 6784 4DEB 6002



On Mon, 17 Sep 2007, Aggelos wrote:

> Date: Mon, 17 Sep 2007 19:46:21 +0300
> From: Aggelos <marmango@freemail.gr>
> Reply-To: gentoo-sparc@lists.gentoo.org
> To: gentoo-sparc@lists.gentoo.org
> Subject: Re: [gentoo-sparc] emerging of silo fails
>
> on 09/17/2007 03:02 PM Andrew Gaffney wrote the following:
>> Aggelos wrote:
>>> poseidon ~ # ls -l /etc/make.profile lrwxrwxrwx 1 root root 62 Sep 12
>>> 15:02 /etc/make.profile ->
>>> ../usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4
>>
>> First, sparc32 isn't supported, so when it breaks, you won't get much
>> help. Second, the 2.4 kernel is mostly unsupported by Gentoo (not just
>> on sparc), so you're not going to find a lot of help there, either.
>
> What kernel can boot a sparcstation 5, besides 2.4 (and lower)?
> Isn't the size of 2.6 prohibitive?
>
> --
> gentoo-sparc@gentoo.org mailing list
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG7swddCBnhE3rYAIRCETtAKCPZTp9dqiVBKzqJgDcojQwt5mxQQCgkvFd
AOwR3UVBeGuUU0kgTSS+rN0=
=TPY0
-----END PGP SIGNATURE-----
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
I have been running gentoo on a sparc64 since 2004.0 or 2005.0 release.
I know it isn't sparc32, but unless you have some dire need to run a
2.4 kernel I would suggest running a 2.6 kernel. Beside that its
getting increasingly difficult to install gentoo under a 2.4 profile.

I think we all sometimes forget gentoo is a progressive linux and is
always changing. Because of this it is only backward compatible to a
short period of time in the past, like a year. Unlike the other
distributions (red hat/SuSe, etc) where you can install older versions
this distribution sorta requires you to stay somewhat current with the
times. =)

Not saying it is impossible. For instance I run a few machines in 2.4
profile because I use them for an OpenMosix cluster. That has been
removed from portage for months now, but I can still install it because
I copied the 2006.0 profile and all the required files to a portage
overlay directory so I could still use it even when gentoo stopped
supporting it. You may have to do this same technique in order to use
your 2.4 kernel and stuff, and as the another poster has mentioned, 2.4
kernel isn't really supported by gentoo anymore in favor of the 2.6
kernel, which I must add works just fine on sparc64

brant williams wrote:
>
> Which version of linux-headers are you running? Can you do an `emerge -
> -pv linux-headers` and show the output?
>
> I have no experience with SPARC32, but 2.4 is a fine kernel, and not
> wholly different (from a user/administrator perspective) than 2.6. You
> have to use devfs instead of udev. .:shrug:.
>
> I know a little about running (Hardened) Gentoo Linux 2.4/2.6 on
> SPARC64, although I imagine it's not drastically different for the
> SPARCStation 5. So let's start with your kernel-headers version and go
> from there. Also, if you could post /usr/src/linux/.config and (if
> possible) any dmesg output, that'd be great.
>
>
>
> brant williams
> FCAA CDCA 20BC 3925 D634 F5C4 7420 6784 4DEB 6002
>
>
>
> On Mon, 17 Sep 2007, Aggelos wrote:
>
>> Date: Mon, 17 Sep 2007 19:46:21 +0300
>> From: Aggelos <marmango@freemail.gr>
>> Reply-To: gentoo-sparc@lists.gentoo.org
>> To: gentoo-sparc@lists.gentoo.org
>> Subject: Re: [gentoo-sparc] emerging of silo fails
>
>> on 09/17/2007 03:02 PM Andrew Gaffney wrote the following:
>>> Aggelos wrote:
>>>> poseidon ~ # ls -l /etc/make.profile lrwxrwxrwx 1 root root 62 Sep 12
>>>> 15:02 /etc/make.profile ->
>>>> ../usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4
>>>
>>> First, sparc32 isn't supported, so when it breaks, you won't get much
>>> help. Second, the 2.4 kernel is mostly unsupported by Gentoo (not just
>>> on sparc), so you're not going to find a lot of help there, either.
>
>> What kernel can boot a sparcstation 5, besides 2.4 (and lower)?
>> Isn't the size of 2.6 prohibitive?
>
>> --
>> gentoo-sparc@gentoo.org mailing list
>
>
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/17/2007 09:49 PM brant williams wrote the following:
>
> Which version of linux-headers are you running? Can you do an `emerge -
> -pv linux-headers` and show the output?

poseidon ~ # emerge -pv linux-headers

!!! Your current profile is deprecated and not supported anymore.
!!! Please upgrade to the following profile if possible:
default-linux/sparc/sparc32/2006.1

To upgrade do the following steps:

# emerge -n '>=sys-apps/portage-2.0.51'
# cd /etc
# rm make.profile
# ln -s ../usr/portage/profiles/default-linux/sparc/sparc32/2006.1
make.profile

# This profile is deprecated and will be removed on or after November 1,
2007

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild R ] sys-kernel/linux-headers-2.4.26-r1 0 kB

Total: 1 package (1 reinstall), Size of downloads: 0 kB
poseidon ~ #



>
> I have no experience with SPARC32, but 2.4 is a fine kernel, and not
> wholly different (from a user/administrator perspective) than 2.6. You
> have to use devfs instead of udev. .:shrug:.

sys-fs/devfsd-1.3.25-r9

>
> I know a little about running (Hardened) Gentoo Linux 2.4/2.6 on
> SPARC64, although I imagine it's not drastically different for the
> SPARCStation 5. So let's start with your kernel-headers version and go
> from there. Also, if you could post /usr/src/linux/.config and (if
> possible) any dmesg output, that'd be great.

See attached files (compressed).
>

I tried to change to kernel 2.6 (see attached 2.6-config) but, the
resulting image exceeded the bootable size, then I stripped it with:
# strip -R .comment -R .note vmlinux
(according to
http://www.gentoo.org/doc/en/handbook/handbook-sparc.xml?part=1&chap=7)
but still the boot process kept hanging on the kernel loading phase.
(attached

--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/17/2007 10:12 PM Dereck Martin wrote the following:
> I have been running gentoo on a sparc64 since 2004.0 or 2005.0 release.
> I know it isn't sparc32, but unless you have some dire need to run a
> 2.4 kernel I would suggest running a 2.6 kernel.

Please see my reply to Brant Williams' post.

Beside that its
> getting increasingly difficult to install gentoo under a 2.4 profile.
>
> I think we all sometimes forget gentoo is a progressive linux and is
> always changing. Because of this it is only backward compatible to a
> short period of time in the past, like a year. Unlike the other
> distributions (red hat/SuSe, etc) where you can install older versions
> this distribution sorta requires you to stay somewhat current with the
> times. =)

I'm experiencing it first hand ;)

>
> Not saying it is impossible. For instance I run a few machines in 2.4
> profile because I use them for an OpenMosix cluster. That has been
> removed from portage for months now, but I can still install it because
> I copied the 2006.0 profile and all the required files to a portage
> overlay directory so I could still use it even when gentoo stopped
> supporting it. You may have to do this same technique in order to use
> your 2.4 kernel and stuff,

Good idea. ;)
How should I proceed? I guess it must me quite simple but, I would
appreciate your help.

Aggelos.
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/17/2007 10:12 PM Dereck Martin wrote the following:
> I have been running gentoo on a sparc64 since 2004.0 or 2005.0 release.
> I know it isn't sparc32, but unless you have some dire need to run a
> 2.4 kernel I would suggest running a 2.6 kernel.

The kernel size problem is described here:
http://www.gentoo.org/doc/en/handbook/2006.1/handbook-sparc.xml?part=1&chap=7

Quote:

When you're done configuring your kernel, continue with Compiling and
Installing. However, after having compiled the kernel, check its size:

# ls -lh vmlinux
-rw-r--r-- 1 root root 2.4M Oct 25 14:38 vmlinux

If the (uncompressed) size is bigger than 2.5 MB (for Sparc32) or 3.5 MB
(for Sparc64), reconfigure your kernel until it doesn't exceed these
limits. One way of accomplishing this is by having most kernel drivers
compiled as modules. Ignoring this can lead to a non-booting kernel.

Also, if your kernel is just a tad too big, you can try stripping it
using the strip command:

# strip -R .comment -R .note vmlinux
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
Like I said before, I highly recommend you just use the latest profile
for the sparc it will give you a 2.6 kernel and such. I don't know the
reasons why you still need a 2.4 kernel, but if you do still need it
here is how I would go about setting up a overlay for an older profile.

with an overlay, an emerge --sync doesn't wipe out the profiles or
packages so it remains in a static state.

I also highly recommend you read the documentation for creating and
managing ebuilds. Chances are you will need to do "ebuild
filename.ebuild digest" and some other things when doing this method.

I also for warn that this is probably not a desirable method, but if you
really want to keep your system in a old profile that isn't maintained
it is about the only way to do so.

Well if you are looking to preserve an older profile like the recently
removed 2006.0 profile, you have to get a portage snapshot of a 2006.0
profile.

Most of the mirrors have removed the 2006.0 profile, but some haven't
yet. A good example would be


http://gentoo.mirrors.tds.net/gentoo/releases/snapshots/2006.0/portage-20060123.tar.bz2

Download that portage snapshot and perform the following commands

cd /usr/local
mkdir portage
mv /dir-to-downloaded-snapshot/portage-20060123.tar.bz2 .
tar xjf portage-20060123.tar.bz2

this will create a portage structure in /usr/local/portage what gentoo
calls a portage overlay.

Then echo PORTDIR_OVERLAY="/usr/local/portage" >> /etc/make.conf

This will tell portage to recognize the overlay when using emerge and
stuff.

Then create a symlink to the 2006.0 profile in the
/usr/local/portage/profiles directory instead of the regular
/usr/portage/profiles

So it would be like this

rm /etc/make.profile
ln -s /usr/local/portage/profiles/<path to profile> /etc/make.profile

The only draw back is when you try to emerge certain apps that have been
completely removed form the current portage distfiles you'll have to
find the file else where and place it in the distfiles your self. This
is common for patches and such. Most of the time the ebuild has various
locations to retrieve the file, and you will have to cross your fingers
and hope it is in one of the locations. =)

I recommend scouring the gentoo SVN and looking at all ebuild files
including the deleted ones and downloading the required patches by hand
found in the "files" directory of the application package you are
wanting. You will need to do this if an ebuild is unmaintained, like in
the instance of openMosix

In writing this i noticed that the sparc32 2006.1 profile has a 2.4
kernel profile. So you should be good to go at least until next year
probably. Make sure you /etc/make.profile is linked to that profile
first and if it is not then you might resolve a lot of problems by doing
that.

A lot of people do this on a per application basis. Like my self. I
basically just do this for openMosix and delete all the other data out
of the portage overlay except the openMosix stuff and the profile.

Aggelos wrote:
> on 09/17/2007 10:12 PM Dereck Martin wrote the following:
>> I have been running gentoo on a sparc64 since 2004.0 or 2005.0 release.
>> I know it isn't sparc32, but unless you have some dire need to run a
>> 2.4 kernel I would suggest running a 2.6 kernel.
>
> Please see my reply to Brant Williams' post.
>
> Beside that its
>> getting increasingly difficult to install gentoo under a 2.4 profile.
>>
>> I think we all sometimes forget gentoo is a progressive linux and is
>> always changing. Because of this it is only backward compatible to a
>> short period of time in the past, like a year. Unlike the other
>> distributions (red hat/SuSe, etc) where you can install older versions
>> this distribution sorta requires you to stay somewhat current with the
>> times. =)
>
> I'm experiencing it first hand ;)
>
>> Not saying it is impossible. For instance I run a few machines in 2.4
>> profile because I use them for an OpenMosix cluster. That has been
>> removed from portage for months now, but I can still install it because
>> I copied the 2006.0 profile and all the required files to a portage
>> overlay directory so I could still use it even when gentoo stopped
>> supporting it. You may have to do this same technique in order to use
>> your 2.4 kernel and stuff,
>
> Good idea. ;)
> How should I proceed? I guess it must me quite simple but, I would
> appreciate your help.
>
> Aggelos.
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
Thanks a lot for your help Martin. ;)
As I said in previous replies, the only problem I face keeping me from
moving to kernel 2.6 is its un-bootable size for sparc32.

If there is a user running a 2.6 kernel on a sparcstation5 or the like,
I would appreciate it if he can post his .config.

Aggelos.

on 09/18/2007 12:11 AM Dereck Martin wrote the following:
> Like I said before, I highly recommend you just use the latest profile
> for the sparc it will give you a 2.6 kernel and such. I don't know the
> reasons why you still need a 2.4 kernel, but if you do still need it
> here is how I would go about setting up a overlay for an older profile.
>
> with an overlay, an emerge --sync doesn't wipe out the profiles or
> packages so it remains in a static state.
>
> I also highly recommend you read the documentation for creating and
> managing ebuilds. Chances are you will need to do "ebuild
> filename.ebuild digest" and some other things when doing this method.
>
> I also for warn that this is probably not a desirable method, but if you
> really want to keep your system in a old profile that isn't maintained
> it is about the only way to do so.
>
> Well if you are looking to preserve an older profile like the recently
> removed 2006.0 profile, you have to get a portage snapshot of a 2006.0
> profile.
>
> Most of the mirrors have removed the 2006.0 profile, but some haven't
> yet. A good example would be
>
>
> http://gentoo.mirrors.tds.net/gentoo/releases/snapshots/2006.0/portage-20060123.tar.bz2
>
> Download that portage snapshot and perform the following commands
>
> cd /usr/local
> mkdir portage
> mv /dir-to-downloaded-snapshot/portage-20060123.tar.bz2 .
> tar xjf portage-20060123.tar.bz2
>
> this will create a portage structure in /usr/local/portage what gentoo
> calls a portage overlay.
>
> Then echo PORTDIR_OVERLAY="/usr/local/portage" >> /etc/make.conf
>
> This will tell portage to recognize the overlay when using emerge and
> stuff.
>
> Then create a symlink to the 2006.0 profile in the
> /usr/local/portage/profiles directory instead of the regular
> /usr/portage/profiles
>
> So it would be like this
>
> rm /etc/make.profile
> ln -s /usr/local/portage/profiles/<path to profile> /etc/make.profile
>
> The only draw back is when you try to emerge certain apps that have been
> completely removed form the current portage distfiles you'll have to
> find the file else where and place it in the distfiles your self. This
> is common for patches and such. Most of the time the ebuild has various
> locations to retrieve the file, and you will have to cross your fingers
> and hope it is in one of the locations. =)
>
> I recommend scouring the gentoo SVN and looking at all ebuild files
> including the deleted ones and downloading the required patches by hand
> found in the "files" directory of the application package you are
> wanting. You will need to do this if an ebuild is unmaintained, like in
> the instance of openMosix
>
> In writing this i noticed that the sparc32 2006.1 profile has a 2.4
> kernel profile. So you should be good to go at least until next year
> probably. Make sure you /etc/make.profile is linked to that profile
> first and if it is not then you might resolve a lot of problems by doing
> that.
>
> A lot of people do this on a per application basis. Like my self. I
> basically just do this for openMosix and delete all the other data out
> of the portage overlay except the openMosix stuff and the profile.
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


In doing some quick google searches, nothing came up in the way of running
2.6 on a SPARCStation. How about trying this (as previously suggested by
Martin, albeit pretty far down in his post... ;)

rm /etc/make.profile

ln -s /usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4 /etc/make.profile

emerge --sync # if you haven't yet

emerge -uDav world

emerge -av silo


brant williams
FCAA CDCA 20BC 3925 D634 F5C4 7420 6784 4DEB 6002



On Tue, 18 Sep 2007, Aggelos wrote:

> Date: Tue, 18 Sep 2007 00:42:52 +0300
> From: Aggelos <marmango@freemail.gr>
> Reply-To: gentoo-sparc@lists.gentoo.org
> To: gentoo-sparc@lists.gentoo.org
> Subject: Re: [gentoo-sparc] emerging of silo fails
>
> Thanks a lot for your help Martin. ;)
> As I said in previous replies, the only problem I face keeping me from
> moving to kernel 2.6 is its un-bootable size for sparc32.
>
> If there is a user running a 2.6 kernel on a sparcstation5 or the like,
> I would appreciate it if he can post his .config.
>
> Aggelos.
>
> on 09/18/2007 12:11 AM Dereck Martin wrote the following:
>> Like I said before, I highly recommend you just use the latest profile
>> for the sparc it will give you a 2.6 kernel and such. I don't know the
>> reasons why you still need a 2.4 kernel, but if you do still need it
>> here is how I would go about setting up a overlay for an older profile.
>>
>> with an overlay, an emerge --sync doesn't wipe out the profiles or
>> packages so it remains in a static state.
>>
>> I also highly recommend you read the documentation for creating and
>> managing ebuilds. Chances are you will need to do "ebuild
>> filename.ebuild digest" and some other things when doing this method.
>>
>> I also for warn that this is probably not a desirable method, but if you
>> really want to keep your system in a old profile that isn't maintained
>> it is about the only way to do so.
>>
>> Well if you are looking to preserve an older profile like the recently
>> removed 2006.0 profile, you have to get a portage snapshot of a 2006.0
>> profile.
>>
>> Most of the mirrors have removed the 2006.0 profile, but some haven't
>> yet. A good example would be
>>
>>
>> http://gentoo.mirrors.tds.net/gentoo/releases/snapshots/2006.0/portage-20060123.tar.bz2
>>
>> Download that portage snapshot and perform the following commands
>>
>> cd /usr/local
>> mkdir portage
>> mv /dir-to-downloaded-snapshot/portage-20060123.tar.bz2 .
>> tar xjf portage-20060123.tar.bz2
>>
>> this will create a portage structure in /usr/local/portage what gentoo
>> calls a portage overlay.
>>
>> Then echo PORTDIR_OVERLAY="/usr/local/portage" >> /etc/make.conf
>>
>> This will tell portage to recognize the overlay when using emerge and
>> stuff.
>>
>> Then create a symlink to the 2006.0 profile in the
>> /usr/local/portage/profiles directory instead of the regular
>> /usr/portage/profiles
>>
>> So it would be like this
>>
>> rm /etc/make.profile
>> ln -s /usr/local/portage/profiles/<path to profile> /etc/make.profile
>>
>> The only draw back is when you try to emerge certain apps that have been
>> completely removed form the current portage distfiles you'll have to
>> find the file else where and place it in the distfiles your self. This
>> is common for patches and such. Most of the time the ebuild has various
>> locations to retrieve the file, and you will have to cross your fingers
>> and hope it is in one of the locations. =)
>>
>> I recommend scouring the gentoo SVN and looking at all ebuild files
>> including the deleted ones and downloading the required patches by hand
>> found in the "files" directory of the application package you are
>> wanting. You will need to do this if an ebuild is unmaintained, like in
>> the instance of openMosix
>>
>> In writing this i noticed that the sparc32 2006.1 profile has a 2.4
>> kernel profile. So you should be good to go at least until next year
>> probably. Make sure you /etc/make.profile is linked to that profile
>> first and if it is not then you might resolve a lot of problems by doing
>> that.
>>
>> A lot of people do this on a per application basis. Like my self. I
>> basically just do this for openMosix and delete all the other data out
>> of the portage overlay except the openMosix stuff and the profile.
> --
> gentoo-sparc@gentoo.org mailing list
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG7v8qdCBnhE3rYAIRCBPkAJ4i82lHP3wqWYQ0Ut/Ahv4V248YtQCffjHK
nvjvccP/Kw7SO15+gWSRITE=
=E5h5
-----END PGP SIGNATURE-----
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/18/2007 01:26 AM brant williams wrote the following:
>
> In doing some quick google searches, nothing came up in the way of
> running 2.6 on a SPARCStation. How about trying this (as previously
> suggested by Martin, albeit pretty far down in his post... ;)
>
> rm /etc/make.profile
>
> ln -s /usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4
> /etc/make.profile
>
> emerge --sync # if you haven't yet
>
> emerge -uDav world
>
> emerge -av silo
>
>
Well, if you look at the top of my original post, the profile I have
been using is already the 2006.1/2.4 ;)
Aggelos.
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256


Yeah, sorry, I'm a dufus. Re-read your original message...

Do you have 'gentoolkit' installed? If so, you might want to run
`revdep-rebuild` which will scan the linking on your system and re-emerge
any needed packages.


brant williams
FCAA CDCA 20BC 3925 D634 F5C4 7420 6784 4DEB 6002



On Tue, 18 Sep 2007, Aggelos wrote:

> Date: Tue, 18 Sep 2007 02:06:00 +0300
> From: Aggelos <marmango@freemail.gr>
> Reply-To: gentoo-sparc@lists.gentoo.org
> To: gentoo-sparc@lists.gentoo.org
> Subject: Re: [gentoo-sparc] emerging of silo fails
>
> Let me clarify that I have a working installation of silo, but the above
> problem came up as I am trying to do a "emerge -e world".
> I had run a "emerge --depclean" and various stuff was removed, maybe
> something necessary for the emerge of silo.
> Here is the relevan section from /var/log/emerge.log
>
> 1189871561: *** emerge --ask --verbose depclean
> 1189871572: >>> depclean
> 1189871654: === Unmerging... (sys-devel/automake-1.8.5-r3)
> 1189871686: >>> unmerge success: sys-devel/automake-1.8.5-r3
> 1189871686: === Unmerging... (sys-devel/automake-1.5)
> 1189871717: >>> unmerge success: sys-devel/automake-1.5
> 1189871717: === Unmerging... (sys-devel/automake-1.6.3)
> 1189871747: >>> unmerge success: sys-devel/automake-1.6.3
> 1189871747: === Unmerging... (sys-devel/automake-1.4_p6)
> 1189871777: >>> unmerge success: sys-devel/automake-1.4_p6
> 1189871777: === Unmerging... (sys-devel/automake-1.9.6-r2)
> 1189871808: >>> unmerge success: sys-devel/automake-1.9.6-r2
> 1189871808: === Unmerging... (sys-devel/automake-1.7.9-r1)
> 1189871839: >>> unmerge success: sys-devel/automake-1.7.9-r1
> 1189871839: === Unmerging... (dev-util/unifdef-1.20)
> 1189871859: >>> unmerge success: dev-util/unifdef-1.20
> 1189871859: === Unmerging... (sys-libs/pwdb-0.62)
> 1189871903: >>> unmerge success: sys-libs/pwdb-0.62
> 1189871903: === Unmerging... (sys-devel/autoconf-2.13)
> 1189871932: >>> unmerge success: sys-devel/autoconf-2.13
> 1189871932: === Unmerging... (sys-libs/db-4.2.52_p2-r1)
> 1189871969: >>> unmerge success: sys-libs/db-4.2.52_p2-r1
> 1189871969: *** exiting successfully.
> 1189872074: *** terminating.
>
> I by-passed with "emerge --resume --skipfirst" and so far so good.
> --
> gentoo-sparc@gentoo.org mailing list
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFG7wg3dCBnhE3rYAIRCChtAJ49cua0n1mgbt1mvXR+n0ZwzHORMgCgpGQ3
WzGS7Gfx39pzumXiCiVNBA4=
=gGPJ
-----END PGP SIGNATURE-----
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
Let me clarify that I have a working installation of silo, but the above
problem came up as I am trying to do a "emerge -e world".
I had run a "emerge --depclean" and various stuff was removed, maybe
something necessary for the emerge of silo.
Here is the relevan section from /var/log/emerge.log

1189871561: *** emerge --ask --verbose depclean
1189871572: >>> depclean
1189871654: === Unmerging... (sys-devel/automake-1.8.5-r3)
1189871686: >>> unmerge success: sys-devel/automake-1.8.5-r3
1189871686: === Unmerging... (sys-devel/automake-1.5)
1189871717: >>> unmerge success: sys-devel/automake-1.5
1189871717: === Unmerging... (sys-devel/automake-1.6.3)
1189871747: >>> unmerge success: sys-devel/automake-1.6.3
1189871747: === Unmerging... (sys-devel/automake-1.4_p6)
1189871777: >>> unmerge success: sys-devel/automake-1.4_p6
1189871777: === Unmerging... (sys-devel/automake-1.9.6-r2)
1189871808: >>> unmerge success: sys-devel/automake-1.9.6-r2
1189871808: === Unmerging... (sys-devel/automake-1.7.9-r1)
1189871839: >>> unmerge success: sys-devel/automake-1.7.9-r1
1189871839: === Unmerging... (dev-util/unifdef-1.20)
1189871859: >>> unmerge success: dev-util/unifdef-1.20
1189871859: === Unmerging... (sys-libs/pwdb-0.62)
1189871903: >>> unmerge success: sys-libs/pwdb-0.62
1189871903: === Unmerging... (sys-devel/autoconf-2.13)
1189871932: >>> unmerge success: sys-devel/autoconf-2.13
1189871932: === Unmerging... (sys-libs/db-4.2.52_p2-r1)
1189871969: >>> unmerge success: sys-libs/db-4.2.52_p2-r1
1189871969: *** exiting successfully.
1189872074: *** terminating.

I by-passed with "emerge --resume --skipfirst" and so far so good.
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/18/2007 02:05 AM brant williams wrote the following:
>
> Yeah, sorry, I'm a dufus. Re-read your original message...
>
> Do you have 'gentoolkit' installed? If so, you might want to run
> `revdep-rebuild` which will scan the linking on your system and
> re-emerge any needed packages.
>
Doing so now in parallel to "emerge -e world"
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
I ran into this problem some time ago on my Ultra 10 running a 2.4
kernel/profile. I didn't keep any notes, so I'm not 100% sure about
this, but if I recall I came to the conclusion that the 2.4 headers
were the problem and there was just no mask in the 2.4 profile to
prevent the newer, incompatible silo version from emerging. Since the
old one worked fine I just masked all newer versions manually and let
it be.

On 9/17/07, Aggelos <marmango@freemail.gr> wrote:
> poseidon ~ # ls -l /etc/make.profile
> lrwxrwxrwx 1 root root 62 Sep 12 15:02 /etc/make.profile ->
> ../usr/portage/profiles/default-linux/sparc/sparc32/2006.1/2.4
> poseidon ~ #
>
> poseidon ~ # cat /proc/cpuinfo
> cpu : Fujitsu MB86904
> fpu : Lsi Logic/Meiko L64804 or compatible
> promlib : Version 3 Revision 2
> prom : 2.15
> type : sun4m
> ncpus probed : 1
> ncpus active : 1
> BogoMips : 109.36
> MMU type : Fujitsu Swift
> contexts : 256
> nocache total : 1048576
> nocache used : 176640
> poseidon ~ #
> poseidon ~ # gcc -v
> Reading specs from /usr/lib/gcc/sparc-unknown-linux-gnu/3.4.6/specs
> Configured with:
> /var/tmp/portage/sys-devel/gcc-3.4.6-r2/work/gcc-3.4.6/configure
> --prefix=/usr --bindir=/usr/sparc-unknown-linux-gnu/gcc-bin/3.4.6
> --includedir=/usr/lib/gcc/sparc-unknown-linux-gnu/3.4.6/include
> --datadir=/usr/share/gcc-data/sparc-unknown-linux-gnu/3.4.6
> --mandir=/usr/share/gcc-data/sparc-unknown-linux-gnu/3.4.6/man
> --infodir=/usr/share/gcc-data/sparc-unknown-linux-gnu/3.4.6/info
> --with-gxx-include-dir=/usr/lib/gcc/sparc-unknown-linux-gnu/3.4.6/include/g++-v3
> --host=sparc-unknown-linux-gnu --build=sparc-unknown-linux-gnu
> --disable-altivec --enable-nls --without-included-gettext
> --with-system-zlib --disable-checking --disable-werror
> --enable-secureplt --disable-libunwind-exceptions --disable-multilib
> --disable-libgcj --enable-languages=c,c++,f77 --enable-shared
> --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
> Thread model: posix
> gcc version 3.4.6 (Gentoo 3.4.6-r2 p1.5, ssp-3.4.6-1.0, pie-8.7.10)
> poseidon ~ #
>
> Here is the log:
>
> Emerging (1 of 55) sys-boot/silo-1.4.13-r1 to /
> * silo-1.4.13-r1.tar.bz2 RMD160 ;-)
> ...
> [ ok ]
> * silo-1.4.13-r1.tar.bz2 SHA1 ;-)
> ...
> [ ok ]
> * silo-1.4.13-r1.tar.bz2 SHA256 ;-)
> ...
> [ ok ]
> * silo-1.4.13-r1.tar.bz2 size ;-)
> ...
> [ ok ]
> * checking ebuild checksums ;-)
> ...
> [ ok ]
> * checking auxfile checksums ;-)
> ...
> [ ok ]
> * checking miscfile checksums ;-)
> ...
> [ ok ]
> * checking silo-1.4.13-r1.tar.bz2 ;-)
> ...
> [ ok ]
> >>> Unpacking source...
> >>> Unpacking silo-1.4.13-r1.tar.bz2 to
> /var/tmp/portage/sys-boot/silo-1.4.13-r1/work
> * Applying silo-1.4.x-noglibc_time.patch
> ...
> [ ok ]
> >>> Source unpacked.
> >>> Compiling source in
> /var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13 ...
> make[1]: Entering directory
> `/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/common'
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c sdiv.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c rem.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c udiv.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c urem.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c jmp.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c printf.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c console.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9 -o prom.o prom.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c tree.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c stringops2.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c stringops1.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c ffs.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c divdi3.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c udivdi3.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector bin2h.c -o bin2h
> make[1]: Leaving directory
> `/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/common'
> make[1]: Entering directory
> `/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/first'
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c first.S -o first.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a ultra.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a generic.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a fd.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -DIMGVERSION='"SILO0.99"' -c
> ieee32.S
> ld -m elf32_sparc -N -Ttext 0x4000 -o first first.o
> nm first | grep -v '*ABS*' | sort > first.map
> strip first
> ld -m elf32_sparc -N -Ttext 0x4000 -o ultra ultra.o
> ld -m elf32_sparc -N -Ttext 0x4000 -o generic generic.o
> nm generic | grep -v '*ABS*' | sort > generic.map
> nm ultra | grep -v '*ABS*' | sort > ultra.map
> strip generic
> strip ultra
> ld -m elf32_sparc -N -Ttext 0x4000 -o fd fd.o
> ld -m elf32_sparc -N -Ttext 0x4000 -o ieee32.b ieee32.o
> nm fd | grep -v '*ABS*' | sort > fd.map
> nm ieee32.b | grep -v '*ABS*' | sort > ieee32.map
> strip fd
> strip ieee32.b
> elftoaout -o first.b first
> chmod 644 ieee32.b
> PT 0 Entry: Loadable to 0x4000[0x1d8] from 0x74[0x1d8] align 0x4
> PT 1 Entry: unknown
> printf 'SILO'0.99 | dd of=first.b bs=8 conv=notrunc seek=3 count=1
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*digit_here.*$/#define DIGIT_OFFSET_TMP 0x\2/p' < first.map > first.h
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*letter_here.*$/#define LETTER_OFFSET_TMP 0x\2/p' < first.map >> first.h
> 1+0 records in
> 1+0 records out
> 8 bytes (8 B) copied, 0.001262 s, 6.3 kB/s
> dd if=/dev/zero of=first.b bs=4 count=1 seek=127
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*number_here.*$/#define NUMBER_OFFSET_TMP 0x\2/p' < first.map >> first.h
> 1+0 records in
> 1+0 records out
> 4 bytes (4 B) copied, 0.001248 s, 3.2 kB/s
> elftoaout -o ultra.b ultra
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*letter_here.*$/#define ULTRA_LETTER_OFFSET_TMP 0x\2/p' < ultra.map >
> ultra.h
> PT 0 Entry: Loadable to 0x4000[0x1d4] from 0x74[0x1d4] align 0x4
> PT 1 Entry: unknown
> printf 'SILO'0.99 | dd of=ultra.b bs=8 conv=notrunc seek=3 count=1
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*number_here.*$/#define ULTRA_NUMBER_OFFSET_TMP 0x\2/p' < ultra.map >>
> ultra.h
> 1+0 records in
> 1+0 records out
> 8 bytes (8 B) copied, 0.001249 s, 6.4 kB/s
> printf '\340' | dd of=ultra.b bs=1 count=1 seek=7 conv=notrunc
> elftoaout -o generic.b generic
> 1+0 records in
> 1+0 records out
> 1 byte (1 B) copied, 0.001257 s, 0.8 kB/s
> dd if=/dev/zero of=ultra.b bs=4 count=1 seek=127
> PT 0 Entry: Loadable to 0x4000[0x400] from 0x200[0x400] align 0x200
> PT 1 Entry: unknown
> printf 'SILO'0.99 | dd of=generic.b bs=8 conv=notrunc seek=3 count=1
> 1+0 records in
> 1+0 records out
> 4 bytes (4 B) copied, 0.001247 s, 3.2 kB/s
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*digit_here.*$/#define GENERIC_DIGIT_OFFSET_TMP 0x\2/p' < generic.map >
> generic.h
> 1+0 records in
> 1+0 records out
> 8 bytes (8 B) copied, 0.001284 s, 6.2 kB/s
> printf '\340' | dd of=generic.b bs=1 count=1 seek=7 conv=notrunc
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*letter_here.*$/#define GENERIC_LETTER_OFFSET_TMP 0x\2/p' < generic.map
> >> generic.h
> 1+0 records in
> 1+0 records out
> 1 byte (1 B) copied, 0.001252 s, 0.8 kB/s
> dd if=/dev/zero of=generic.b bs=4 count=1 seek=255
> sed -n 's/^\(000000000000\|0000\)4\([0-9a-f][0-9a-f][0-9a-f]\)
> .*number_here.*$/#define GENERIC_NUMBER_OFFSET_TMP 0x\2/p' < generic.map
> >> generic.h
> 1+0 records in
> 1+0 records out
> 4 bytes (4 B) copied, 0.001243 s, 3.2 kB/s
> elftoaout -o fd.b fd
> PT 0 Entry: Loadable to 0x4000[0x400] from 0x200[0x400] align 0x200
> PT 1 Entry: unknown
> printf 'SILO'0.99 | dd of=fd.b bs=8 conv=notrunc seek=3 count=1
> 1+0 records in
> 1+0 records out
> 8 bytes (8 B) copied, 0.001248 s, 6.4 kB/s
> printf '\340' | dd of=fd.b bs=1 count=1 seek=7 conv=notrunc
> 1+0 records in
> 1+0 records out
> 1 byte (1 B) copied, 0.001245 s, 0.8 kB/s
> dd if=/dev/zero of=fd.b bs=4 count=1 seek=255
> 1+0 records in
> 1+0 records out
> 4 bytes (4 B) copied, 0.001241 s, 3.2 kB/s
> make[1]: Leaving directory
> `/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/first'
> make[1]: Entering directory
> `/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/second'
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9
> -DIMGVERSION='"SILO0.99"' crt0.S
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -DVERSION='"1.4.13"' -c decomp.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -o malloc.o
> ../common/malloc.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c bmark.S -o bmark.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c main.c -o main.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c cmdline.c -o cmdline.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c disk.c -o disk.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c file.c -o file.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c misc.c -o misc.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c cfg.c -o cfg.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c strtol.c -o strtol.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c ranges.c -o ranges.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9a timer.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c -Wa,-Av9 memory.c
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/iom.c -o fs/iom.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/ext2.c -o fs/ext2.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/isofs.c -o fs/isofs.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/romfs.c -o fs/romfs.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c fs/ufs.c -o fs/ufs.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c mul.S -o mul.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c umul.S -o umul.o
> sparc-unknown-linux-gnu-gcc -Os -Wall -I. -I../include
> -fomit-frame-pointer -fno-strict-aliasing -DSMALL_RELOC=0x280000
> -DLARGE_RELOC=0x380000 -fno-stack-protector -c ls.c -o ls.o
> In file included from /usr/include/asm/bitops.h:14,
> from /usr/include/linux/fs.h:26,
> from ../include/ufs/ufs_fs.h:36,
> from fs/ufs.c:36:
> /usr/include/asm/system.h:25: error: redeclaration of enumerator `sun4'
> ../include/promlib.h:12: error: previous definition of 'sun4' was here
> /usr/include/asm/system.h:26: error: redeclaration of enumerator `sun4c'
> ../include/promlib.h:12: error: previous definition of 'sun4c' was here
> /usr/include/asm/system.h:27: error: redeclaration of enumerator `sun4m'
> ../include/promlib.h:12: error: previous definition of 'sun4m' was here
> /usr/include/asm/system.h:28: error: redeclaration of enumerator `sun4d'
> ../include/promlib.h:12: error: previous definition of 'sun4d' was here
> /usr/include/asm/system.h:29: error: redeclaration of enumerator `sun4e'
> ../include/promlib.h:12: error: previous definition of 'sun4e' was here
> /usr/include/asm/system.h:30: error: redeclaration of enumerator `sun4u'
> ../include/promlib.h:12: error: previous definition of 'sun4u' was here
> make[1]: *** [fs/ufs.o] Error 1
> make[1]: *** Waiting for unfinished jobs....
> make[1]: Leaving directory
> `/var/tmp/portage/sys-boot/silo-1.4.13-r1/work/silo-1.4.13/second'
> make: *** [all] Error 1
> *
> * ERROR: sys-boot/silo-1.4.13-r1 failed.
> * Call stack:
> * ebuild.sh, line 1654: Called dyn_compile
> * ebuild.sh, line 990: Called qa_call 'src_compile'
> * ebuild.sh, line 44: Called src_compile
> * silo-1.4.13-r1.ebuild, line 36: Called die
> *
> * (no error message)
> * If you need support, post the topmost build error, and the call stack
> if relevant.
> * A complete build log is located at
> '/var/tmp/portage/sys-boot/silo-1.4.13-r1/temp/build.log'.
> *
>
> * Messages for package sys-boot/silo-1.4.13-r1:
>
> *
> * ERROR: sys-boot/silo-1.4.13-r1 failed.
> * Call stack:
> * ebuild.sh, line 1654: Called dyn_compile
> * ebuild.sh, line 990: Called qa_call 'src_compile'
> * ebuild.sh, line 44: Called src_compile
> * silo-1.4.13-r1.ebuild, line 36: Called die
> *
> * (no error message)
> * If you need support, post the topmost build error, and the call stack
> if relevant.
> * A complete build log is located at
> '/var/tmp/portage/sys-boot/silo-1.4.13-r1/temp/build.log'.
> *
> poseidon ~ #
>
> --
> gentoo-sparc@gentoo.org mailing list
>
>

--
Aaron Mavrinac
www.mavrinac.com

PGP Public Key: http://www.mavrinac.com/pgp.asc
--
gentoo-sparc@gentoo.org mailing list
Re: emerging of silo fails [ In reply to ]
on 09/20/2007 07:53 PM Aaron Mavrinac wrote the following:
> I ran into this problem some time ago on my Ultra 10 running a 2.4
> kernel/profile. I didn't keep any notes, so I'm not 100% sure about
> this, but if I recall I came to the conclusion that the 2.4 headers
> were the problem and there was just no mask in the 2.4 profile to
> prevent the newer, incompatible silo version from emerging. Since the
> old one worked fine I just masked all newer versions manually and let
> it be.
>

I did the same:
I masked silo-1.4.13-r1 and tried silo-1.4.13 and it compiled just fine ;-)

Thanks.
Aggelos.
--
gentoo-sparc@gentoo.org mailing list