Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: gdb-patches@sources.redhat.com
Subject: Can't build current gdb source tree -- gnulib dependency?
Date: Fri, 04 Jul 2008 00:31:00 -0000	[thread overview]
Message-ID: <1215131443.3549.86.camel@localhost.localdomain> (raw)

Hey guys, excuse me if this is already being covered.
I know there are some threads about eg. gnulib stdint, 
and I don't know if what I'm seeing is related.

Brand new cvs checkout of "gdb", main trunk, (just updated
a few minutes ago, in time to get version.in change).

configure --disable-nls on a FC7 x86 laptop
(yeah, I know it's not the latest)

On first running "make CFLAGS=-g all-gdb" it terminates with:


config.status: creating gnulib/Makefile
config.status: error: cannot find input file: gnulib/Makefile.in

(of course there's no gnulib in my source tree -- does it
need to be added to the gdb module?)





             reply	other threads:[~2008-07-04  0:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04  0:31 Michael Snyder [this message]
2008-07-04  0:53 ` Daniel Jacobowitz
2008-07-04  1:07 ` Joel Brobecker
2008-07-04  1:54   ` Christopher Faylor
2008-07-04  2:34     ` Joel Brobecker
2008-07-04  2:32   ` Michael Snyder

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=1215131443.3549.86.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=gdb-patches@sources.redhat.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