From: Mark Hatle <mark.hatle@windriver.com>
To: Philip Balister <philip@balister.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3 v2] sanity.bbclass: Check for the known broken version of make
Date: Mon, 8 Jul 2013 11:55:05 -0500 [thread overview]
Message-ID: <51DAEEE9.6000203@windriver.com> (raw)
In-Reply-To: <51D0569A.7050705@balister.org>
On 6/30/13 11:02 AM, Philip Balister wrote:
> On 06/30/2013 11:56 AM, Trevor Woerner wrote:
>> On 27 June 2013 10:08, Mark Hatle <mark.hatle@windriver.com> wrote:
>>> See GNU Savannah bug 30612 -- make 3.82 is known to be broken.
>>>
>>> A number of vendors are providing a modified version, so checking
>>> for just the version string is not enough. We also need to check
>>> if the patch for the issue has been applied. We use a modified
>>> version of the reproduced to check for the issue.
>>>
>>> Signed-off-by: Mark Hatle <mark.hatle@windriver.com>
>>> ---
>>> +
>>> + if status != 0:
>>> + return "Your version of make 3.82 is broken. Please revert to 3.81 or install a patched version.\n"
>>
>>
>> Instead of returning an error and asking the user to manually update
>> their own 'make', wouldn't it be better if bitbake simply built its
>> own known-to-be-working -native version instead? In this way a good,
>> working version of 'make' could be installed in a potential SDK's
>> sysroot as well?
>
> Is the broken version good enough to build a working version?
(Catching up on email after my vacation...)
That is the primary issue, can we even trust the host system to work well enough
to build a working version.
Second, there was recently a change to oe-core that got rid of all of the
"bootstrap" builds, in favor of the 'buildtools'. For anyone with an old or
broken system, they will need to download (or build) the buildtools.. install it
and have it in their path prior to running oe-core.
This will provide the basic set of python, tar, git, and make that is needed for
the build system.
On a "working" host, you can use bitbake buildtools-tarball to generate it.
--Mark
> Philip
>
>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>
next prev parent reply other threads:[~2013-07-08 16:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 14:08 [PATCH 1/3 v2] sanity.bbclass: Check for the known broken version of make Mark Hatle
2013-06-27 14:21 ` Burton, Ross
2013-06-28 10:20 ` Paul Barker
2013-06-28 13:13 ` Mark Hatle
2013-06-28 15:11 ` Paul Barker
2013-06-28 18:22 ` Paul Barker
2013-06-30 15:56 ` Trevor Woerner
2013-06-30 16:02 ` Philip Balister
2013-06-30 22:55 ` Trevor Woerner
2013-07-08 16:55 ` Mark Hatle [this message]
2013-07-09 15:14 ` Trevor Woerner
2013-07-19 9:41 ` Paul Eggleton
2013-07-21 13:27 ` Trevor Woerner
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=51DAEEE9.6000203@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philip@balister.org \
/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