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: Corinna Vinschen <cygwin AT cygwin DOT com>
Date: Tue, 19 Dec 2000 11:53:12 +0100
X-Mailer: KMail [version 1.1.99]
Content-Type: text/plain;
  charset="US-ASCII"
To: cygwin <cygwin AT cygwin DOT com>
References: <5 DOT 0 DOT 2 DOT 1 DOT 0 DOT 20001217230850 DOT 033bea20 AT pop DOT bresnanlink DOT net> <3A3E9F45 DOT 2707 DOT CB405 AT localhost>
In-Reply-To: <3A3E9F45.2707.CB405@localhost>
Subject: Re: where to find nslookup for Cygwin?
MIME-Version: 1.0
Message-Id: <00121911531201.28008@cygbert>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id FAA15706

On Tuesday 19 December 2000 08:35, Stephen C. Biggs wrote:
> On 18 Dec 2000, at 9:44, Corinna Vinschen wrote:
> > 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.

You are right but this shouldn't influence your package. It's a problem
in the gcc configuration. IMO this should be changed in gcc but not
result in changing the package scheme.

BTW: I don't have that problem since I have set the environment
variables C_INCLUDE_PATH and CPLUS_INCLUDE_PATH to /usr/local/include.

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