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=s7gXwsqs7/wYhNJni96Bd4BqbJtyzSY/41e77k0QistPGCA7wxusm
	g4Hhonl0nxf+GqTWyA7RoPJrpBBEI0W8izNyRgp3olPXy7kzNWBFZaj82X5yAhJM
	xysug7r16euNMD04YkGpCRLYbiUlwKXr2RnnBg4VVrPRhYe1J2gUyI=
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=rsOXiUlV2ep2o+O8jMMKLSxUqAE=; b=GTSTMYd+V4TNwfgWfxnVl3RLhb4L
	IHf3T6wdtaMExwnRyoNAPyh8O0waiHiXQ16e500d7l6ssI57ZMm2YNyeGx39gye7
	tDMdo4QdLIzRuXd74CftvHETYcNTbOQtuZwqPz3U1tnVOrVtcnDVE0N7/5Mx+Ilp
	BYuuPfRBHHP0OJ4=
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=1.2 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,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:	U2FsdGVkX1/e3lTkO5xodX1AEiHhqjiw
Date:	Wed, 6 Nov 2013 19:38:02 -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:	<20131107003802.GA1243@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> <527ADCBF DOT 5010607 AT shaddybaddah DOT name>
MIME-Version:	1.0
In-Reply-To:	<527ADCBF.5010607@shaddybaddah.name>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Thu, Nov 07, 2013 at 11:20:15AM +1100, Shaddy Baddah wrote:
>As the OP has suggested in a recent post in their "Building a snapshot"
>thread, the problem is that there is a mix in methods to locating
>xidepend, whereby it is referenced via a relative dir path which would
>be direct.
>
>Only that there is a change of directory beforehand to which the
>relative dir path is no longer applicable, and this causes error. For me
>this was happening with a separate build dir, but I suspect that it
>would happen regardless, as the winsup/doc subpath lives under the
><target_architecture> subdir that is created exclusively for the build
>anyway.
>
>In-lining that patch will make that clearer:
>
>
>--- a/winsup/doc/Makefile.in
>+++ b/winsup/doc/Makefile.in
>@@ -91,6 +91,6 @@ cygwin-docs.tar.bz2 : $(TBFILES) $(TBDEPS)
>  Makefile.dep: cygwin-ug-net.xml
>         builddir=`pwd` \
>         && cd $(srcdir) \
>-       && $(srcdir)/xidepend $^ > "$${builddir}/$@"
>+       && ./xidepend $^ > "$${builddir}/$@"
>
>  -include Makefile.dep
>
>Beyond that, I also experienced the (minor) fop issue, and did not
>persevere. As I did not need the documentation to be built.

Your patch is correct.  I just checked in a variation of it along with
reinstating the "build in doc errors are ignored" behavior.

Many GNU projects deprecate using relative paths to the source
directory, probably just for problems like this.  However, it's
always been possible in Cygwin so it should remain possible.

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 -