public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: sid@sources.redhat.com
Subject: Re: SID won't build
Date: Thu, 30 Jan 2003 19:36:00 -0000	[thread overview]
Message-ID: <1043955361.24759.5547.camel@hermes.chez-thomas.org> (raw)
In-Reply-To: <20030130122139.A15968@redhat.com>

On Thu, 2003-01-30 at 10:21, Frank Ch. Eigler wrote:
> Hi -
> 
> On Wed, Jan 29, 2003 at 03:24:01PM -0700, Gary Thomas wrote:
> > I updated from CVS today and SID no longer builds.  [...]
> > In file included from /work2/sid/src/opcodes/m32r-asm.c:28:
> > /work2/sid/src/opcodes/sysdep.h:28:20: config.h: No such file or
> > directory
> > [...]
> 
> I don't see this failure.  My daily automated build ran just fine
> yesterday afternoon, though it does this by checking out the CVS
> "sid" module, and running "make all".  Maybe one of the related
> top-level make targets ("sid-all"?) don't have all their dependencies
> listed properly.

I've tried making sure my sources are up-to-date two ways:
  cvs -q update -d -P
and
  cvs -d :pserver:anoncvs@sources.redhat.com:/cvs/src co sid

Both trees give the same results.

I'm trying to build with the simplest setup (in my mind):
  /tmp/src/sid/configure --prefix=XYZ

Ideas?

-- 
------------------------------------------------------------
Gary Thomas                 |
MLB Associates              |  Consulting for the
+1 (970) 229-1963           |    Embedded world
http://www.mlbassoc.com/    |
email: <gary@mlbassoc.com>  |
gpg: http://www.chez-thomas.org/gary/gpg_key.asc
------------------------------------------------------------

  reply	other threads:[~2003-01-30 19:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-29 22:24 Gary Thomas
2003-01-30 17:21 ` Frank Ch. Eigler
2003-01-30 19:36   ` Gary Thomas [this message]
2003-01-30 19:56     ` Frank Ch. Eigler

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=1043955361.24759.5547.camel@hermes.chez-thomas.org \
    --to=gary@mlbassoc.com \
    --cc=fche@redhat.com \
    --cc=sid@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).