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
Date: Wed, 19 Jul 2000 14:37:19 -0400
Message-Id: <200007191837.OAA10805@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: dtrom AT bumba DOT net
CC: cygwin AT sources DOT redhat DOT com
In-reply-to: <200007191823.OAA30347@bumba.net> (message from Dave Trombley on
	Wed, 19 Jul 2000 14:23:17 -0400)
Subject: Re: Compiling Postgresql on latest cygwin - 2 questions
References:  <200007191823 DOT OAA30347 AT bumba DOT net>


> I sucessfully built and linked the backend using the old ld.exe and
> linker scripts in a new kit.  ld -verbose seems to indicate that
> although one may change the linker scripts, a version reamins
> 'hard-compiled' in.  I'm not sure if it actually is compiled in or
> no; I know next to nothing about binutils.

It is.  The linker *always* uses a link script, but 99% of the time,
it uses an internal one.  Actually, there are six built-in ones, and
the one that is used depends on which command-line parameters you give
(like -r, -U, etc).

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com