> > However why would you want another one? Either stay clear of libc (keep it static),
> > or use the vendor supplied one.
>
> My program uses a {$LINKLIB c} (or to be more precise... the inet unit),
> but I want to use uclibc as the program shuld run on an linux network
> router (--> www.fli4l.de ) and it uses uclibc as standart libc.
As said there are two possibilities:
- not use libc, and patch inet to use syscalls.
- fix the startup code for uclibc. (make a diff between the glibc one and the FPC one,
and try to incorporate those differences into the uclibc one)
Startup code fixing is not funny, I suggest you go with the syscall method.
_______________________________________________
fpc-pascal maillist - [EMAIL PROTECTED]
http://lists.freepascal.org/mailman/listinfo/fpc-pascal
