RE: Building a snapshot

RE: Building a snapshot

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

> > See the FAQ: <http://cygwin.com/faq.html#faq.programming.building-cygwin>

Well, I guess this time I followed the instructions to a tee
by using a separate "build" directory, but the snapshot build still
fails at the very same spot:

...
make[3]: Leaving directory `/home/lavr/build/i686-pc-cygwin/winsup/lsaauth'
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
make[3]: *** No rule to make target `Makefile.dep', needed by `all'.  Stop.
make[3]: Leaving directory `/home/lavr/build/i686-pc-cygwin/winsup/doc'
Makefile:82: recipe for target `doc' failed
make[2]: *** [doc] Error 1
make[2]: Leaving directory `/home/lavr/build/i686-pc-cygwin/winsup'
Makefile:8381: recipe for target `all-target-winsup' failed
make[1]: *** [all-target-winsup] Error 2
make[1]: Leaving directory `/home/lavr/build'
Makefile:833: recipe for target `all' failed
make: *** [all] Error 2

Any help will be highly appreciated.

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

Re: Building a snapshot

[Andrey Repin]

Greetings, Lavrentiev, Anton (NIH/NLM/NCBI) [C]!

>> > See the FAQ: <http://cygwin.com/faq.html#faq.programming.building-cygwin>

> Well, I guess this time I followed the instructions to a tee
> by using a separate "build" directory, but the snapshot build still
> fails at the very same spot:

> ...
> make[3]: Leaving directory `/home/lavr/build/i686-pc-cygwin/winsup/lsaauth'
> 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
> make[3]: *** No rule to make target `Makefile.dep', needed by `all'.  Stop.
> make[3]: Leaving directory `/home/lavr/build/i686-pc-cygwin/winsup/doc'
> Makefile:82: recipe for target `doc' failed
> make[2]: *** [doc] Error 1
> make[2]: Leaving directory `/home/lavr/build/i686-pc-cygwin/winsup'
> Makefile:8381: recipe for target `all-target-winsup' failed
> make[1]: *** [all-target-winsup] Error 2
> make[1]: Leaving directory `/home/lavr/build'
> Makefile:833: recipe for target `all' failed
> make: *** [all] Error 2

> Any help will be highly appreciated.

It failing to assemble documentation, if I understand it right.
The page you mentioned expressly say that these errors can be ignored.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 06.11.2013, <21:13>

Sorry for my terrible english...


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

RE: Building a snapshot

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

> 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

Re: Building a snapshot

[Christopher Faylor]

On Thu, Nov 07, 2013 at 02:30:30PM +0000, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> I'm not sure how you translate not building in the source directory to
>> "the configure file is not supposed to be used".

Sorry.  I interpreted your confusion about the "generic to GNU"
configure script as you deciding not to run it.

>> 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.
>
>I've built a lot of GNU stuff, and most of it does use the 1), 2), 3) above.

Good for you.  If you want help from "Cygwin Gurus" you're going to have
to follow their recommendations or at least follow the instructions in
the FAQ.

>Even GCC allows doing that (but does not recommend), but I say it's
>rather an exception.  And for that, their building instructions include
>specific steps to use a separate build directory.
>
>Confusing is that the README file does not provide a clue to call
>configure from a separate build directory.  Quite the contrary, it
>shows that configure must be started from the current directory, which
>is supposedly the top of the archive (because no other location to do
>that is ever mentioned, and even if it was -- there would not be any
>configure in that build directory -- it must still be called from the
>top of the archive, i.e.  using some path, not ".").  That's about
>"generic".

The README file is (unlike the configury) a generic one for GNU
projects.  The top-level configury allows building Cygwin as part of a
toolchain which includes gcc, gdb, binutils, bfd, and newlib.  As you
note, gcc and, I believe gdb and binutils also discourage building in
the source directory but they all use the same README.

>And I later posted that I followed the "no build in the source
>directory" rule, and it failed just as ungracefully as the build I had
>been doing prior.  I asked why, and no one responded other than "it's
>how it is supposed to be".  Really?

You've apparently missed some cygwin ml messages:

http://cygwin.com/ml/cygwin/2013-11/threads.html#00163

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

RE: Building a snapshot

[Lavrentiev, Anton (NIH/NLM/NCBI) [C]]

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

I've built a lot of GNU stuff, and most of it does use the 1), 2), 3) above.
Take for example the latest make:
---
The simplest way to compile this package is:

  1. `cd' to the directory containing the package's source code and type
     `./configure' to configure the package for your system.  If you're
     using `csh' on an old version of System V, you might need to type
     `sh ./configure' instead to prevent `csh' from trying to execute
     `configure' itself.

     Running `configure' takes awhile.  While running, it prints some
     messages telling which features it is checking for.

  2. Type `make' to compile the package. 
---

Even GCC allows doing that (but does not recommend), but I say it's rather an exception.
And for that, their building instructions include specific steps to use a separate build directory.

I'm not sure how you come up with the translation of what I said, that
"the configure file is not supposed to be used"...

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

Confusing is that the README file does not provide a clue to call configure
from a separate build directory.  Quite the contrary, it shows that configure must
be started from the current directory, which is supposedly the top of the archive
(because no other location to do that is ever mentioned, and even if it was -- there
would not be any configure in that build directory -- it must still be called
from the top of the archive, i.e. using some path, not ".").  That's about "generic".

And I later posted that I followed the "no build in the source directory" rule, and it failed
just as ungracefully as the build I had been doing prior. I asked why, and no one responded
other than "it's how it is supposed to be".
Really?

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