From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] intltool: no business defining PERLLIB
Date: Mon, 12 Mar 2012 08:00:42 +0100 [thread overview]
Message-ID: <20120312080042.19fa11bf@skate> (raw)
In-Reply-To: <1331517531-2291-2-git-send-email-gustavo@zacarias.com.ar>
Le Sun, 11 Mar 2012 22:58:49 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> $(eval $(call AUTOTARGETS))
This could be removed. We don't have libxml-parser-perl for the target.
This line used to be necessary because the host variant wouldn't work
without the target variant being defined, but it's no longer the case.
Therefore, the package/intltool/Config.in could go as well.
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:[~2012-03-12 7:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-12 1:58 [Buildroot] microperl fixes and improvements Gustavo Zacarias
2012-03-12 1:58 ` [Buildroot] [PATCH 1/3] intltool: no business defining PERLLIB Gustavo Zacarias
2012-03-12 6:58 ` Thomas Petazzoni
2012-03-12 10:14 ` Gustavo Zacarias
2012-03-12 11:33 ` Thomas Petazzoni
2012-03-12 12:07 ` Gustavo Zacarias
2012-03-12 7:00 ` Thomas Petazzoni [this message]
2012-03-19 15:30 ` Thomas Petazzoni
2012-03-19 15:52 ` Gustavo Zacarias
2012-03-19 15:57 ` Thomas Petazzoni
2012-03-19 16:10 ` Gustavo Zacarias
2012-03-19 16:22 ` Peter Korsgaard
2012-03-19 16:38 ` Thomas Petazzoni
2012-03-12 1:58 ` [Buildroot] [PATCH 2/3] libxml-parser-perl: add missing dep and drop wrong paths Gustavo Zacarias
2012-03-12 7:01 ` Thomas Petazzoni
2012-03-12 9:49 ` Gustavo Zacarias
2012-03-12 7:46 ` Thomas Petazzoni
2012-03-12 10:07 ` Gustavo Zacarias
2012-03-12 11:31 ` Thomas Petazzoni
2012-03-12 11:46 ` Gustavo Zacarias
2012-03-12 1:58 ` [Buildroot] [PATCH 3/3] host-microperl: define module paths and other improvements Gustavo Zacarias
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=20120312080042.19fa11bf@skate \
--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