Re: fatal error: config.h: No such file or directory

2014-12-24 Thread Andrew Haley
On 23/12/14 21:54, Bruce Korb wrote:
 On 12/23/14 09:07, Aldy Hernandez wrote:
 Andrew Haley a...@redhat.com writes:

 On 12/21/2014 02:38 AM, Bruce Korb wrote:
 Shouldn't the configure step have made config.h?

 It's probably because you are building in srcdir.  That is not
 supported.

 Hmm, newbies run into this often enough that I wonder whether we should
 just error out from the configuration stage.
 
 Yeah, we newbies who've only been fiddling it for 15 years.
 I think it a good idea.  My script that does the configure  build
 is much newer though.  It's only about 5 years old.
 
 Good error messages are really, really, really important --
 especially if you are changing requirements.  Someone from
 the distant dusty past may wind up with a stubbed toe.
 
 Oh, another point:
 
 Some projects cannot be built with separate source/build directories
 and some projects (like yours) cannot be build without separation.
 So the real question is, Does it really save enough development effort
 that it is not worth doing the you can build it either way way?

We'd have to test it and we'd have to test building in a separate
subdir.  That's a big testing effort, and it's a question of whether
it's a good way for us to spend our own time and that of our build
boxes.  I say no, and agree that Aldy has a good point.

Andrew.


Re: fatal error: config.h: No such file or directory

2014-12-23 Thread Aldy Hernandez
Andrew Haley a...@redhat.com writes:

 On 12/21/2014 02:38 AM, Bruce Korb wrote:
 Shouldn't the configure step have made config.h?

 It's probably because you are building in srcdir.  That is not
 supported.

Hmm, newbies run into this often enough that I wonder whether we should
just error out from the configuration stage.

Aldy


Re: fatal error: config.h: No such file or directory

2014-12-23 Thread Bruce Korb

On 12/23/14 09:07, Aldy Hernandez wrote:

Andrew Haley a...@redhat.com writes:


On 12/21/2014 02:38 AM, Bruce Korb wrote:

Shouldn't the configure step have made config.h?


It's probably because you are building in srcdir.  That is not
supported.


Hmm, newbies run into this often enough that I wonder whether we should
just error out from the configuration stage.


Yeah, we newbies who've only been fiddling it for 15 years.
I think it a good idea.  My script that does the configure  build
is much newer though.  It's only about 5 years old.

Good error messages are really, really, really important --
especially if you are changing requirements.  Someone from
the distant dusty past may wind up with a stubbed toe.

Oh, another point:

Some projects cannot be built with separate source/build directories
and some projects (like yours) cannot be build without separation.
So the real question is, Does it really save enough development effort
that it is not worth doing the you can build it either way way?


Re: fatal error: config.h: No such file or directory

2014-12-21 Thread Andrew Haley
On 12/21/2014 02:38 AM, Bruce Korb wrote:
 Shouldn't the configure step have made config.h?

It's probably because you are building in srcdir.  That is not
supported.

Andrew.



fatal error: config.h: No such file or directory

2014-12-20 Thread Bruce Korb

after 2 hours and 10 minutes:


/bin/sh ./libtool --tag=CXX   --mode=compile 
/u/gnu/proj/gcc-svn-bld/host-x86_64-unknown-linux-gnu/gcc/xg++ 
-B/u/gnu/proj/gcc-svn-bld/host-x86_64-unknown-linux-gnu/gcc/ -nostdinc++ `if 
test -f 
/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/scripts/testsuite_flags;
 then /bin/sh 
/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/scripts/testsuite_flags
 --build-includes; else echo -funconfigured-libstdc++-v3 ; fi` 
-L/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src 
-L/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs 
-L/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs 
-B/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs 
-B/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs 
-B/u/gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/bin/ 
-B/u/gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/lib/ -isystem 
/u/gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/includ

e
-isystem /u/gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/sys-include
-DHAVE_CONFIG_H -I. -I../.././libcc1  -I ../.././libcc1/../include -I 
../.././libcc1/../libgcc -I ../host-x86_64-unknown-linux-gnu/gcc 
-I../.././libcc1/../gcc -I ../.././libcc1/../gcc/c -I 
../.././libcc1/../gcc/c-family -I ../.././libcc1/../libcpp/include   -W -Wall  
-fvisibility=hidden -g -O2 -D_GNU_SOURCE -MT findcomp.lo -MD -MP -MF 
.deps/findcomp.Tpo -c -o findcomp.lo ../.././libcc1/findcomp.cc

libtool: compile:  
/u/gnu/proj/gcc-svn-bld/host-x86_64-unknown-linux-gnu/gcc/xg++ 
-B/u/gnu/proj/gcc-svn-bld/host-x86_64-unknown-linux-gnu/gcc/ -nostdinc++ 
-nostdinc++ 
-I/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/include/x86_64-unknown-linux-gnu
 -I/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/include 
-I/u/gnu/proj/gcc-svn-bld/libstdc++-v3/libsupc++ 
-I/u/gnu/proj/gcc-svn-bld/libstdc++-v3/include/backward 
-I/u/gnu/proj/gcc-svn-bld/libstdc++-v3/testsuite/util 
-L/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src 
-L/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs 
-L/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs 
-B/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/src/.libs 
-B/u/gnu/proj/gcc-svn-bld/x86_64-unknown-linux-gnu/libstdc++-v3/libsupc++/.libs 
-B/u/gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/bin/ 
-B/u/gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/lib/ -isystem /u

/
gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/include -isystem 
/u/gnu/proj/gcc-svn-inst/x86_64-unknown-linux-gnu/sys-include -DHAVE_CONFIG_H 
-I. -I../.././libcc1 -I ../.././libcc1/../include -I ../.././libcc1/../libgcc 
-I ../host-x86_64-unknown-linux-gnu/gcc -I../.././libcc1/../gcc -I 
../.././libcc1/../gcc/c -I ../.././libcc1/../gcc/c-family -I 
../.././libcc1/../libcpp/include -W -Wall -fvisibility=hidden -g -O2 
-D_GNU_SOURCE -MT findcomp.lo -MD -MP -MF .deps/findcomp.Tpo -c 
../.././libcc1/findcomp.cc  -fPIC -DPIC -o .libs/findcomp.o

../.././libcc1/findcomp.cc:20:20: fatal error: config.h: No such file or 
directory
compilation terminated.
make[3]: *** [findcomp.lo] Error 1
make[3]: Leaving directory 
`/u/gnu/proj/gcc-svn-bld/host-x86_64-unknown-linux-gnu/libcc1'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/u/gnu/proj/gcc-svn-bld/host-x86_64-unknown-linux-gnu/libcc1'
make[1]: *** [all-libcc1] Error 2
make[1]: Leaving directory `/u/gnu/proj/gcc-svn-bld'
make: *** [all] Error 2


The config:

 ./configure --enable-languages=c,c++ --disable-multilib 
--prefix=/u/gnu/proj/gcc-svn-inst 'CFLAGS=-g -Wall'

(I must disable multilib or it chokes and dies very early.)

Shouldn't the configure step have made config.h?