public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug bootstrap/64320] New: Missing config.h during findcomp.cc compilation
@ 2014-12-15 19:45 townsend at astro dot wisc.edu
  2014-12-16 19:45 ` [Bug bootstrap/64320] " townsend at astro dot wisc.edu
                   ` (2 more replies)
  0 siblings, 3 replies; 4+ messages in thread
From: townsend at astro dot wisc.edu @ 2014-12-15 19:45 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64320

            Bug ID: 64320
           Summary: Missing config.h during findcomp.cc compilation
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: townsend at astro dot wisc.edu

I'm trying to build the latest trunk (rev. 218759) on Linux. Configuring with:

 ./configure CC=gcc --build=x86_64-pc-linux-gnu --prefix=/root/madsdk
--with-gmp=/root/madsdk --with-mpfr=/root/madsdk --with-mpc=/root/madsdk
--enable-languages=c,c++,fortran --disable-multilib --disable-nls
--disable-libsanitizer

...I get the following error during make:

libtool: compile:  /root/madsdk-src/gcc/host-x86_64-pc-linux-gnu/gcc/xg++
-B/root/madsdk-src/gcc/host-x86_64-pc-linux-gnu/gcc/ -nostdinc++ -nostdinc++
-I/root/madsdk-src/gcc/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/root/madsdk-src/gcc/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/root/madsdk-src/gcc/libstdc++-v3/libsupc++
-I/root/madsdk-src/gcc/libstdc++-v3/include/backward
-I/root/madsdk-src/gcc/libstdc++-v3/testsuite/util
-L/root/madsdk-src/gcc/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/root/madsdk-src/gcc/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/root/madsdk-src/gcc/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/root/madsdk-src/gcc/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/root/madsdk-src/gcc/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/root/madsdk/x86_64-pc-linux-gnu/bin/ -B/root/madsdk/x86_64-pc-linux-gnu/lib/
-isystem /root/madsdk/x86_64-pc-linux-gnu/include -isystem
/root/madsdk/x86_64-pc-linux-gnu/sys-include -DHAVE_CONFIG_H -I.
-I../.././libcc1 -I ../.././libcc1/../include -I ../.././libcc1/../libgcc -I
../host-x86_64-pc-linux-gnu/gcc -I../.././libcc1/../gcc -I
../.././libcc1/../gcc/c -I ../.././libcc1/../gcc/c-family -I
../.././libcc1/../libcpp/include -I/root/madsdk/include -I/root/madsdk/include
-I/root/madsdk/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
`/root/madsdk-src/gcc/host-x86_64-pc-linux-gnu/libcc1'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/root/madsdk-src/gcc/host-x86_64-pc-linux-gnu/libcc1'
make[1]: *** [all-libcc1] Error 2
make[1]: Leaving directory `/root/madsdk-src/gcc'
make: *** [all] Error 2

When attempting to build on OS X (10.6), I get the exact same error.


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug bootstrap/64320] Missing config.h during findcomp.cc compilation
  2014-12-15 19:45 [Bug bootstrap/64320] New: Missing config.h during findcomp.cc compilation townsend at astro dot wisc.edu
@ 2014-12-16 19:45 ` townsend at astro dot wisc.edu
  2014-12-21  9:21 ` schwab@linux-m68k.org
  2022-01-09 22:41 ` [Bug libcc1/64320] Missing config.h during findcomp.cc compilation when srcdir=objdir tromey at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: townsend at astro dot wisc.edu @ 2014-12-16 19:45 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64320

--- Comment #1 from Rich Townsend <townsend at astro dot wisc.edu> ---
OK, it seems that this bug comes from building with srcdir == objdir. If I
build in a separate directory, then the problem goes away.

As an aside, I hadn't realized that using srcdir == objdir is generally
discouraged (see, e.g., https://gcc.gnu.org/install/configure.html). Is this a
recent change, or have I always been doing it wrong?


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug bootstrap/64320] Missing config.h during findcomp.cc compilation
  2014-12-15 19:45 [Bug bootstrap/64320] New: Missing config.h during findcomp.cc compilation townsend at astro dot wisc.edu
  2014-12-16 19:45 ` [Bug bootstrap/64320] " townsend at astro dot wisc.edu
@ 2014-12-21  9:21 ` schwab@linux-m68k.org
  2022-01-09 22:41 ` [Bug libcc1/64320] Missing config.h during findcomp.cc compilation when srcdir=objdir tromey at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: schwab@linux-m68k.org @ 2014-12-21  9:21 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64320

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2014-12-21
     Ever confirmed|0                           |1

--- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> ---
Please try this patch:

diff --git a/libcc1/Makefile.am b/libcc1/Makefile.am
index ecab22c..7a274b3 100644
--- a/libcc1/Makefile.am
+++ b/libcc1/Makefile.am
@@ -17,7 +17,7 @@
 ## <http://www.gnu.org/licenses/>.

 ACLOCAL_AMFLAGS = -I .. -I ../config
-gcc_build_dir = ../$(host_subdir)/gcc
+gcc_build_dir = ../gcc
 AM_CPPFLAGS = -I $(srcdir)/../include -I $(srcdir)/../libgcc \
     -I $(gcc_build_dir) -I$(srcdir)/../gcc \
     -I $(srcdir)/../gcc/c -I $(srcdir)/../gcc/c-family \
diff --git a/libcc1/Makefile.in b/libcc1/Makefile.in
index ce752c0..1916134 100644
--- a/libcc1/Makefile.in
+++ b/libcc1/Makefile.in
@@ -245,7 +245,7 @@ top_builddir = @top_builddir@
 top_srcdir = @top_srcdir@
 visibility = @visibility@
 ACLOCAL_AMFLAGS = -I .. -I ../config
-gcc_build_dir = ../$(host_subdir)/gcc
+gcc_build_dir = ../gcc
 AM_CPPFLAGS = -I $(srcdir)/../include -I $(srcdir)/../libgcc \
     -I $(gcc_build_dir) -I$(srcdir)/../gcc \
     -I $(srcdir)/../gcc/c -I $(srcdir)/../gcc/c-family \


^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Bug libcc1/64320] Missing config.h during findcomp.cc compilation when srcdir=objdir
  2014-12-15 19:45 [Bug bootstrap/64320] New: Missing config.h during findcomp.cc compilation townsend at astro dot wisc.edu
  2014-12-16 19:45 ` [Bug bootstrap/64320] " townsend at astro dot wisc.edu
  2014-12-21  9:21 ` schwab@linux-m68k.org
@ 2022-01-09 22:41 ` tromey at gcc dot gnu.org
  2 siblings, 0 replies; 4+ messages in thread
From: tromey at gcc dot gnu.org @ 2022-01-09 22:41 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64320

Tom Tromey <tromey at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |tromey at gcc dot gnu.org
         Resolution|---                         |DUPLICATE

--- Comment #4 from Tom Tromey <tromey at gcc dot gnu.org> ---
The patch here, that was reported as fixing the problem,
was fixed in bug #65763.

*** This bug has been marked as a duplicate of bug 65763 ***

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2022-01-09 22:41 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-15 19:45 [Bug bootstrap/64320] New: Missing config.h during findcomp.cc compilation townsend at astro dot wisc.edu
2014-12-16 19:45 ` [Bug bootstrap/64320] " townsend at astro dot wisc.edu
2014-12-21  9:21 ` schwab@linux-m68k.org
2022-01-09 22:41 ` [Bug libcc1/64320] Missing config.h during findcomp.cc compilation when srcdir=objdir tromey at gcc dot gnu.org

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