From: Joe Buck <jbuck@synopsys.com>
To: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
Cc: dj@redhat.com, crossgcc@sources.redhat.com,
gcc-patches@gcc.gnu.org, gcc@gcc.gnu.org, peter@baradas.org
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
Date: Fri, 23 May 2003 17:49:00 -0000 [thread overview]
Message-ID: <20030523104125.B25849@synopsys.com> (raw)
In-Reply-To: <200305231529.LAA21736@caip.rutgers.edu>; from ghazi@caip.rutgers.edu on Fri, May 23, 2003 at 11:29:38AM -0400
On Fri, May 23, 2003 at 11:29:38AM -0400, Kaveh R. Ghazi wrote:
> > From: DJ Delorie <dj@redhat.com>
> >
> > > FWIW, it appears to be fixed on mainline. We can backport vsprintf.c
> > > to 3.3.1 if you think it's worth fixing. Here's the diff:
> >
> > If 3.3 complains about varargs, we should backport it.
>
> Done.
>
> (I did "make vsprintf.o" before and after the patch and verified it
> fixed the problem.)
Ideally there should be a PR for this problem, so I can point to it in
the 3.3.1 release notes. Any volunteers to make one? I would, but I
don't know what platforms that this problem causes a failure for.
next prev parent reply other threads:[~2003-05-23 17:42 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
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 [this message]
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=20030523104125.B25849@synopsys.com \
--to=jbuck@synopsys.com \
--cc=crossgcc@sources.redhat.com \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--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).