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=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Wed, 6 Nov 2013 17:59:36 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Building a snapshot ("Not an ELF file" error)
Message-ID: <20131106225936.GC2699@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5F8AAC04F9616747BC4CC0E803D5907D0C40C8EC AT MLBXv04 DOT nih DOT gov> <5F8AAC04F9616747BC4CC0E803D5907D0C40C985 AT MLBXv04 DOT nih DOT gov> <5F8AAC04F9616747BC4CC0E803D5907D0C40CF9B AT MLBXv04 DOT nih DOT gov> <527A449D DOT 2070701 AT shaddybaddah DOT name> <20131106134727 DOT GD2611 AT calimero DOT vinschen DOT de> <5F8AAC04F9616747BC4CC0E803D5907D0C40D3F0 AT MLBXv04 DOT nih DOT gov> <527A5A68 DOT 8050206 AT cygwin DOT com> <5F8AAC04F9616747BC4CC0E803D5907D0C40D4DE AT MLBXv04 DOT nih DOT 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