mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: ptxdist@pengutronix.de
Cc: Michael Olbrich <m.olbrich@pengutronix.de>
Subject: Re: [ptxdist] [PATCH 0/6] OSELAS.Toolchain host tool version bumps
Date: Fri, 19 Feb 2016 18:13:32 +0100	[thread overview]
Message-ID: <20160219171332.GA2411@archie.tuxnet.lan> (raw)
In-Reply-To: <20160219145956.GA3115@archie.tuxnet.lan>

On Fri, Feb 19, 2016 at 03:59:56PM +0100, Clemens Gruber wrote:
> Hi Michael,
> 
> On Fri, Feb 19, 2016 at 02:56:41PM +0100, Michael Olbrich wrote:
> > I've pushed the relevant commits to the toolchain git. I expect, that
> > source tarballs with new releases will probably follow next week.
> 
> We talked about a new toolchain with the latest and greatest (tm) a few
> months ago.
> It should include GCC 5.3, GDB 7.10.1, Binutils 2.26 and now glibc 2.23.
> 
> Are there any remaining problems with those new versions which delay the
> release?
> 
> Would be nice if we could take a look at this new latest-and-greatest
> toolchain on the master branch of the OSELAS.Toolchain git repository.
> 
> Thanks,
> Clemens

I forgot to say:
I already use such a toolchain and only a few minor patch fixups were
necessary for arm-v7a-* (but it is clearly much more work to ensure that
it still works on every possible platform you support instead of one or
two)

Maybe it's also time to remove the glibc-ports entry as the major
architectures are included in glibc mainline since 2.19, right?

I'd also suggest adding --enable-stackguard-randomization to the glibc
default configure arguments.
Without it, every binary built with -fstack-protector uses the same
canary value (0xff0a0000).
With that option, the binary uses a different random canary at runtime
(different at each invocation, taken from /dev/urandom).
Debian and ArchLinux both have this option enabled since many years.

Cheers,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

      reply	other threads:[~2016-02-19 17: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
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 [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=20160219171332.GA2411@archie.tuxnet.lan \
    --to=clemens.gruber@pqgruber.com \
    --cc=m.olbrich@pengutronix.de \
    --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