search

bmanojlovic / rpi-cross-compile

Raspbian cross compile chroot creator
10 stars 7 forks source link

qemu-binfmt-conf.sh command not found #5

Closed realies closed 9 years ago

realies commented 9 years ago

I'm getting an error when I try to load raspbian_run start on a vagrant debian 7.7.0 amd64

vagrant@debian-7:~/rpi-cross-compile$ sudo ./raspbian_run start ++ which qemu-binfmt-conf.sh

bmanojlovic commented 9 years ago

This line states it should be ok (this is debian based startup of "service") service binfmt-support start [ ok ] Enabling additional executable binary formats: binfmt-support.

my script after tries to detect if /proc/sys/fs/binfmt_misc has arm entry which is required for transparent execution of arm binaries. Can you please do ls /proc/sys/fs/binfmt_misc/ There should be multiple "entries", and another question is did you install required qemu packages (from readme)?

realies commented 9 years ago

Hi, I've installed everything from README.md and ls /proc/sys/fs/binfmt_misc/ returns python2.6 qemu-cris qemu-ppc qemu-sh4eb status python2.7 qemu-m68k qemu-ppc64 qemu-sparc qemu-alpha qemu-microblaze qemu-ppc64abi32 qemu-sparc32plus qemu-arm qemu-mips qemu-s390x qemu-sparc64 qemu-armeb qemu-mipsel qemu-sh4 register

From the above I should understand that the qemu packages are fine, so can you please tell me how to build arm binaries, since I've tried compiling x264 from git and when I load the x264 binary to the RPi it says that it can't be executed, I'm guessing I've been building x86_x64 binary.

Thanks

bmanojlovic commented 9 years ago

it looks to me it has changed from arm to qemu-arm so just ignore error and you should be fine

On Mon, Dec 8, 2014 at 2:09 PM, realies notifications@github.com wrote:

Hi, I've installed everything from README.md and ls /proc/sys/fs/binfmt_misc/ returns python2.6 qemu-cris qemu-ppc qemu-sh4eb status python2.7 qemu-m68k qemu-ppc64 qemu-sparc qemu-alpha qemu-microblaze qemu-ppc64abi32 qemu-sparc32plus qemu-arm qemu-mips qemu-s390x qemu-sparc64 qemu-armeb qemu-mipsel qemu-sh4 register

From the above I should understand that the qemu packages are fine, so can you please tell me how to build arm binaries, since I've tried compiling x264 from git and when I load the x264 binary to the RPi it says that it can't be executed, I'm guessing I've been building x86_x64 binary.

Thanks

— Reply to this email directly or view it on GitHub https://github.com/bmanojlovic/rpi-cross-compile/issues/5#issuecomment-66113595 .

realies commented 9 years ago

What could then be the reason that I can't run the compiled x264 in the Debian on the RPi? Are there any special flags that I need to put?

bmanojlovic commented 9 years ago

can you please send me exact steps you have done so i can try replicating them. it is rather good question can something cpu instruction sensitive as x264 even be compiled with cross compiler?

On Mon, Dec 8, 2014 at 4:30 PM, realies notifications@github.com wrote:

What could then be the reason that I can't run the compiled x264 in the Debian on the RPi?

— Reply to this email directly or view it on GitHub https://github.com/bmanojlovic/rpi-cross-compile/issues/5#issuecomment-66131808 .

realies commented 9 years ago

I think that's pretty much it:

git clone git://git.videolan.org/x264
cd x264

./configure --disable-asm
make
make install
bmanojlovic commented 9 years ago

I have just tested building it in my arm chroot and it compiled just fine, and i can run it (without params) on raspberry pi but why it does not work is not something i can tell you

root@rpi:~# ./x264 -o akio_h264.264 /root/akiyo_qcif.yuv 176x144 raw [error]: raw input requires a resolution. x264 [error]: could not open input file `/root/akiyo_qcif.yuv' root@rpi:~# ls -l /root/akiyo_qcif.yuv -rw-r--r-- 1 root root 11404800 Apr 24 2006 /root/akiyo_qcif.yuv root@rpi:~#

On Mon, Dec 8, 2014 at 5:35 PM, realies notifications@github.com wrote:

I think that's pretty much it:

git clone git://git.videolan.org/x264 cd x264

./configure --disable-asm make make install

— Reply to this email directly or view it on GitHub https://github.com/bmanojlovic/rpi-cross-compile/issues/5#issuecomment-66142868 .

realies commented 9 years ago

Running the x264 on the Pi results in this:

pi@raspberrypi ~ $ sudo ./x264 ./x264: 1: ./x264: ELF: not found ./x264: 2: ./x264: Syntax error: "(" unexpected

bmanojlovic commented 9 years ago

Please upload this binary so I can test it and see what it is really On Dec 8, 2014 9:54 PM, "realies" notifications@github.com wrote:

Running the x264 on the Pi results in this:

pi@raspberrypi ~ $ sudo ./x264 ./x264: 1: ./x264: ELF: not found ./x264: 2: ./x264: Syntax error: "(" unexpected

— Reply to this email directly or view it on GitHub https://github.com/bmanojlovic/rpi-cross-compile/issues/5#issuecomment-66185337 .

realies commented 9 years ago

It should be accessible from here: http://realies.no-ip.org:81/x264

bmanojlovic commented 9 years ago

i think you misunderstood what that raspbian_run script do. You are supposed to chroot into /opt/db_raspbian using "sudo chroot /opt/db_raspbian" . I presume you have done running debootstrap_raspbian_chroot

On Mon, Dec 8, 2014 at 10:23 PM, realies notifications@github.com wrote:

It should be accessible from here: http://realies.no-ip.org:81/x264

— Reply to this email directly or view it on GitHub https://github.com/bmanojlovic/rpi-cross-compile/issues/5#issuecomment-66189897 .

realies commented 9 years ago

Hello and thanks for the clarification. I have been compiling without setting up the chroot first, which has caused building using the wrong tools. Now I can crosscompile successfully, still struggling with how to configure the libraries paths, but getting along nicely. Is it possible to get a general explanation of what are the raspbian_run and debootstrap_raspbian_chroot scripts doing? And possibly have it in the read me for people like me. Thanks : )

bmanojlovic commented 9 years ago

Thanks you for comments, will try to update README when i find enough time. Happy holidays!