All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nuno Mota <nrmmota@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] ELFCLASS issue on building Perl module Term::ReadKey
Date: Fri, 2 Nov 2018 12:27:01 +0000	[thread overview]
Message-ID: <CAAnJVhB-JrAu9P=zXK5q9Wg28XC9LgyZ5+V384FtA6_C=Rx41g@mail.gmail.com> (raw)
In-Reply-To: <CAB0FRsuDcAujD=yBC3kLPnF8voFputTyh2T9aZk97eXcYHzYkA@mail.gmail.com>

I see this is tricky.
What would be the best way to tackle this?

Regards,
Nuno

Fran?ois Perrad <francois.perrad@gadz.org> escreveu no dia quinta,
1/11/2018 ?(s) 17:36:

>
>
> Le jeu. 1 nov. 2018 ? 12:04, Thomas Petazzoni <
> thomas.petazzoni at bootlin.com> a ?crit :
>
>> Hello Nuno,
>>
>> I'm adding Fran?ois and Christopher in Cc, since they are the two
>> developers using/working on Perl support in Buildroot.
>>
>>
> Christopher works on this package, see
> https://patchwork.ozlabs.org/patch/959629/
> https://patchwork.ozlabs.org/patch/956600/
>
> This package is not cross-compilation friendly.
>
> Fran?ois
>
>
>>
>> --
>> Thomas Petazzoni, CTO, Bootlin
>> Embedded Linux and Kernel engineering
>> https://bootlin.com
>> _______________________________________________
>> buildroot mailing list
>> buildroot at busybox.net
>> http://lists.busybox.net/mailman/listinfo/buildroot
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20181102/45f22d13/attachment.html>

  reply	other threads:[~2018-11-02 12:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 20:53 [Buildroot] ELFCLASS issue on building Perl module Term::ReadKey Nuno Mota
2018-11-01 11:04 ` Thomas Petazzoni
2018-11-01 17:36   ` François Perrad
2018-11-02 12:27     ` Nuno Mota [this message]
2018-11-03 21:18       ` Christopher McCrory
2018-11-05 21:25 ` Christopher McCrory
2018-11-05 21:36   ` Nuno Mota
2018-11-08 16:43 ` Christopher McCrory
2018-11-09 18:07   ` Nuno Mota

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='CAAnJVhB-JrAu9P=zXK5q9Wg28XC9LgyZ5+V384FtA6_C=Rx41g@mail.gmail.com' \
    --to=nrmmota@gmail.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.