Comments on: Chapter 7: Cross-Compilation and the Eclipse IDE

By: Sud

Sud — Fri, 27 Apr 2018 02:56:25 +0000

Hello, I’m not finding any .dtb files in overlays directory
id@debian930:~/linux/arch/arm/boot/dts/overlays$ ls *.dtb
ls: cannot access ‘*.dtb’: No such file or directory

Did anyone encounter this ? if so how to resolve this.

Thanks in advance.

By: Sud

Sud — Sat, 14 Apr 2018 03:51:18 +0000

I’m getting an error when I run (page 300) make -j 6 ARCH=arm CROSS_COMPILE=${CC} zImage modules dtbs

It says Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong not protected by compiler

By: RR

RR — Mon, 09 Apr 2018 01:58:18 +0000

Brendan — You are a lifesaver. This even worked within Eclipse IDE.

By: Idan

Idan — Thu, 05 Apr 2018 10:53:06 +0000

I think this one is obsolete for debian 9 (strech)
and instead , people should try this one:
https://wiki.debian.org/Multiarch/HOWTO
(or keep using the Linaro toolchain)

By: KrzysztofK

KrzysztofK — Sat, 17 Mar 2018 05:49:24 +0000

Brendan,
Many thanks for your tip! It worked in my case. The first time I reproduced chapter with Eclipse and QEMU cross compilation worked, then stopped with the error:
/lib/ld-linux-armhf.so.3: No such file or directory
Adding export QEMU_LD_PREFIX=/usr/arm-linux-gnueabihf to ~/bashrc fixed the problem.

By: Brendan Lynskey

Brendan Lynskey — Sat, 06 Jan 2018 21:38:03 +0000

For the.so problem, add the following to your ~/.bashrc script:

export QEMU_LD_PREFIX=/usr/arm-linux-gnueabihf

By: DC

DC — Fri, 25 Aug 2017 15:35:43 +0000

All was going well until page 278 when I attempted to sftp the testrpi file. I can’t even seem to ping the Pi from my Debian VB. Do I need to set the network settings on the Debian in some specific way, other than default? Within Debian, the network is attached to NAT with Cable Connected enabled.

I’m using an Ethernet cable directly from my laptop running the Debain VB to the Pi. I can ping it just fine from the command prompt under Windows, so the problem is not the cable. Any ideas?

Thank you,
DC

By: Mitchell

Mitchell — Mon, 15 May 2017 17:31:22 +0000

I know this is an old post, but for anybody else looking for a solution I was able to get it to work by entering the complete path to GDB in the debug configuration. (GDB Debugger field in the Debugger tab of the Debug configuration dialog) In my case, this is:

/home/baldwinm/tools/arm-bcm2708/gcc-linaro-arm-linux-gnueabihf-raspbian-x64/bin/arm-linux-gnueabihf-gdb

Entering just the name of the linaro toolchain debugger (“arm-linux-gnueabihf-gdb”) led to the same “Unknown version” error for me, despite having the path to the linaro tools in my PATH environment variable.

Hope this helps.

By: Mitchell

Mitchell — Mon, 15 May 2017 17:21:14 +0000

Check out your sources.list:

cat /etc/apt/sources.list

If there is an entry that starts, “deb:cdrom…” comment it out (by placing a # character at the start of the line)

This will force apt update to search the online repositories instead of looking on the CDROM image.

Hope this helps…

By: Tom Betka

Tom Betka — Sat, 06 May 2017 01:01:35 +0000

Nishand D’silva, You might need to remove the references to the Debian CD ROM in the /etc/apt/sources.list file. You’ll have to edit the file as the superuser though, so Google around a bit for tips if you don’t already know how to do this (and haven’t already gotten this resolved).