From: DJ Delorie <dj@redhat.com>
To: peter@baradas.org
Cc: gcc@gcc.gnu.org, crossgcc@sources.redhat.com
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
Date: Tue, 20 May 2003 16:19:00 -0000 [thread overview]
Message-ID: <200305201609.h4KG9jR20778@greed.delorie.com> (raw)
In-Reply-To: <20030520053204.ADDB298982@baradas.org> (message from Peter Barada on Tue, 20 May 2003 01:32:04 -0400 (EDT))
> gcc-3.3/lbiberty/vsprintf.c, indeed includes <varargs.h> (which gcc
> supplies), so if gcc-3.3 has killed support for varargs,h, why is
> libiberty/vsprintf.c trying to include it.
That code in libiberty is ancient. If it's broken now, that means
that whoever dropped support for varargs.h didn't test it well enough.
> In fact, why is gcc-3.3 trying to build libiberty with the *target*
> compiler anyway?
Libiberty is built up to three times: First, for the machine upon
which the build happens, second, for the machine upon which the
resulting tools will run, and third, for the target for which the
tools produce code.
next prev parent reply other threads:[~2003-05-20 16:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 6:12 Peter Barada
2003-05-20 6:53 ` Erik Christiansen
2003-05-20 10:53 ` Kai Ruottu
2003-05-20 10:44 ` Kai Ruottu
2003-05-21 4:55 ` Peter Barada
2003-05-21 7:13 ` Peter Barada
2003-05-21 15:05 ` Randy Rude
2003-05-21 15:38 ` Peter Barada
2003-05-21 16:56 ` Randy Rude
2003-05-21 17:28 ` Joe Buck
2003-05-21 17:39 ` DJ Delorie
2003-05-22 14:59 ` Randy Rude
2003-05-22 17:36 ` DJ Delorie
2003-05-23 19:40 ` Randy Rude
2003-05-22 3:14 ` Peter Barada
2003-05-22 12:17 ` Kai Ruottu
2003-05-22 13:33 ` Peter Barada
2003-05-23 3:25 ` Peter Barada
2003-05-20 16:19 ` DJ Delorie [this message]
2003-05-20 21:06 ` Kaveh R. Ghazi
2003-05-20 21:44 ` DJ Delorie
2003-05-23 15:30 ` Kaveh R. Ghazi
2003-05-23 17:49 ` Joe Buck
2003-05-23 18:17 ` Peter Barada
2003-05-23 18:17 ` Joe Buck
2003-05-23 18:39 ` Peter Barada
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=200305201609.h4KG9jR20778@greed.delorie.com \
--to=dj@redhat.com \
--cc=crossgcc@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=peter@baradas.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).