From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] intltool: no business defining PERLLIB
Date: Mon, 19 Mar 2012 17:38:36 +0100 [thread overview]
Message-ID: <20120319173836.107d5c6c@skate> (raw)
In-Reply-To: <87ipi0ims7.fsf@macbook.be.48ers.dk>
Le Mon, 19 Mar 2012 17:22:00 +0100,
Peter Korsgaard <jacmet@uclibc.org> a ?crit :
> >> Reverted? It was never applied.
>
> Thomas> Sorry, my bad, I thought it had been applied and was the reason of the
> Thomas> failure. I will investigate what is causing this new breakage.
>
> It was afaik the microperl -> gentargets change.
Ah, yes, on the failed cases, I have BR2_PACKAGE_MICROPERL=y.
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-19 16:38 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
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 [this message]
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=20120319173836.107d5c6c@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 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.