[ntp:questions] Help with cross-compiling NTP for the Raspberry Pi requested
David Taylor
david-taylor at blueyonder.co.uk.invalid
Fri Mar 7 12:01:51 UTC 2014
On 06/03/2014 20:24, Rob Windgassen wrote:
> On Thu, 06 Mar 2014 16:20:27 +0000, David Taylor wrote:
[]
>> How, in very simple terms, may I apply the same for cross-compiling NTP?
>
> When your kernel cross-compile was succesful you want to use the same
> compiler.
> You can achieve that by setting CC on the line with configure like
>
> CC=/home/david/kernel/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/
> arm-bcm2708hardfp-linux-gnueabi/bin/gcc \
> ../configure
Rob, Harlan,
Thanks for your continuing help.
Harlan, I wish it were as easy as setting the path, but doing an "ls" on
that directory shows that all the tools have the prefix in front of
their normal file name, for example:
$ ls
/home/david/kernel/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin/
arm-bcm2708hardfp-linux-gnueabi-addr2line bcm2708hardfp-addr2line
arm-bcm2708hardfp-linux-gnueabi-ar bcm2708hardfp-ar
arm-bcm2708hardfp-linux-gnueabi-as bcm2708hardfp-as
arm-bcm2708hardfp-linux-gnueabi-c++ bcm2708hardfp-c++
arm-bcm2708hardfp-linux-gnueabi-cc bcm2708hardfp-cc
arm-bcm2708hardfp-linux-gnueabi-c++filt bcm2708hardfp-c++filt
arm-bcm2708hardfp-linux-gnueabi-cpp bcm2708hardfp-cpp
arm-bcm2708hardfp-linux-gnueabi-ct-ng.config bcm2708hardfp-ct-ng.config
arm-bcm2708hardfp-linux-gnueabi-elfedit bcm2708hardfp-elfedit
arm-bcm2708hardfp-linux-gnueabi-g++ bcm2708hardfp-g++
arm-bcm2708hardfp-linux-gnueabi-gcc bcm2708hardfp-gcc
arm-bcm2708hardfp-linux-gnueabi-gcc-4.7.1 bcm2708hardfp-gcc-4.7.1
Rob,
I tried setting the CC variable as you suggested, and it does then show
the cross-compiler when the version is checked:
CCPREFIX=/home/david/kernel/tools/arm-bcm2708/arm-bcm2708hardfp-linux-gnueabi/bin/arm-bcm2708hardfp-linux-gnueabi-
export CCPREFIX
CC=${CCPREFIX}gcc
export CC
${CC} --version
However, as above, I guess that still leaves all the other tools used in
the NTP build (such as CCLD) pointing at the wrong version of the
executables. I can then do a configure and make, but the executables
are still not the expected size (again, I guess, because the wrong tools
are being used).
Any further suggestions?
--
Thanks,
David
Web: http://www.satsignal.eu
More information about the questions
mailing list