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:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; q=dns; s=default; b=bvA
	AADJV/RZlr7qq7v/JrbjvtW+zNgyFscF0vedEIKvnFA0cV6se8hnU50JYXKx+Y5l
	VgUx7Kryj7+feKjt4JuTb5MZZQB+8JDCX83pBtSBrYEywWmF4eG9LVudhgPogRPd
	5qNzbwDQzRZ/wjP/FyWOcRZez9mfkJsHVNytLcEc=
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:from:to:subject:date:message-id:content-type
	:content-transfer-encoding:mime-version; s=default; bh=nNZ8B/KAB
	gqJ/hvnAzi6GM/ldas=; b=ELNLMZP6ahPT6CoBM5TKe9BA4IEa09mVoy6QgXJYb
	MKGJ2IGcBHEWB9WNsOWM/OV7n5NqOlzWhhHq/GJmyBOMHGiu3GOxcQX4hfrbNs+K
	re02zRAoOJ0R7AbuyzWrQgxvf8gU4mDwW7YDYvO3ug2eYCoRY5sFqjXuLotghTw8
	Vs=
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=2.8 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPAM_SUBJECT,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.2
X-HELO:	nihxway3out.hub.nih.gov
X-IronPortListener:	Outbound_SMTP
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	AsQGAAKje1KcKEfb/2dsb2JhbABagweBC78OgSUWbQeCJQEBAQMBEihEDQEIDRUULxMnBBsah1kGmzyEbJxtjyiDWIEQA45UkByLJoMmgio
From:	"Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject:	RE: Building a snapshot
Date:	Thu, 7 Nov 2013 14:30:30 +0000
Message-ID:	<5F8AAC04F9616747BC4CC0E803D5907D0C40D998@MLBXv04.nih.gov>
MIME-Version:	1.0
X-IsSubscribed:	yes
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id rA7EV781026208

> I'm not sure how you translate not building in the source directory to
> "the configure file is not supposed to be used".

> 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.
Take for example the latest make:
---
The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package. 
---

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.

I'm not sure how you come up with the translation of what I said, that
"the configure file is not supposed to be used"...

> If this is still confusing then you probably shouldn't be attempting to
> build from source at all.

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".

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?

Anton Lavrentiev
Contractor NIH/NLM/NCBI

--
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 -