Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
From:	"Stephen C. Biggs" <s_c_biggs AT bigfoot DOT com>
To:	Corinna Vinschen <cygwin AT cygwin DOT com>
Date:	Mon, 18 Dec 2000 23:35:33 -0800
MIME-Version:	1.0
Subject:	Re: where to find nslookup for Cygwin?
Reply-to:	s_c_biggs AT bigfoot DOT com
Message-ID:	<3A3E9F45.2707.CB405@localhost>
References:	<5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001217230850 DOT 033bea20 AT pop DOT bresnanlink DOT net>
In-reply-to:	<0012180944040M.21902@cygbert>
X-mailer:	Pegasus Mail for Win32 (v3.12c)

On 18 Dec 2000, at 9:44, Corinna Vinschen wrote:

> On Monday 18 December 2000 06:24, Chris Abbey wrote:
> > At 20:50 12/17/00 -0800, Stephen C. Biggs wrote:
> > >Thank you for the reply.  This does NOT entirely answer my question.
> >
> > hmm... as has been pointed out, I didn't realize the difference
> > between preparing tarballs for the main distro and for the franken.de
> > server, those details will have to wait for someone more familiar
> > with the franken.de way of doing things to come on line. :( sorry.
> >
> >  > How can it be pre-patched and ALSO cygwin-specific??
> >
> > in this case I'd interpret "pre-patched" as "previously patched",
> > not "before being patched". So the tarball is already containing
> > the cygwin specific code.
> 
> Create a patched source archive and a separate patch file. This should
> accomodate all needs.
> 
> BTW: Please build your binary package so that it uses /usr/local as
> prefix (which should be the default) and not /usr. This way it's easier
> to distinguish between packages from the base distribution and external
> packages.

I have no problem with this, and I happen to agree that this is the 
way it should be... however, this will break compiles of external 
packages in cygwin that need the installed include files because of 
the system search order in gcc that is configured by cygwin.

See my post entitled: "strange GCC system include search order".

What this forces people to do is:
export 'CFLAGS=-isystem /usr/local/include'

which seems wrong to me; i.e. it is defined as a system include path 
in most if not all other installations of gcc on Unix.

> 
> Corinna
> 
> -- 
> Corinna Vinschen                  Please, send mails regarding Cygwin to
> Cygwin Developer                                mailto:cygwin AT cygwin DOT com
> Red Hat, Inc.
> 
> --
> Want to unsubscribe from this list?
> Check out: http://cygwin.com/ml/#unsubscribe-simple
> 



--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

- Raw text -