mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 0/6] OSELAS.Toolchain host tool version bumps
Date: Sun, 20 Dec 2015 16:13:06 +0100	[thread overview]
Message-ID: <20151220151306.GB25555@archie.tuxnet.lan> (raw)
In-Reply-To: <20151217104917.GG27568@pengutronix.de>

On Thu, Dec 17, 2015 at 11:49:17AM +0100, Michael Olbrich wrote:
> On Mon, Dec 14, 2015 at 02:51:45PM +0100, Ladislav Michl wrote:
> > On Sun, Dec 13, 2015 at 08:37:14PM +0100, Robert Schwebel wrote:
> > > Hi Clemens,
> > > 
> > > On Sun, Dec 13, 2015 at 04:34:43PM +0100, Clemens Gruber wrote:
> > > > the used host-xz version was not available anymore, I therefore updated
> > > > it and in the process, decided to update some of the other host
> > > > libraries as well.
> > > > 
> > > > In the next patch following these host tool version bumps, I made a
> > > > first attempt to move to current stable gcc, glibc, binutils and gdb.
> > > > (Just as a starting point, marked RFC)
> > > 
> > > Thanks for your patches, but Michael is already testing the toolchain
> > > for the new december release. Please stay tuned, a release is already
> > > being prepared based on the latest-and-greatest.
> > 
> > Hi Robert,
> > 
> > staying tunned is not enough ;-) Is there any preview available? I just
> > checked pengutronix' git and didn't find anything related.
> > I need this patch included: https://gcc.gnu.org/ml/gcc-patches/2012-07/msg01483.html
> > and will eventuely provide patch against OSELAS.Toolchain if needed.
> 
> This is fixed in gcc-5.3 right? That's the compiler the new toolchain will
> use.
> 
> Michael

Yes, this is fixed in 5.3!
See libstdc++-v3/libsupc++/eh_personality.cc, line 385.

Btw.: Michael, it would be great if you could push your current
development state of OSELAS.Toolchain to git.pengutronix.de to see where
you are at.

Thanks.
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-12-20 15:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 15:34 Clemens Gruber
2015-12-13 15:34 ` [ptxdist] [PATCH 1/6] host-gmp: bump version to 6.1.0 Clemens Gruber
2015-12-13 15:34 ` [ptxdist] [PATCH 2/6] host-isl: bump version to 0.14.1 Clemens Gruber
2015-12-13 15:34 ` [ptxdist] [PATCH 3/6] host-libelf: bump version to 0.164 Clemens Gruber
2015-12-13 15:34 ` [ptxdist] [PATCH 4/6] host-mpc: bump version to 1.0.3 Clemens Gruber
2015-12-13 15:34 ` [ptxdist] [PATCH 5/6] host-mpfr: bump version to 3.1.3 Clemens Gruber
2015-12-13 15:34 ` [ptxdist] [PATCH 6/6] host-xz: bump version to 5.2.2 Clemens Gruber
2015-12-13 19:37 ` [ptxdist] [PATCH 0/6] OSELAS.Toolchain host tool version bumps Robert Schwebel
2015-12-14 13:51   ` Ladislav Michl
2015-12-17 10:49     ` Michael Olbrich
2015-12-20 15:13       ` Clemens Gruber [this message]
2016-02-18 19:03   ` Jon Ringle
2016-02-18 19:06     ` Erwin Rol
2016-02-19  7:37       ` Robert Schwebel
2016-02-19  7:42         ` Bruno Thomsen
2016-02-19 13:56           ` Michael Olbrich
2016-02-19 14:59             ` Clemens Gruber
2016-02-19 17:13               ` Clemens Gruber

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=20151220151306.GB25555@archie.tuxnet.lan \
    --to=clemens.gruber@pqgruber.com \
    --cc=ptxdist@pengutronix.de \
    /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