public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* RE: Building a snapshot
@ 2013-11-06 17:03 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
  2013-11-06 17:21 ` Andrey Repin
  0 siblings, 1 reply; 5+ messages in thread
From: Lavrentiev, Anton (NIH/NLM/NCBI) [C] @ 2013-11-06 17:03 UTC (permalink / raw)
  To: cygwin

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

^ permalink raw reply	[flat|nested] 5+ messages in thread
* RE: Building a snapshot
@ 2013-11-07 14:30 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
  2013-11-07 16:22 ` Christopher Faylor
  0 siblings, 1 reply; 5+ messages in thread
From: Lavrentiev, Anton (NIH/NLM/NCBI) [C] @ 2013-11-07 14:30 UTC (permalink / raw)
  To: cygwin

> 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

^ permalink raw reply	[flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-11-07 16:22 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-06 17:03 Building a snapshot Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-06 17:21 ` Andrey Repin
2013-11-06 17:36   ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-07 14:30 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2013-11-07 16:22 ` Christopher Faylor

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