Re: silo problem

[Andreas Jaeger <aj@arthur.rhein-neckar.de>]

>>>>> Davide Barbieri writes:

Davide> Tom Dyas wrote:
>> > 	I'm still trying to have a silo working with glibc.
>> > 
>> > I had some problems, with some assembler code.
>> > 
>> > There is a file, called jmp.S which defines the symbol
>> > __setjmp, which is also defined in /usr/lib/libc.a
>> > 
>> > So, when it is time to link silo, I had this error:
>> > /usr/lib/libc.a(setjmp.o): In function `_setjmp':
>> > setjmp.o(.text+0x0): multiple definition of `__setjmp'
>> > jmp.o(.text+0x0): first defined here
>> > make: *** [second] Error 1
>> 
>> The problem is that the second stage bootloader links with libc to bring
>> in some minor functions like the strcmp and such. Ideally, it should be
>> linked without libc just like the kernel. 
> [...]
Davide> BTW, isn't __setjmp already defined also in libc5?
Davide> (I haven't a libc5 system here)

All symbols starting with a underscore ("_") are reserved for internal 
use of the C library by the ISO C standard. __setjmp might be defined
in libc5 but that's not relevant here. The bug is that silo uses a
_reserved_ identifier! 

Either use setjmp completly from the C library or don't use the
library at all.

If you need all the str* function, just get them from glibc and
include them in silo. The sources are under the LGPL.

Andreas
-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@alma.student.uni-kl.de


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-sparc-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .