From: Daniel Jacobowitz <drow@false.org>
To: binutils@sources.redhat.com
Subject: Re: Q: Estimated date for 2.16 release ?
Date: Thu, 24 Feb 2005 17:54:00 -0000 [thread overview]
Message-ID: <20050224173132.GC5216@nevyn.them.org> (raw)
In-Reply-To: <Pine.BSF.4.58.0501271126570.35923@dair.pair.com>
On Sun, Jan 30, 2005 at 09:10:52PM -0500, Hans-Peter Nilsson wrote:
> On Thu, 27 Jan 2005, Daniel Jacobowitz wrote:
> > On Thu, Jan 27, 2005 at 10:56:30AM -0500, Hans-Peter Nilsson wrote:
> > > On Thu, 27 Jan 2005, Ian Lance Taylor wrote:
> > > > Hans-Peter Nilsson <hp@bitrange.com> writes:
> > > > > BTW, was the intl/ directory about to be added to binutils?
> > > > > Maybe that and the fallout should be done before the release.
> > > > > Or maybe better done after branching?
> > > > The binutils releases already have an intl directory, don't they?
> > > > They used to, and it seems to me that they still do.
> > >
> > > Oh right you are, problem misdiagnosed. Still a problem,
> > > though, and one that would be good to fix before the next
> > > release.
> >
> > It's more complicated than you think :-)
>
> Uh, remind me: what did I think? (I made no claim about
> simplicity above. ;-)
>
> FWIW, one workaround is to remove the intl directory from the
> combined sources. Perhaps better than upgrading binutils to
> autoconf 2.59 at this time (which would seem necessary in order
> to sync the intl machinery).
Anyway, it sounds like this is specifically related to combined builds,
and therefore not an issue for 2.16; if you try to combine released
toolchain components rather than HEAD, this is the least of your
problems :-)
> Anyway, I've seen a problem with the stabs linker-warning
> machinery (see libgloss/libnosys/warning.h) and a.out; there's a
> SEGV which valgrind says is an invalid access, after allocated
> memory. Valgrind also changes the behavior and instead of the
> linker warnings, the symbols are undefined. PR and testcase
> later.
I believe that you've fixed this since the above message. Am I
remembering rightly?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-02-24 17:31 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 13:45 Tomer Levi
2005-01-27 14:00 ` Daniel Jacobowitz
2005-01-27 14:07 ` Christian Joensson
2005-01-27 14:12 ` Eric Botcazou
2005-01-27 14:34 ` Jakub Jelinek
2005-02-14 10:46 ` Eric Botcazou
2005-02-14 13:01 ` Eric Botcazou
2005-01-27 14:26 ` Joel Sherrill <joel@OARcorp.com>
2005-01-27 14:36 ` Hans-Peter Nilsson
2005-02-24 18:53 ` Daniel Jacobowitz
2005-02-24 19:03 ` Hans-Peter Nilsson
2005-02-24 19:09 ` Joel Sherrill <joel@OARcorp.com>
2005-02-24 20:36 ` Eric Norum
2005-01-27 14:27 ` Hans-Peter Nilsson
2005-01-27 15:12 ` Ian Lance Taylor
2005-01-27 15:56 ` Hans-Peter Nilsson
2005-01-27 16:06 ` Daniel Jacobowitz
2005-01-31 2:11 ` Hans-Peter Nilsson
2005-02-24 17:54 ` Daniel Jacobowitz [this message]
2005-01-27 18:45 ` Thorsten Glaser
2005-02-24 17:49 ` Daniel Jacobowitz
2005-02-24 18:17 ` Thorsten Glaser
2005-04-25 8:06 ` Thorsten Glaser
2005-01-27 19:09 ` The Doctor
2005-01-31 11:40 ` Nick Clifton
2005-01-31 0:25 ` Ben Elliston
2005-01-31 0:42 ` Daniel Jacobowitz
2005-01-31 1:01 ` Ben Elliston
2005-02-24 17:50 ` Daniel Jacobowitz
2005-01-31 0:30 ` Ben Elliston
2005-01-31 0:42 ` Daniel Jacobowitz
2005-01-31 17:15 ` Nick Clifton
2005-02-24 18:40 ` Daniel Jacobowitz
2005-03-08 20:53 ` Daniel Jacobowitz
2005-03-10 9:32 ` Nick Clifton
2005-03-21 11:00 ` Alan Modra
2005-03-21 11:52 ` Daniel Jacobowitz
2005-01-31 16:25 ` Nick Clifton
2005-02-14 18:07 ` Aaron W. LaFramboise
2005-02-15 17:10 ` Nick Clifton
2005-02-24 18:59 ` Daniel Jacobowitz
2005-02-14 10:47 Anil Paranjape
2005-02-14 10:50 ` Miles Bader
2005-02-14 15:08 ` Nick Clifton
2005-02-14 16:17 ` Nick Clifton
2005-02-14 19:19 Anil Paranjape
2005-02-14 23:20 ` Nick Clifton
2005-02-16 12:11 Anil Paranjape
2005-02-16 15:49 ` Nick Clifton
2005-03-01 13:42 Anil Paranjape
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=20050224173132.GC5216@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@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).