From: Paul Sokolovsky <pmiscml@gmail.com>
To: "Mike (mwester)" <mwester@dls.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: OE a deterministic build system?
Date: Tue, 10 Apr 2007 18:14:12 +0300 [thread overview]
Message-ID: <1704526428.20070410181412@gmail.com> (raw)
In-Reply-To: <009901c77b80$b9b02e70$6e01a8c0@twilight>
Hello Mike,
Tuesday, April 10, 2007, 5:58:40 PM, you wrote:
>>> Can someone make sanity.bbclass detect dash and exit with a
>>> warning/error? :)
>>
>> Probably better is to make bash-native and depend on it?
>> (or ash)
>> Just curious.
> Ack!
I bet you meant "Nak!".
> OE already builds a lot of stuff natively -- there's no need to slow
> builds done even more by building something natively that one should be able
> to presume exists on every reasonable build machine. I think if a build
> machine has gcc, it shouldn't be too much more difficult to expect a working
> bash as well, IMO.
Sure, it makes no sense to *depend* on them. But it would make sense
to still has comprehensive set of *-native recipes, and make sanity.bb
to be smart enough to suggest user that one could build *-native thing
manually as one way to resolve missing build-time dependency. (No, I
don't think that sanity.bb should be smartass and build missing things
itself - user should request that explicitly).
> Mike (mwester)
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-04-10 15:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-09 6:22 OE a deterministic build system? Rolf Leggewie
2007-04-09 16:52 ` Justin Patrin
2007-04-09 17:50 ` Philip Balister
2007-04-09 21:53 ` Richard Purdie
2007-04-09 22:15 ` Justin Patrin
2007-04-10 13:02 ` José Bernardo Bandos Rodrigues
2007-04-10 14:39 ` Richard Purdie
2007-04-10 14:46 ` Sergey Lapin
2007-04-10 14:58 ` Mike (mwester)
2007-04-10 15:14 ` Paul Sokolovsky [this message]
2007-04-12 5:18 ` Rolf Leggewie
2007-04-12 5:37 ` Rolf Leggewie
2007-04-10 18:30 ` Leon Woestenberg
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=1704526428.20070410181412@gmail.com \
--to=pmiscml@gmail.com \
--cc=mwester@dls.net \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.