From: "Frank Ch. Eigler" <fche@redhat.com>
To: Dzung Nguyen <dunguyen@iol.unh.edu>
Cc: sid@sources.redhat.com, clp@iol.unh.edu
Subject: Re: another error with sid
Date: Mon, 02 Dec 2002 13:08:00 -0000 [thread overview]
Message-ID: <20021202210816.GA23780@redhat.com> (raw)
In-Reply-To: <3DEBC9D9.3040106@iol.unh.edu>
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
Hi -
> We have been getting errors with sid quite often recently (past couple
> of months). These problems hardly occurred before. Anybody knows why
> this is happenning now? [...]
> [...]
> /mnt/u9/toolchain/buildsys/source/toolchain/sid/component/cgen-cpu/tracedis.c:
> In function `bfd_put_bits':
> /mnt/u9/toolchain/buildsys/source/toolchain/sid/component/cgen-cpu/tracedis.c:108:
> parse error before "boolean"
> [...]
Yeah ... binutils just recently got a global s/boolean/bfd_boolean/
replacement, and we just have to follow suit (or abandon that notation).
- FchE
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2002-12-02 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-02 12:53 Dzung Nguyen
2002-12-02 13:08 ` Frank Ch. Eigler [this message]
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=20021202210816.GA23780@redhat.com \
--to=fche@redhat.com \
--cc=clp@iol.unh.edu \
--cc=dunguyen@iol.unh.edu \
--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).