This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Link tests after GCC_NO_EXECUTABLES

On Tue, Sep 18, 2007 at 03:27:18PM +0200, Bernd Schmidt wrote:
> Jie Zhang wrote:
> > Bernd Schmidt wrote:
> >> Jie Zhang wrote:
> >>> But by design if gcc_no_link = no, link tests should be avoided.
> >>
> >> ??? I would have thought gcc_no_link = yes means link tests are avoided.
> >>
> > Oops, I meant gcc_no_link = yes.
> 
> Stupid double negatives.  Okay, so then your problem is that gcc_no_link=yes.  
> Find out why it's setting that.

It always does for newlib.  The libtool tests are relatively recent
(from some recent autotools upgrade).

I believe this particular error comes from using --enable-shared on a
newlib target.

-- 
Daniel Jacobowitz
CodeSourcery
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]