This is the mail archive of the
binutils@sourceware.org
mailing list for the binutils project.
Re: [PATCH] Re: more plugin testsuite issues
- From: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- To: Dave Korn <dave dot korn dot cygwin at gmail dot com>, "binutils at sourceware dot org" <binutils at sourceware dot org>
- Date: Fri, 05 Nov 2010 00:36:28 +0000
- Subject: Re: [PATCH] Re: more plugin testsuite issues
- References: <20101026045431.GB5348@bubble.grove.modra.org> <4CC70CDB.9060202@gmail.com> <20101028081642.GK31277@bubble.grove.modra.org> <4CD2E0C1.2060304@gmail.com> <4CD31374.5060702@gmail.com> <20101104235453.GU26513@bubble.grove.modra.org>
On 04/11/2010 23:54, Alan Modra wrote:
> On Thu, Nov 04, 2010 at 08:11:32PM +0000, Dave Korn wrote:
>> * ld-plugin/plugin.exp (testobjfiles): Dont use HOSTING_CRT0.
>> (testobjfiles_notext): Likewise.
>> (libs): Don't use HOSTING_LIBS; fill with default symbol defs instead.
>>
>> * lib/ld-lib.exp (ld_simple_link_defsyms): Add cygming clause.
>>
>> What do you think? OK for head?
>
> Seems reasonable, but didn't you want to test libraries? Not saying
> you should, but figured that was why you called printf in the test.
Well yeah, that was what I wanted, but I can't see any reasonable way to do
it that's going to be portable everywhere. We don't know what the libs or
startup objects are called for the cross-target, so we can't figure out how to
link it. I could perhaps hack default_ld_compile around to make it possible
to omit the -c flag, and just let the cross-compiler driver do all the work, I
suppose, if you think that would be better?
cheers,
DaveK