X-Recipient: archive-cygwin@delorie.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=E5n77TFkBotoQ5JeHC8qKipkwmLY2GdwjArAvkuAwpOH9raC0hv/F
	69YMwyfg8dQedgcV7FUaw3PRy1a/FOVgGOtXcWGkf+1gDJrPCoi9GVxHe4Bi0dYD
	RhRZ4IPJxU/WVZWNdBvffs5qW5q6HydvDwzs4HuahVH8qQGxPKcN3k=
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=Q8Va0y0TURgGaigy1pVd66dCxL4=; b=qGweFoFYow3QX6hlMUAfXJxSNxMk
	ffrXD/hjrP1PXa7rwt3crBOI9svwHGTWJzGekkwrzJqJxFNmxGayjli4Llo01PGh
	D5FmFgwhQ1c12Xxl9VXaqR6Cv7W47QjQruDEM/EF+3vvINenC5tDDNZ32jnKA/bG
	qGTi+PbzWqd8Ono=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=1.2 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO: mho-02-ewr.mailhop.org
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/nl431phZrfjO/S3GPExtK
Date: Wed, 6 Nov 2013 17:59:36 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Building a snapshot ("Not an ELF file" error)
Message-ID: <20131106225936.GC2699@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <5F8AAC04F9616747BC4CC0E803D5907D0C40C8EC@MLBXv04.nih.gov> <5F8AAC04F9616747BC4CC0E803D5907D0C40C985@MLBXv04.nih.gov> <5F8AAC04F9616747BC4CC0E803D5907D0C40CF9B@MLBXv04.nih.gov> <527A449D.2070701@shaddybaddah.name> <20131106134727.GD2611@calimero.vinschen.de> <5F8AAC04F9616747BC4CC0E803D5907D0C40D3F0@MLBXv04.nih.gov> <527A5A68.8050206@cygwin.com> <5F8AAC04F9616747BC4CC0E803D5907D0C40D4DE@MLBXv04.nih.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5F8AAC04F9616747BC4CC0E803D5907D0C40D4DE@MLBXv04.nih.gov>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Wed, Nov 06, 2013 at 03:20:55PM +0000, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> See the FAQ: <http://cygwin.com/faq.html#faq.programming.building-cygwin>
>
>I see, thanks Larry!  There's a Readme file at the top level of
>the snapshot tar ball, which I glanced at, and saw the usual
>"./configure; make" sequence even though now when I looked more
>closely, the file is just something generic to GNU, not particularly
>to CYGWIN.  Not sure what it is doing there -- but certainly not helping
>(esp. for the first-timers)...

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.

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

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

