mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [ANNOUNCE] OSELAS.Toolchain() 2013.12.1 released
Date: Mon, 10 Feb 2014 19:13:26 +0100	[thread overview]
Message-ID: <20140210181326.GF4177@pengutronix.de> (raw)
In-Reply-To: <20140206131659.GB25496@pengutronix.de>

Hi,

On Thu, Feb 06, 2014 at 02:16:59PM +0100, Michael Olbrich wrote:
> On Thu, Feb 06, 2014 at 01:38:26PM +0100, Alexander Aring wrote:
> > On Thu, Feb 06, 2014 at 01:05:54PM +0100, Michael Olbrich wrote:
> > > Hi,
> > > 
> > > I'm happy to announce that I've just released OSELAS.Toolchain-2013.12.1.
> > > 
> > > This is a bugfix-only release. The relevant changes since 2013.12.0 are:
> > >  - "SUSV3 LEGACY" enabled for uClibc. This includes 'usleep()' which is
> > >    still used by some busybox applets.
> > >  - correct version handling for toolchains with Linaro GCC.
> > >    PTXdist toolchain auto detection should work correctly again.
> > >  - Upstream gcc patch for PR target/58854 added.
> > > 
> > > I highly recommend to switch to this version if you're using 2013.12.0.
> > > Without the last bugfix gcc can generate incorrect code. The Linux kernel
> > > is affected and this results in random crashes.
> > > 
> > > Download the release here:
> > > http://www.pengutronix.de/oselas/toolchain/download/
> > > 
> > 
> > While configure of glibc-2.18 I get:
> > 
> > *** These critical programs are missing or too old: make
> > *** Check the INSTALL file for required versions.
> > 
> > 
> > 
> > my make version is:
> > 
> > GNU Make 4.0
> > Built for x86_64-unknown-linux-gnu
> > Copyright (C) 1988-2013 Free Software Foundation, Inc.
> > License GPLv3+: GNU GPL version 3 or later
> > <http://gnu.org/licenses/gpl.html>
> > This is free software: you are free to change and redistribute it.
> > There is NO WARRANTY, to the extent permitted by law.
> > 
> > 
> > 
> > So there are some mssing "| 4.*" in the configure script.
> > The (in my opinion, because it's change generated code) hacked solution
> > helps here:
> > 
> > https://projects.archlinux.org/svntogit/packages.git/tree/trunk/glibc-2.18-make-4.patch?h=packages/glibc
> 
> I would need to test this first. Even make 3.82 caused all kind of
> problems, so we need to check if the toolchain actually builds with make
> 4.0

btw, I just confirmed, that compiling the toolchains with make 3.82 will
fail! It ties to install stuff to /usr during glibc-headers.install.
So far, I've not seen a fix for this. I have no idea what's going on there.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2014-02-10 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 12:05 Michael Olbrich
2014-02-06 12:38 ` Alexander Aring
2014-02-06 13:16   ` Michael Olbrich
2014-02-10 18:13     ` Michael Olbrich [this message]
2014-02-10 18:17       ` Alexander Aring
2014-02-10 18:30         ` Alexander Aring

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=20140210181326.GF4177@pengutronix.de \
    --to=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