[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 2.59 and Explicit libc linking checks

From: Ralf Wildenhues
Subject: Re: 2.59 and Explicit libc linking checks
Date: Fri, 3 Mar 2006 20:52:52 +0100
User-agent: Mutt/1.5.9i

Hi Rafael,

* Rafael Rivera Jr. wrote on Fri, Mar 03, 2006 at 08:08:30PM CET:
> Thanks for the libtool pointer. I have CCed the proper list but intend 
> on removing address@hidden in future replies.


> On SkyOS (and cross-compiling tools for SkyOS on Cygwin), libsky gets 
> implicitly linked but because we failed this check, -lc is getting added 
> ( archive_cmds_need_lc=yes ) which bombs in the linking stages.

Excuse my ignorance, but what is SkyOS?  What does config.guess return
for this system?

Support for SkyOS probably needs to be added to Libtool.  Including a
setting in libtool.m4 to set


> >There is a comment a few lines above:
> >  
> >      # Test whether the compiler implicitly links with -lc since on some
> >      # systems, -lgcc has to come before -lc. If gcc already passes -lc
> >      # to ld, don't add -lc before -lgcc.

> Maybe I'm confused, but it looks like this code is trying to determine 
> whether or not -lc exists. If this is the case, it looks like the logic 
> is backwards because grep returns an error code of 1. Again, maybe I'm 
> just confused.

The idea is: libc is always needed (think unixy background), so we only
omit it if it is added by default by the compiler driver anyway.  Makes
sense now?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]