Re: /usr/local/{include,lib} on Cygwin

From: Jason Tishler <Jason(dot)Tishler(at)dothill(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-ports(at)postgresql(dot)org
Subject: Re: /usr/local/{include,lib} on Cygwin
Date: 2001-03-07 04:06:33
Message-ID: 20010306230633.L1510@dothill.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-ports

Peter,

On Tue, Mar 06, 2001 at 05:35:16PM +0100, Peter Eisentraut wrote:
> Our build system is set up to automatically include -I/usr/local/include
> and -L/usr/local/lib on the compile and link command lines on Cygwin.
> Now I see a lot of users where this issues a warning message that this
> directory doesn't exist. This may confuse new users. Also, shouldn't gcc
> be searching these directories automatically?

I'm not a gcc expert, but from empirical evidence I was able to determine
that Cygwin gcc seems to automatically search /usr/local/include and
/usr/local/lib during compilation and linking, respectively. Hence, it
seems that the above options are redundant.

> Can someone comment whether
> it would be better to remove these explicit options?

If removing redundancy is better, then I guess so. Nevertheless, I just
removed them from src/Makefile.global and src/backend/Makefile, did a
make clean, make and a fairly recent CVS source tree built without errors.

Jason

--
Jason Tishler
Director, Software Engineering Phone: +1 (732) 264-8770 x235
Dot Hill Systems Corp. Fax: +1 (732) 264-8798
82 Bethany Road, Suite 7 Email: Jason(dot)Tishler(at)dothill(dot)com
Hazlet, NJ 07730 USA WWW: http://www.dothill.com

In response to

Responses

Browse pgsql-ports by date

  From Date Subject
Next Message Tom Lane 2001-03-07 04:22:34 Re: /usr/local/{include,lib} on Cygwin
Previous Message Jane G 2001-03-07 04:04:09 Re: new beep problem