From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Build OSELAS toolchain fails saying that make is "too old"
Date: Tue, 28 Mar 2017 10:49:03 +0200 [thread overview]
Message-ID: <CABDcavYxCY4cTyUPfZf_rFkM9c74EVyvakdyYV7+3QPkXKUzcw@mail.gmail.com> (raw)
In-Reply-To: <20170328075829.aut7z37arribyxvj@pengutronix.de>
Hello,
2017-03-28 9:58 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> On Mon, Mar 27, 2017 at 06:43:21PM +0200, Guillermo Rodriguez Garcia wrote:
>> Hello,
>>
>> I am rebuilding OSELAS.Toolchain-2012.12.1 on a new machine (Ubuntu
>> 16.04). This is for an existing target platform; previous versions of
>> the toolchain were built on Ubuntu 10 and Ubuntu 12 hosts.
>>
>> Now when I try to build the toolchain, the glibc-headers package fails
>> to build with this error:
>>
>> *** These critical programs are missing or too old: make
>>
>> I guess my make is actually too new (4.1) rather than too old. Any
>> ideas how to fix this?
>
> The check is broken and does not accept make 4.x. Please use
> OSELAS.Toolchain-2012.12.2. It has a fix for this and several CVEs.
Thank you for your answer, however I would like to avoid switching to
a different toolchain. After all the whole point of ptxdist was to
have reproducible builds...
I'll see if I can backport the fixes.
Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2017-03-28 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 16:43 Guillermo Rodriguez Garcia
2017-03-28 7:58 ` Michael Olbrich
2017-03-28 8:49 ` Guillermo Rodriguez Garcia [this message]
2017-03-28 9:28 ` Juergen Borleis
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=CABDcavYxCY4cTyUPfZf_rFkM9c74EVyvakdyYV7+3QPkXKUzcw@mail.gmail.com \
--to=guille.rodriguez@gmail.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