This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] PE direct linking to dlls, accept any filename.
- From: Christopher Faylor <cgf-use-the-mailinglist-please at sourceware dot org>
- To: 'Pedro Alves' <pedro_alves at portugalmail dot pt>, 'Binutils' <binutils at sourceware dot org>
- Date: Sun, 17 Dec 2006 01:05:21 -0500
- Subject: Re: [PATCH] PE direct linking to dlls, accept any filename.
- References: <458414F4.4040202@portugalmail.pt> <000001c7217c$89ce2bc0$3a4861cb@anykey>
On Sun, Dec 17, 2006 at 02:41:55PM +1300, Danny Smith wrote:
>>
>> This is exactly what happens when linking with the unpatched ld.
>> Don't you have an ld.exe link/copy to ../../ld-new.exe in
>> /develop/cvs/binutils/build/ld/tmpdir/ld/ ?
>> If there isn't one, then the one in the system will be picked up.
>> Maybe I missed something in direct.exp?
>> This is surelly a test bug, since my manual testing was successful
>> once I copied ld-new.exe to tmpdir/ld/ld.exe.
>
>Most be a bug, at least in my instantiation, of deja-gnu.
>If I 'make install' newly built ld.exe, the test passes.
>
>So I withdraw my objection to the patch.
>
>Could you add a test for symlinks (on cygwin), eg where libfoo.a is a
>symlink to $PATH/foo.dll.
>This is what
> if (REALPATH (entry->filename, fbuf) == NULL)
> strncpy (fbuf, entry->filename, sizeof (fbuf));
>is about I think.
Does it not work with cygwin symlinks currently?
cgf