From: "Frank Ch. Eigler" <fche@redhat.com>
To: Gary Thomas <gary@mlbassoc.com>
Cc: sid@sources.redhat.com
Subject: Re: SID won't build
Date: Thu, 30 Jan 2003 17:21:00 -0000 [thread overview]
Message-ID: <20030130122139.A15968@redhat.com> (raw)
In-Reply-To: <1043879041.24759.4217.camel@hermes.chez-thomas.org>; from gary@mlbassoc.com on Wed, Jan 29, 2003 at 03:24:01PM -0700
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
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.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-01-30 17:21 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 [this message]
2003-01-30 19:36 ` Gary Thomas
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=20030130122139.A15968@redhat.com \
--to=fche@redhat.com \
--cc=gary@mlbassoc.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).