RS6000: Missing EABI symbols at link time

[Nick Clifton]

Hi Geoff,

> However, it is a bug that libstdc++-v3 does not build on powerpc- eabi.  
> It should not be trying to link anything; its final product is  a .a 
> archive.

Right - this is really the point.  The configure tests used by 
libstdc++-v3 appear to include checking to make sure that the compiler 
can compile and link an executable.  I do not know enough about 
configure to know how to stop this link test and I was not sure what 
gcc's policy actually was.  I guessed that the policy was that any gcc 
compiler should be able to link together an executable without needing 
any special command line options, or that if it couldn't do this, then 
it would issue an informative error message telling the user what was 
needed.  eg:

   "gcc required one of -mfreebfd, -mads, ... to be specified on the 
command line before it can create an executable."

Do you think that this is fair ?  Plus should libstdc++-v3 be modified 
(somehow) not to require a compiler than can link together an executable ?

Cheers
   Nick