From: Daniel Egger <degger@fhm.edu>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: Daniel Jacobowitz <drow@mvista.com>,
GCC Mailinglist <gcc@gcc.gnu.org>,
Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: Building with --enable-languages problematic
Date: Sat, 13 Oct 2001 10:36:00 -0000 [thread overview]
Message-ID: <1002917256.12257.18.camel@sonja> (raw)
In-Reply-To: <20011009162834.A23280@disaster.jaj.com>
Am Die, 2001-10-09 um 22.28 schrieb 1002659314:
> Something like the completely untested patch, appended?
Looks fine to me.
--
Servus,
Daniel
prev parent reply other threads:[~2001-10-13 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-09 12:24 Daniel Egger
2001-10-09 12:29 ` guerby
2001-10-09 12:30 ` Daniel Jacobowitz
2001-10-09 13:06 ` Daniel Egger
2001-10-09 13:25 ` Gerald Pfeifer
2001-10-11 7:38 ` Daniel Egger
2001-10-12 13:56 ` Gerald Pfeifer
2001-10-09 13:27 ` Phil Edwards
2001-10-13 10:36 ` Daniel Egger [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=1002917256.12257.18.camel@sonja \
--to=degger@fhm.edu \
--cc=drow@mvista.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=pedwards@disaster.jaj.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).