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] [RFC] OSELAS.Toolchain Update gcc, glibc, binutils and gdb
Date: Sun, 20 Dec 2015 16:06:05 +0100	[thread overview]
Message-ID: <20151220150604.GA25555@archie.tuxnet.lan> (raw)
In-Reply-To: <20151217105301.GH27568@pengutronix.de>

Hi,

On Thu, Dec 17, 2015 at 11:53:01AM +0100, Michael Olbrich wrote:
> Hi,
> 
> On Sun, Dec 13, 2015 at 04:44:23PM +0100, Clemens Gruber wrote:
> > A first attempt to update the toolchain.
> 
> I've done a lot of updated myself already. But I looked at your changes. I
> hadn't noticed, that cloog is no longer needed, so I extracted that from
> your patch :-).
> I didn't look too closely at the patch stacks. Anything special here, or is
> that just updates to the latest version?
> 
> Michael

Yes, besides separating cloog from isl in rules/cross-gcc.make, it's updates.

As of the GCC docs, the current stable version of isl (0.15) should work
too, but I got too many build failures, so I only updated to 0.14.1.

Also, regarding the following patch for gmp:
0001-HACK-config.guess-disable-build-tests-to-use-generic.patch
Is it necessary to have this applied per default? Could we make a
configuration option to enable auto-detected CPU optimizations?

So to summarize, we are getting the following versions:
binutils 2.25.1
gcc 5.3
gdb 7.10.1
glibc 2.22
host-gmp 6.1.0
host-isl 0.14.1
host-libelf 0.164
host-mpc 1.0.3
host-mpfr 3.1.3
host-xz 5.2.2
host-zlib 1.2.8

?

Thanks,
Clemens

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-13 15:44 Clemens Gruber
2015-12-17 10:53 ` Michael Olbrich
2015-12-20 15:06   ` 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=20151220150604.GA25555@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