All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@openembedded.org
Subject: Re: OE a deterministic build system?
Date: Mon, 09 Apr 2007 13:50:07 -0400	[thread overview]
Message-ID: <461A7CCF.8020206@balister.org> (raw)
In-Reply-To: <432beae0704090952u55847886o5eca96007a2d22be@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 842 bytes --]

Justin Patrin wrote:
>> Now, I really wonder what causes this virgin build to fail for me when
>> it seems everybody else can happily build it?  Is OE not deterministic?
>> Hints and discussion welcome.
>>
> 
> Of course it's deterministic....you do get the same error every time,
> don't you? Sounds like it's a difference between your system and
> everyone else's. I'll try a build myself with almost your exact
> local.conf and a fully up to date .dev as well.

I've had trouble in the past with autoconf detecting software installed 
on the build machine and using those paths for the OE build. This was 
caused by bad m4 macros that OE could not account for. I fixed the 
autoconf and solved the problem. Read the logs of the failed package and 
see if it is using headers from the machine you are building on.

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2007-04-09 17:50 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 [this message]
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
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=461A7CCF.8020206@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.