Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/7] bison: add host rules
Date: Wed, 29 Sep 2010 09:03:19 +0200	[thread overview]
Message-ID: <20100929090319.70706501@surf> (raw)
In-Reply-To: <1284832789-22631-5-git-send-email-llandwerlin@gmail.com>

On Sat, 18 Sep 2010 19:59:46 +0200
llandwerlin at gmail.com wrote:

> +$(eval $(call AUTOTARGETS,package,bison,host))

Bison is part of our set of mandatory dependencies on the host, as
checked in toolchain/dependencies/dependencies.sh. Therefore,
host-bison shouldn't be needed.

However, flex is also part of the mandatory dependencies on the host,
but we still have a couple of package that depend on host-flex.
Interesting.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2010-09-29  7:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-18 17:59 [Buildroot] [review request] rework of libtool llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 1/7] libtool: bump to 2.2.6b + introduce 2 libtool packages + cross compile patch llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 2/7] package: modifications to work with new libtool policy llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 3/7] tslib: Fix installation with new autotools policy llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 4/7] bison: add host rules llandwerlin at gmail.com
2010-09-29  7:03   ` Thomas Petazzoni [this message]
2010-09-18 17:59 ` [Buildroot] [PATCH 5/7] expat: comply with new libtool policy llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 6/7] sysstat: bump to 9.1.5 and " llandwerlin at gmail.com
2010-09-18 17:59 ` [Buildroot] [PATCH 7/7] gstreamer: allow autoreconfigure with gettext 0.18 llandwerlin at gmail.com

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=20100929090319.70706501@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