From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v11 2/9] perl: new package
Date: Tue, 06 Nov 2012 02:05:52 +0100 [thread overview]
Message-ID: <50986270.4070804@mind.be> (raw)
In-Reply-To: <CAB0FRsvaWPoSfSOv1uyPjpzHMU4a_hxPF_jB4XEhuVUFg4KcSQ@mail.gmail.com>
On 11/05/12 17:41, Fran?ois Perrad wrote:
>> > $/home/bernd/.fbr/build/output/build/perl-5.16.1/Cross/run-qemu-i386
>> > /home/bernd/.fbr/build/output/host/usr/bin/make all PERL_CORE=1
>> > LIBPERL_A=libperl.so
>> > qemu: Unsupported syscall: 240
>> > qemu: Unsupported syscall: 240
>> >
>> > First I got this error message with Debian Squeeze i386 (virtualbox guest,
>> > Win XP host), but also on Debian wheezy amd64 running non-virtualized.
>> >
>> > My .config can be found here:http://pastebin.com/yz1SzeB2
>> > I am using buildroot as part of the FLI4L source package[1].
>> >
>> > Kind regards, Bernd
>> >
> I could reproduce the lastest problem on the HEAD of Buildroot with
> qemu_x86_defconfig (which is a smaller config than your FLI4L config).
Is it possible that this is because the target binary is created with
kernel headers 3.2, but you're running it on a host which is only 2.6.32
(squeeze)? But then it should work on wheezy, because that has 3.2 as
well (at least since about four months IIRC). Although... 240 on i386
is futex, which has existed already since long before 2.6.32.
I do find this bug report:
https://bugs.launchpad.net/ubuntu/+source/qemu-linaro/+bug/758424
but I'm not sure if it is relevant.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-11-06 1:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 13:13 [Buildroot] [PATCH v11 1/9] host-qemu: new package Francois Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 2/9] perl: " Francois Perrad
2012-10-30 20:20 ` Bernd Kuhls
2012-11-05 16:41 ` François Perrad
2012-11-06 1:05 ` Arnout Vandecappelle [this message]
2012-11-06 7:08 ` Thomas Petazzoni
2012-11-06 10:28 ` Alexander Khryukin
2012-11-06 21:09 ` Bernd Kuhls
2012-11-06 22:59 ` Arnout Vandecappelle
2012-11-07 19:32 ` Bernd Kuhls
2012-11-08 15:04 ` Arnout Vandecappelle
2012-11-06 21:03 ` Bernd Kuhls
2012-11-06 10:24 ` François Perrad
2012-11-06 16:23 ` François Perrad
2012-11-08 18:02 ` François Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 3/9] perl: add DB_File Francois Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 4/9] gdbm: new package Francois Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 5/9] perl: add GDBM_File Francois Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 6/9] perl: add option "custom install" Francois Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 7/9] perl: prepare the removal of microperl Francois Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 8/9] cpanminus: new package Francois Perrad
2012-10-19 13:13 ` [Buildroot] [PATCH v11 9/9] microperl: remove it Francois Perrad
2012-11-03 16:10 ` [Buildroot] [PATCH v11 1/9] host-qemu: new package Peter Korsgaard
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=50986270.4070804@mind.be \
--to=arnout@mind.be \
--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