From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: OE breakages, was: Re: fakeroot fails to build
Date: Fri, 27 Feb 2009 09:26:34 -0700 [thread overview]
Message-ID: <20090227162633.GD5420@smtp.west.cox.net> (raw)
In-Reply-To: <c384c5ea0902270806n70ce6bbfg45d19b5ebaf64050@mail.gmail.com>
On Fri, Feb 27, 2009 at 05:06:25PM +0100, Leon Woestenberg wrote:
> Hello,
>
> On Thu, Feb 26, 2009 at 6:20 PM, Frans Meulenbroeks
> <fransmeulenbroeks@gmail.com> wrote:
> >> On 25-02-09 16:14, Mike (mwester) wrote:
> >
> > The problem I am facing is somewhat different.
> > I've added packages which build and test fine in my environment but
> > for some reason they do not build properly on tinderbox.
> >
> That often indicates a leak to the host and/or missing DEPENDS.
>
> The build machines that run test builds, should do so with the minimal
> amount of host requirements.
>
> Easily testable using virtual machines with freshly installed Linux,
> as most machines grow their installed package base during their
> lifecycle.
Also, chroots work for this.
--
Tom Rini
next prev parent reply other threads:[~2009-02-27 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 17:20 OE breakages, was: Re: fakeroot fails to build Frans Meulenbroeks
2009-02-26 19:37 ` Michael 'Mickey' Lauer
2009-02-27 16:06 ` Leon Woestenberg
2009-02-27 16:26 ` Tom Rini [this message]
2009-02-27 17:56 ` Frans Meulenbroeks
2009-02-27 19:35 ` Tom Rini
2009-02-28 10:54 ` Frans Meulenbroeks
2009-02-28 15:53 ` Tom Rini
2009-02-28 18:07 ` Frans Meulenbroeks
2009-02-28 18:29 ` Tom Rini
2009-03-01 17:09 ` Koen Kooi
2009-03-02 18:55 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2009-02-25 6:53 Mike (mwester)
2009-02-25 7:57 ` Koen Kooi
2009-02-25 8:23 ` Michael 'Mickey' Lauer
2009-02-25 15:14 ` Mike (mwester)
2009-02-25 15:43 ` OE breakages, was: " Koen Kooi
2009-02-26 13:05 ` Bernhard Guillon
2009-02-27 19:30 ` Rodrigo Vivi
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=20090227162633.GD5420@smtp.west.cox.net \
--to=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox