All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/4] lttng-tools: bump to 2.1.0
Date: Tue, 01 Jan 2013 22:21:03 +0100	[thread overview]
Message-ID: <87bod8sips.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20121231181629.727e4aa7@skate> (Thomas Petazzoni's message of "Mon, 31 Dec 2012 18:16:29 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 Thomas> Dear Samuel Martin,
 Thomas> On Sun, 30 Dec 2012 23:17:46 +0100, Samuel Martin wrote:

 >> +# Since the 2.1.0 release, lttng-tools depends on flex and bison,
 >> +# but they are not added to the dependency list since they are
 >> +# already Buildroot dependencies.

 Thomas> We are not very clear about this: we have packages for host-flex and
 Thomas> host-bison, and they are actually used by some of our packages. But we
 Thomas> also require the user to have flex and bison installed in his
 Thomas> distribution.

 Thomas> Probably something that should be clarified, in one direction or
 Thomas> another.

Yes, it would be good to get rid of the flex/bison deps, and use our own
everywhere if possible.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2013-01-01 21:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-30 22:17 [Buildroot] [pull request] Pull request for branch for-master/lttng Samuel Martin
2012-12-30 22:17 ` [Buildroot] [PATCH 1/4] lttng-libust: bump to 2.1.0 Samuel Martin
2012-12-30 22:17 ` [Buildroot] [PATCH 2/4] lttng-modules: " Samuel Martin
2012-12-30 22:17 ` [Buildroot] [PATCH 3/4] lttng-tools: " Samuel Martin
2012-12-31 17:16   ` Thomas Petazzoni
2013-01-01 21:21     ` Peter Korsgaard [this message]
2012-12-30 22:17 ` [Buildroot] [PATCH 4/4] lttng-babeltrace: bump to 1.0.0 Samuel Martin
2013-01-01 21:21 ` [Buildroot] [pull request] Pull request for branch for-master/lttng Peter Korsgaard

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=87bod8sips.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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.