All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stefan Fröberg" <stefan.froberg@petroprogram.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python: firefox host-python dependency needs --enable-unicodedata
Date: Tue, 21 Aug 2012 16:37:52 +0300	[thread overview]
Message-ID: <50338F30.7020907@petroprogram.com> (raw)
In-Reply-To: <20120821132339.45b28565@skate>

Hello Thomas

21.8.2012 14:23, Thomas Petazzoni kirjoitti:
> Le Wed, 15 Aug 2012 22:00:26 +0300,
> Stefan Froberg <stefan.froberg@petroprogram.com> a ?crit :
>
>> +ifneq ($(BR2_PACKAGE_PYTHON_UNICODEDATA),y)
>> +	HOST_PYTHON_CONF_OPT += --disable-unicodedata	
>> +else
>> +	HOST_PYTHON_CONF_OPT += --enable-unicodedata
>> +endif
> No, this is not correct. The BR2_PACKAGE_* options are here to
> configure the *target* packages. Host packages that are only
> dependencies to build target packages do not have kconfig options. So
> in this case, the only solution is to simply use --enable-unicodedata
> unconditionally to the host-python build.

Oh, sorry.
I was just trying to be carefull and not to mess with host-python too much.

>
> Can you post an updated patch with this change?

No problem. I will cook a new lil patch and resend.


By the way Thomas, what do you think about these two little changes to
SQLite and Valgrind ?

http://lists.busybox.net/pipermail/buildroot/2012-August/057377.html

http://lists.busybox.net/pipermail/buildroot/2012-August/057379.html


I also noticed that you accepted yasm and that little cairo patch for
next version.
Thank you!

Stefan

> Thanks,
>
> Thomas

  reply	other threads:[~2012-08-21 13:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-15 19:00 [Buildroot] [PATCH] python: firefox host-python dependency needs --enable-unicodedata Stefan Froberg
2012-08-15 19:00 ` Stefan Froberg
2012-08-21 11:23   ` Thomas Petazzoni
2012-08-21 13:37     ` Stefan Fröberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-08-21 13:48 Stefan Froberg
2012-08-24 21:41 ` Thomas Petazzoni

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=50338F30.7020907@petroprogram.com \
    --to=stefan.froberg@petroprogram.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.