Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dr. Rolf Jansen" <rj@surtec.com>
To: gdb@sourceware.org
Subject: error during configure/make sequence on GDB-CVS sources at Mac OS X
Date: Wed, 23 Apr 2008 20:55:00 -0000	[thread overview]
Message-ID: <565DF7B3-6F48-4FC3-A6C5-F84B03723359@surtec.com> (raw)

The following relates to:

Mac OS X 10.5.2, PPC
Xcode 3.0, Apple gcc and tools 4.0.1.

Building, installation, and running of gdb-6.8.50.20080408 works fine.

Building the current CVS (from today, 2008-04-23) stops during  
configure of src/gdb with the following error:

configure: creating ./config.status
config.status: creating Makefile
config.status: creating .gdbinit
config.status: creating gnulib/Makefile
config.status: error: cannot find input file: gnulib/Makefile.in
make[1]: *** [configure-gdb] Error 1
make: *** [all] Error 2

The commands are:

mkdir build
cd build
../gdb-cvs/configure --target=i386-mingw32msvc --disable-nls --disable- 
tui
make

In fact, gdb-6.8.50.20080408 is the last snapshot that builds at my  
system. The build of gdb-6.8.50.20080415 and of gdb-6.8.50.20080423  
does stop at the same stage with the same error like the current gdb- 
cvs does.

Please do no take this as any kind of a request. I only want to let  
you know that a commit made in the 7 days from 2008-04-08 to  
2008-04-15 changed something in the configure-gdb script which might  
break building of gdb on some systems.

Best regards

Dr. Rolf Jansen


             reply	other threads:[~2008-04-23 19:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 20:55 Dr. Rolf Jansen [this message]
2008-04-24  1:19 ` Daniel Jacobowitz
2008-04-24 16:25   ` Dr. Rolf Jansen
2008-04-26 15:40     ` Daniel Jacobowitz
2008-04-26 16:22       ` Dr. Rolf Jansen

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=565DF7B3-6F48-4FC3-A6C5-F84B03723359@surtec.com \
    --to=rj@surtec.com \
    --cc=gdb@sourceware.org \
    /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