X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=RbQKG7uKjmUiBdmjoY4QGpgln1YzES5JP1VC0RopzFN+8LWquI3R3
	+/cgLaA3uX4cCAa1X6fDLQD3ZwdVpqqQOCtknwbCZOx8JKh3czk9kK724roeI30j
	B9f2tAuJHBLwBaScQMN9hjIrXqBQca5Vbk0Z/f9EjCNzH4I4mQDycc=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=L/nViyCvlz4u+Kac7SekzmCBtWA=; b=LUVtVJEk+T+9iAusiQR6P0c+SQXS
	GvdgMZTjX+6nbFLzgvG9cyj2Hmj5x/TXycZbwLwgJ2eWKdvz0Fwy9Di6F9vOxJ/V
	Y6O8JS7AdX1XnPv2NZsW1+UYbNfLBOtUFKwh1QWhHYEXdNEv0aZ6KUlWh6Xtp7ur
	tSmjqPbowh4ysLU=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=4.0 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPAM_SUBJECT,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	mho-01-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18VFgBqaTHLsq+LAsFk/JDq
Date:	Thu, 7 Nov 2013 11:22:29 -0500
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Building a snapshot
Message-ID:	<20131107162229.GA4088@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<5F8AAC04F9616747BC4CC0E803D5907D0C40D998 AT MLBXv04 DOT nih DOT gov>
MIME-Version:	1.0
In-Reply-To:	<5F8AAC04F9616747BC4CC0E803D5907D0C40D998@MLBXv04.nih.gov>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Thu, Nov 07, 2013 at 02:30:30PM +0000, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> I'm not sure how you translate not building in the source directory to
>> "the configure file is not supposed to be used".

Sorry.  I interpreted your confusion about the "generic to GNU"
configure script as you deciding not to run it.

>> The configure script isn't generic.  It's intended for building Cygwin.
>
>> Once again: YOU ARE NOT SUPPOSED TO BUILD IN THE SOURCE DIRECTORY.
>
>> That means you don't do this:
>
>> 1) Unpack tarball.
>
>> 2) cd to unpacked directory.
>
>> 3) ./configure
>
>> You need to create a separate build directory and run configure there.
>> This is standard GNU stuff.  Nothing Cygwin specific here.
>
>I've built a lot of GNU stuff, and most of it does use the 1), 2), 3) above.

Good for you.  If you want help from "Cygwin Gurus" you're going to have
to follow their recommendations or at least follow the instructions in
the FAQ.

>Even GCC allows doing that (but does not recommend), but I say it's
>rather an exception.  And for that, their building instructions include
>specific steps to use a separate build directory.
>
>Confusing is that the README file does not provide a clue to call
>configure from a separate build directory.  Quite the contrary, it
>shows that configure must be started from the current directory, which
>is supposedly the top of the archive (because no other location to do
>that is ever mentioned, and even if it was -- there would not be any
>configure in that build directory -- it must still be called from the
>top of the archive, i.e.  using some path, not ".").  That's about
>"generic".

The README file is (unlike the configury) a generic one for GNU
projects.  The top-level configury allows building Cygwin as part of a
toolchain which includes gcc, gdb, binutils, bfd, and newlib.  As you
note, gcc and, I believe gdb and binutils also discourage building in
the source directory but they all use the same README.

>And I later posted that I followed the "no build in the source
>directory" rule, and it failed just as ungracefully as the build I had
>been doing prior.  I asked why, and no one responded other than "it's
>how it is supposed to be".  Really?

You've apparently missed some cygwin ml messages:

http://cygwin.com/ml/cygwin/2013-11/threads.html#00163

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -