From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] oprofile "requires" gmp??? Slight fork: BR2_STAGING_DIR
Date: Wed, 29 Dec 2010 11:57:33 +0100 [thread overview]
Message-ID: <20101229115733.55dc9bd2@surf> (raw)
In-Reply-To: <4D1A54D6.60805@zacarias.com.ar>
Hello,
On Tue, 28 Dec 2010 18:21:26 -0300
Gustavo Zacarias <gustavo@zacarias.com.ar> wrote:
> I was about to say that we can keep a symlink from staging->sysroot
> but i'd rather watch it die because i can't think of any useful
> purpose where people can't use the computed $(STAGING_DIR) directly.
I think we should keep such a symbolic link, at least at the beginning.
It'll allow users to notice that staging/ still exists, but has moved
to another place.
Regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2010-12-29 10:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-23 4:47 [Buildroot] oprofile "requires" gmp??? ANDY KENNEDY
2010-12-23 7:27 ` Thomas Petazzoni
2010-12-23 19:03 ` ANDY KENNEDY
2010-12-24 8:05 ` Thomas Petazzoni
2010-12-27 18:15 ` ANDY KENNEDY
2010-12-27 18:15 ` Gustavo Zacarias
2010-12-27 18:18 ` Gustavo Zacarias
[not found] ` <9AC3F0E75060224C8BBC5BA2DDC8853A1EAEB132@EXV1.corp.adtran.com>
2010-12-28 13:04 ` Gustavo Zacarias
2010-12-28 16:19 ` [Buildroot] oprofile "requires" gmp??? Slight fork: BR2_STAGING_DIR ANDY KENNEDY
2010-12-28 21:21 ` Gustavo Zacarias
2010-12-28 22:31 ` ANDY KENNEDY
2010-12-29 10:57 ` Thomas Petazzoni [this message]
2010-12-29 11:21 ` Peter Korsgaard
2010-12-29 21:02 ` [Buildroot] oprofile "requires" gmp??? ANDY KENNEDY
2010-12-29 21:10 ` Peter Korsgaard
2010-12-29 21:54 ` ANDY KENNEDY
2010-12-29 22:01 ` Gustavo Zacarias
2010-12-29 22:41 ` ANDY KENNEDY
2010-12-29 23:26 ` ANDY KENNEDY
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=20101229115733.55dc9bd2@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 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.