Mailing List Archive

I recently installed 2006.1 on a netra T1, then performed a --deep --update
world.

I followed up with a revdep-rebuild, which unmerged silo, so I tried to
re-emerge it.

Now, I'm getting the following error when trying to emerge SILO...

---
ld -m elf32_sparc -N -Ttext 0x280000 -Bstatic -o second crt0.o decomp.o
../common/console.o ../common/printf.o malloc.o ../common/jmp.o
../common/prom.o ../common/tree.o ../common/urem.o ../common/udiv.o
../common/stringops1.o ../common/ffs.o ../common/divdi3.o
../common/udivdi3.o bmark.o main.o cmdline.o disk.o file.o misc.o cfg.o
strtol.o ranges.o timer.o memory.o fs/libfs.a mul.o ../common/rem.o
../common/sdiv.o umul.o ../common/stringops2.o ls.o muldi3.o -lext2fs mark.o
/usr/lib/libext2fs.a(closefs.o): In function `ext2fs_super_and_bgd_loc':
closefs.c:(.text+0x270): undefined reference to `__umoddi3'
make[1]: *** [second] Error 1
make[1]: Leaving directory
`/var/tmp/portage/sys-boot/silo-1.4.13/work/silo-1.4.13/second'
make: *** [all] Error 1

!!! ERROR: sys-boot/silo-1.4.13 failed.
Call stack:
ebuild.sh, line 1614: Called dyn_compile
ebuild.sh, line 971: Called qa_call 'src_compile'
environment, line 3307: Called src_compile
silo-1.4.13.ebuild, line 40: 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/temp/build.log'.
----------

Any ideas?