RE: Undefined weak symbols in shared libraries

["Dave Korn" <dave dot korn at artimi dot com>]

Nick Clifton wrote on 29 July 2008 08:40:

>> - The testsuite never runs C tests on cross targets.  This is an
>> annoying limitation for me since I mostly cross-test.  It's fixable,
>> but will introduce some dependencies on having a target during cross
>> testing that are not currently present.  Any opinions on that?
> 
> If you need a cross compiler why not put the test in the gcc testsuite ?
> 
> Answer: because it is testing the linker not the compiler.  But I think
> that the execution tests in the gcc testsuite should be considered to be
> toolchain tests rather then just compiler tests and hence it is
> reasonable to include checks on the linker's behaviour.  Besides there
> already are linker-feature tests in the gcc testsuite, so there is a
> precedent.

  Wouldn't-it-be-nice-if .....  the testsuite used a cross-compiler if it
found one installed, but (just in case it doesn't) the testsuite came with
all the .s files pre-generated by --save-temps and checked into the
repository?  Kinda like what we already do for files that can be generated
but not every end user has the tools installed?



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....