Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Dr. Rolf Jansen" <rj@surtec.com>
To: gdb@sourceware.org
Subject: Re: error during configure/make sequence on GDB-CVS sources at Mac OS X
Date: Thu, 24 Apr 2008 16:25:00 -0000	[thread overview]
Message-ID: <40BB42D6-A95E-4ED2-82BD-7574622BF351@surtec.com> (raw)
In-Reply-To: <20080423200306.GA14064@caradoc.them.org>


Am 23.04.2008 um 17:03 schrieb Daniel Jacobowitz:

> On Wed, Apr 23, 2008 at 04:53:57PM -0300, Dr. Rolf Jansen wrote:
>> 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
>
> Are you building from snapshot tarballs or from a CVS checkout?  Looks
> like CVS, and you didn't get the new gnulib directory.  Use cvs co
> to update, not cvs up.

I was talking about both.

Weekly snapshots
   gdb-6.8.50.20080408: build completes successfully
   gdb-6.8.50.20080415: build breaks
   gdb-6.8.50.20080421: build breaks

gdb-cvs updated only today (checked out at the beginning of April)
   build breaks

gdb-cvs just checked out (after your message)
   build completes successfully

So the issue seems to be resolved. In fact the gnulib directory was  
missing in my CVS working copy as well as in two of the snapshots at  
the ftp server of sourceware.org.

I will use co in the future for keeping my CVS working directory up to  
date.

Best regards

Dr. Rolf Jansen


  reply	other threads:[~2008-04-23 20:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 20:55 Dr. Rolf Jansen
2008-04-24  1:19 ` Daniel Jacobowitz
2008-04-24 16:25   ` Dr. Rolf Jansen [this message]
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=40BB42D6-A95E-4ED2-82BD-7574622BF351@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