public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lavrentiev, Anton (NIH/NLM/NCBI) [C]" <lavr@ncbi.nlm.nih.gov>
To: Andrey Repin <cygwin@cygwin.com>
Subject: RE: Building a snapshot
Date: Wed, 06 Nov 2013 17:36:00 -0000	[thread overview]
Message-ID: <5F8AAC04F9616747BC4CC0E803D5907D0C40D5CF@MLBXv04.nih.gov> (raw)
In-Reply-To: <821879778.20131106211500@mtu-net.ru>

> The page you mentioned expressly say that these errors can be ignored.

It says,

> Normally, building ignores any errors in building the documentation

which IIUC means it should ignore such errors on its own -- not stop
with a hard failure, such as with not being able to construct a path
with a correct nesting level to a script, which is there.

Following make by how it changes its current working directory, I get:

make[3]: Entering directory `/home/lavr/build/i686-pc-cygwin/winsup/doc'
builddir=`pwd` \
&& cd ../../../../cygwin-snapshot-20130925-1/winsup/doc \
&& ../../../../cygwin-snapshot-20130925-1/winsup/doc/xidepend ../../../../cygwin-snapshot-20130925-1/winsup/doc/cygwin-ug-net.xml > "${builddir}/Makefile.dep"
/bin/sh: line 2: ../../../../cygwin-snapshot-20130925-1/winsup/doc/xidepend: No such file or directory

$ cd /home/lavr/build/i686-pc-cygwin/winsup/doc

~/build/i686-pc-cygwin/winsup/doc
$ ls -l ../../../../cygwin-snapshot-20130925-1/winsup/doc/xidepend
-rwxr-xr-x 1 lavr Domain Users 874 Jun  4 07:50 ../../../../cygwin-snapshot-20130925-1/winsup/doc/xidepend

~/build/i686-pc-cygwin/winsup/doc
$ cd ../../../../cygwin-snapshot-20130925-1/winsup/doc

~/cygwin-snapshot-20130925-1/winsup/doc
$ ls -l ../../../../cygwin-snapshot-20130925-1/winsup/doc/xidepend
ls: cannot access ../../../../cygwin-snapshot-20130925-1/winsup/doc/xidepend: No such file or directory

So the xidepend location was calculated correctly w.r.t. to the build directory,
but since cwd changed to the source tree (?), it was no longer valid.

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

  reply	other threads:[~2013-11-06 17:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 17:03 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-06 17:21 ` Andrey Repin
2013-11-06 17:36   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C] [this message]
2013-11-07 14:30 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-07 16:22 ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5F8AAC04F9616747BC4CC0E803D5907D0C40D5CF@MLBXv04.nih.gov \
    --to=lavr@ncbi.nlm.nih.gov \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).