From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Question concerning buildroot-libtool.patch
Date: Thu, 24 Jun 2010 16:03:20 +0200 [thread overview]
Message-ID: <20100624160320.3722ccbd@surf> (raw)
In-Reply-To: <201006241335.53291.PeterHuewe@gmx.de>
Hello,
On Thu, 24 Jun 2010 13:35:53 +0200
Peter H?we <PeterHuewe@gmx.de> wrote:
> As my development system is my normal home pc, it is quite prune to updates
> and changes :)
> Since I've just graduated and thus unemployed setting up a dedicated
> development environment isn't an option unfortunately :/
You can always create a chroot to have a clean build environment.
However, it's nice to have people testing things in non-clean
environments, since those are much closer to the reality than minimal
chroots.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-06-24 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 22:57 [Buildroot] Question concerning buildroot-libtool.patch Peter Hüwe
2010-06-24 7:25 ` Thomas Petazzoni
2010-06-24 11:35 ` Peter Hüwe
2010-06-24 14:03 ` Thomas Petazzoni [this message]
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=20100624160320.3722ccbd@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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