Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2 0/6] Move gdbsupport to top level
Date: Wed, 15 Jan 2020 14:30:00 -0000	[thread overview]
Message-ID: <b30dfd03-66c1-d962-6c89-ae01ceb272e1@redhat.com> (raw)
In-Reply-To: <20200109005807.7314-1-tom@tromey.com>

I'm seeing this on F27 (a clean build from scratch):

~~~~~~~~~~~~~~~~~~~~~~~~~~~
 make[3]: Entering directory '/home/pedro/brno/pedro/gdb/binutils-gdb/build/gdbsupport'
   CC       gdb_tilde_expand.o
 In file included from /home/pedro/gdb/binutils-gdb/src/gdbsupport/../gnulib/import/libc-config.h:33:0,
                  from ../gnulib/import/glob.h:544,
                  from /home/pedro/gdb/binutils-gdb/src/gdbsupport/gdb_tilde_expand.c:22:
 ../bfd/config.h:7:4: error: #error config.h must be #included before system headers
  #  error config.h must be #included before system headers
     ^~~~~
~~~~~~~~~~~~~~~~~~~~~~~~~~~

libc-config.h, where it includes config.h, says:

~~~~~~~~~~~~~~~~~~~~~~~~~~~
 /* This is intended to be a good-enough substitute for glibc system
    macros like those defined in <sys/cdefs.h>, so that Gnulib code
    shared with glibc can do this as the first #include:
 
      #ifndef _LIBC
      # include <libc-config.h>
      #endif
 
    When compiled as part of glibc this is a no-op; when compiled as
    part of Gnulib this includes Gnulib's <config.h> and defines macros
    that glibc library code would normally assume.  */
 
 #include <config.h>
~~~~~~~~~~~~~~~~~~~~~~~~~~~

So it seems like the issue is that that '#include <config.h>' picks up
bfd's config.h instead of gnulib's by mistake.

Thanks,
Pedro Alves


  parent reply	other threads:[~2020-01-15 14:09 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  0:58 Tom Tromey
2020-01-09  0:58 ` [PATCH v2 4/6] Remove use of <config.h> from gdb/nat/ Tom Tromey
2020-01-09  0:58 ` [PATCH v2 1/6] Consolidate definition of USE_WIN32API Tom Tromey
2020-01-09  0:58 ` [PATCH v2 5/6] Add gdbsupport check-defines script Tom Tromey
2020-01-09  0:58 ` [PATCH v2 6/6] Don't link gdb twice against libiberty Tom Tromey
2020-01-11 16:58 ` [PATCH v2 0/6] Move gdbsupport to top level Tom Tromey
2020-01-12  2:48   ` Simon Marchi
2020-01-14 23:25     ` Tom Tromey
2020-01-15  0:36     ` Tom Tromey
2020-01-15 21:27   ` Christian Biesinger via gdb-patches
2020-01-17 18:02     ` Tom Tromey
2020-01-15 14:30 ` Pedro Alves [this message]
     [not found]   ` <8a8de6a9-37b8-cad3-c818-be903037fe48@redhat.com>
2020-01-15 16:07     ` Pedro Alves
     [not found]       ` <87c733a2-2b25-a954-88a1-9bfb1a7eca12@redhat.com>
2020-01-15 21:46         ` Pedro Alves
2020-01-15 22:12           ` Pedro Alves
2020-01-16  0:48             ` Pedro Alves
2020-01-16  2:57               ` Christian Biesinger via gdb-patches
2020-01-16 17:22                 ` Pedro Alves
2020-01-16 18:01                   ` Christian Biesinger via gdb-patches
2020-01-16 18:28                     ` Pedro Alves
2020-01-16 19:21                       ` Christian Biesinger via gdb-patches
2020-01-16  9:02           ` Simon Marchi
2020-01-16 15:24             ` Pedro Alves
2020-01-17 12:20               ` Simon Marchi
2020-01-17 13:37                 ` Pedro Alves
2020-01-17 14:40                   ` Simon Marchi
2020-01-17 15:32                     ` Pedro Alves
2020-01-17 18:13                       ` Tom Tromey
2020-01-16  4:23 ` Simon Marchi

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=b30dfd03-66c1-d962-6c89-ae01ceb272e1@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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