🚀 go-pugleaf

In article <4bb61k$255@segfault.monkeys.com>, rfg@monkeys.com (Ronald F. Guilmette) writes:

[....]

|> As it turns out, this is a NOT a problem with either GCC or the assembler
|> or the linker.  It has been reported to me that the problem is due to
|> a rather serious bug in the linux C library (ELF version).  It apparently
|> fails to properly export its symbols as ELF ``weak linkage'' symbols
|> (as all good ELF libc libraries should).
|> 
|> I have been assured (by H.J. Lu, maintainer of the linux C library) that
|> this problem in the library will be fixed in the next release of the
|> library.  For the time being, the simplest workaround is just to avoid
|> using the names of libc library functions in your own programs (e.g.
|> as names of your own global variables or functions).

Libc 5.2.18 fixes some symbols, sync is one of them. But there are so many
to go. Also I'd like to support MT in one library without adding much
overhead to single thread programs. It is kind of very complicated.
On top of these, I am in the middle of relocating. I don't know when I
can resume working on libc :-(.

H.J.