tiny winsup config patch

Christopher Faylor cgf@cygnus.com
Mon Feb 15 21:47:00 GMT 1999

On Tue, Feb 16, 1999 at 12:32:36AM -0500, DJ Delorie wrote:
>> I don't think that it should be the function of winsup's configure to
>> ensure that the build environment which surrounds it is ok.  Cygnus
>> provides a build environment.  If you don't want to use it, then you
>> take your lumps.
>I think winsup's configure needs to know if it's building with a local
>version of newlib et al, and use it directly if so, rather that use
>newlib's libc.a (via libcygwin.a) but the installed cross compiler's

Why would we use the installed cross-compiler's headers?  If someone has
winsup installed without newlib then this will just work.  If they don't
then they should keep everything up to date.  ../newlib/lib[cm].a should
be up to date with respect to the headers.

>> If you're going to check for ../newlib, then you should check for
>> ../libiberty and ../include, too.  Do we really want to go down that
>> path?
>For building winsup and winsup/utils, I think we must.  That's the
>library we link against (via libcygwin.a), those should be the headers
>we include.

We should certainly include the same headers as are used to build cygwin
but I don't think that requires a configure change.


More information about the Cygwin-developers mailing list