DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=Twp9SeKk8RbNQNvY/c15fqd/HnTQtTCVwxzmBMYnzTS
	SyhsrqqmZnEPKDO8ihZ8dwdetYI6HiS2nkVZdMjrHrg0d7KYWwlMumGGD2PDNB13
	dPnYu1jFJaUw1ChNuKauwzEvvHTO2o+U6BZ2wGq9pGa21cu8EelZ9NmhDNMTedPw
	=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <527ADCBF.5010607@shaddybaddah.name>
Date: Thu, 07 Nov 2013 11:20:15 +1100
From: Shaddy Baddah <lithium-cygwin@shaddybaddah.name>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130922 Icedove/17.0.9
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: Building a snapshot ("Not an ELF file" error)
References: <5F8AAC04F9616747BC4CC0E803D5907D0C40C8EC@MLBXv04.nih.gov> <5F8AAC04F9616747BC4CC0E803D5907D0C40C985@MLBXv04.nih.gov> <5F8AAC04F9616747BC4CC0E803D5907D0C40CF9B@MLBXv04.nih.gov> <527A449D.2070701@shaddybaddah.name> <20131106134727.GD2611@calimero.vinschen.de>
In-Reply-To: <20131106134727.GD2611@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

On Nov 07 00:47, Corinna Vinschen wrote:
>> On Nov 06 02:37, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>>> It'd still be very interesting to know an opinion of the CYGWIN gurus
>>> about this trouble that I asked yesterday (thanks to Marco, I now know
>>> that the original ELF error is benign):
>>>
>>>> make[3]: Entering directory `/home/lavr/cygwin-snapshot-20130925-1/i686-pc-
>>>> cygwin/winsup/doc'
>>>> builddir=`pwd` \
>>>> && cd ../../.././winsup/doc \
>>>> && ../../.././winsup/doc/xidepend ../../.././winsup/doc/cygwin-ug-net.xml >
>>>> "${builddir}/Makefile.dep"
>>>> /bin/sh: line 2: ../../.././winsup/doc/xidepend: No such file or directory
>>>> make[3]: *** No rule to make target `Makefile.dep', needed by `all'.  Stop.
>>>> make[3]: Leaving directory `/home/lavr/cygwin-snapshot-20130925-1/i686-pc-
>>>> cygwin/winsup/doc'
>>
>> I noticed this recently too. I think it's just a bit of oversight with a
>> recent check-in to CVS.
>>
>> I've attached a patch that should fix this for the winsup module.
>
> Nope.  We don't support building within the source dir.  If you build in
> a separate build dir, which you should do anyway, xidepend is guaranteed
> to be not in .

Sorry, the patch is meant to be for the "build in a separate build dir"
method too.

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.

-- 
Regards,
Shaddy


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