Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sylvain Raybaud <sylvain.raybaud@green-communications.fr>
To: buildroot@busybox.net
Subject: [Buildroot] host âckage empty dependency list
Date: Thu, 15 Oct 2015 11:14:07 +0200	[thread overview]
Message-ID: <561F6E5F.9070709@green-communications.fr> (raw)
In-Reply-To: <20151014181336.GO2451@tarshish>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Baruch

On 14/10/2015 20:13, Baruch Siach wrote:
> Hi Sylvain,
> 
> On Wed, Oct 14, 2015 at 05:16:59PM +0200, Sylvain Raybaud wrote:
>> I'd like the host variant of a package to have no dependency at
>> all, while its target variant has some. Specifying an empty list
>> with
>> 
>> HOST_FOO_DEPENDENCIES = ""
>> 
>> gives me an error. Not setting HOST_FOO_DEPENDENCY or setting 
>> HOST_FOO_DEPENDENCIES =
>> 
>> makes it inherit the dependencies of target variant. Is there a
>> way to achieve this?
> 
> This is weird. Existing packages (e.g. tar, tcl, libcap, etc.)
> have
> 
> HOST_LIBCAP_DEPENDENCIES =
> 
> and it seems to work for them. Please post the full .mk file, and
> the build error message.
> 
> baruch
> 

Sorry, you're right, probably some other packages happened to select
the same dependencies as my package. I tried adding an exotic
dependency to my package and no host variant of it was built. Sorry
for the noise.

Cheers,

Sylvain


- -- 
Sylvain Raybaud
www.green-communications.fr
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJWH25fAAoJEEkkwl4JtJ9yKgsP/RhsqqL9+lhZfEELBV0shAZ2
BDSMqtO/Ctx/k3dw/wM8zKINT0H0ELiB3Ywg1nC8AEKsIuoI5nzLimE8kS9vRxQe
1xLoNhqeWYmIrCJQ1f8uoIQaYkcz6uxwTVThB5XTuukOrG8FG1j88zs0xQywU3ri
lnuQfUtx9A7FRO3qK17QFEv0xzAiysTt61GClJzreoL6Q5hXk2eqHjumoKE2M32A
0ICSA8VKOhMa0R0i3bKYZiKC60/3ap1L6hIFM/QpnkKXXgIZm6O8/LTZGCqtsi8d
5tyH+/dT3ALeDZwrvufk8idVMPk8vxE5YMM6t07YbFtHJiiOaSAqnXcNMCw2kKk+
xF3cX7a1x6e8XRjucaPqVIazT0OwQNFBAH871luA8E1n7qPx/FzbaeoEzKfqUUGo
8yYIfT319fldyV8wWSqcT0gkkH987QYp8XxzPwCqnr1TM8hGx16/4HGICLmh+/cE
jOfhnJEwPsuJ9Hr/RP/EvlXO7jAZVKQZAoyq0YwntUAWoR+qceuRqUL2D595iDGy
DVz4oGv8Gy8eT/Ss1/Qa7UpKH79kHrIyvfiJCXsmUxNf3vCjQbM8N7Zp/ZsqdNZl
MvjuM90oBcyJzXA8CEp2rtxzxejbKFFU+8vlSO+Zi4LYQJp15aBlX3RTTknO5ccl
1MTy4f4oopOfkqwBsEea
=zY7d
-----END PGP SIGNATURE-----

      reply	other threads:[~2015-10-15  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 15:16 [Buildroot] host âckage empty dependency list Sylvain Raybaud
2015-10-14 18:13 ` Baruch Siach
2015-10-15  9:14   ` Sylvain Raybaud [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=561F6E5F.9070709@green-communications.fr \
    --to=sylvain.raybaud@green-communications.fr \
    --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