Re: more plugin testsuite issues

[Dave Korn <dave dot korn dot cygwin at gmail dot com>]

On 28/10/2010 09:16, Alan Modra wrote:
> On Tue, Oct 26, 2010 at 06:16:11PM +0100, Dave Korn wrote:
>> On 26/10/2010 05:54, Alan Modra wrote:
>>> Hi Dave,
>>>   Is there a good reason why we need $LIBS in plugin.exp:58
>>> set libs "$LIBS $HOSTING_LIBS"
>>   Almost certainly not.  I verified on i686-pc-cygwin and i686-pc-linux-gnu
>> that nothing fails when it's removed.  Feel free to commit that change.
> 
> Committed.
> 
> 	* ld-plugin/plugin.exp (libs): Remove $LIBS.


  Alan, did that solve everything for you, or are there still problems from
systems without libc?

  It might be easiest just to make these tests native only, like you suggested
earlier.  I would have liked to do a trial link to see if it was possible to
run the tests even in cross, but there doesn't seem to be suitable support in
the testsuite to do a generic cross link: default_ld_link is no good because
it does the 'set libs "$LIBS $HOSTING_LIBS"' thing (that's where I got it from
in the first place, btw) and default_ld_simple_link is no use because it
doesn't add any libs (or startup objects) at all.

  Ah, hang on, I just discovered ld_simple_link_defsyms.  If I use that, is it
meant to guarantee I have enough symbols defined to link an object file
without needing any crt startup objects or libraries?  Maybe all I need do is
add "__main" to the list there, and not use any (particularly $HOSTING) libs
or crt0 at all in this test.  Does that sound right?

    cheers,
      DaveK