On 11/23/07, Miklos Szeredi <[EMAIL PROTECTED]> wrote:
> The problem is that the linker somehow gets confused by these
> versioned symbols and resolves them wrongly.  And _that_ is a bug in
> the linker in uclibc (and other systems where this happens).

The linker is not the issue, as the loading is done at runtime.
But if you sure there is a problem with some binutil, please file a
bug, you can describe this better than I can.
I think the problem is with uclibc, which need to scan for latest
entry points only. But this will make it more complex/larger than it
is.

Also please notice that the fact you support backward compatibility in
fuse makes your output larger... So maybe just add
--enable-backward-compatibility to your configure script will solve
all this... Usually this should not be enabled at all.

Regards,
Alon.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
ntfs-3g-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ntfs-3g-devel

Reply via email to