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] Fix microperl
Date: Wed, 7 Mar 2012 16:50:35 +0100	[thread overview]
Message-ID: <20120307165035.6f9d0f84@skate> (raw)
In-Reply-To: <d35484b93145763e6c0dcb6274f4954e@zacarias.com.ar>

Le Wed, 07 Mar 2012 12:29:21 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :

> It has a limitation on modules at the moment, they must be of the pm 
> (interpreted) type rather than the more complex xs ones (C usually).
> That's because full perl is required for xs which in turn requires a 
> full-blown configuration.

Ok.

> For the most part it checks for libc functions and presence of other 
> libs, and platform details (sizeof... and so on).
> At the moment this would be "important" (not for me though) to get 
> target autoconf/automake going since there are new required modules 
> which are XS when the auto* packages were versioned bumped.

Could you expand on this, because I'm not sure I got what you said.

> The proper solution would probably be define the lowest denominator
> for libc, say uclibc-0.9.31, generate a cache on a qemu/working
> target and get that back into the package.

A bit like what we do for ./configure scripts already, at the end of
package/Makefile.in, correct?

Regards,

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

  reply	other threads:[~2012-03-07 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 21:09 [Buildroot] [PATCH] Fix microperl Arnout Vandecappelle
2012-03-06 21:21 ` Peter Korsgaard
2012-03-06 21:31   ` Joshua Jackson
2012-03-07  8:06   ` Thomas Petazzoni
2012-03-07 15:29     ` Gustavo Zacarias
2012-03-07 15:50       ` Thomas Petazzoni [this message]
2012-03-07 16:04         ` 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=20120307165035.6f9d0f84@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