On 09/03/2014 23:20, John Hasler wrote:
I believe you want this:
libcap-dev - development libraries and header files for libcap2
Thanks, John. I was trying that first as the easiest solution, but that
package is already installed, and the latest version.
--
Cheers,
David
Web:
On 09/03/2014 01:53, Mike George wrote:
David:
It doesn't look like libcap is included in the rpi toolchain.
I was able to build a kernel using the directions on your website
but I failed building NTP. I think capability.h should be present under
On 08/03/2014 23:11, Mike George wrote:
David:
The configure script checks to see if you have the necessary
dependencies for the options you have
chosen. If not, it sets the option to no. You should see it reported
in the messages.
Of course the compile will also work, just without the option
David:
I sent you some suggestions off-list for setting up the cross-compile
environment.
Mike
On 3/9/2014 09:21, David Taylor wrote:
On 09/03/2014 01:53, Mike George wrote:
David:
It doesn't look like libcap is included in the rpi toolchain.
I was able to build a kernel using the
I believe you want this:
libcap-dev - development libraries and header files for libcap2
--
John Hasler
jhas...@newsguy.com
Dancing Horse Hill
Elmwood, WI USA
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
Initial write-up is here:
http://www.satsignal.eu/raspberry-pi/kernel-cross-compile.html#ntp
Comments and corrections welcomed. Many, many thanks for the group
here, without whose help this would not have been possible for this
Linux novice.
--
Cheers,
David
Web: http://www.satsignal.eu
David:
Maybe your build environment is missing libcaps.
On my ubuntu machine that I built NTP on I installed
libcap2
libcap-dev
Not sure if I needed the -dev but I didn't try without it.
Mike
On 3/8/2014 07:14, David Taylor wrote:
David:
The configure script checks to see if you have the necessary
dependencies for the options you have
chosen. If not, it sets the option to no. You should see it reported
in the messages.
Of course the compile will also work, just without the option you
requested.
I think there was
David:
It doesn't look like libcap is included in the rpi toolchain.
I was able to build a kernel using the directions on your website
but I failed building NTP. I think capability.h should be present under
On 06/03/2014 20:24, Rob Windgassen wrote:
On Thu, 06 Mar 2014 16:20:27 +, 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
David Taylor writes:
On 06/03/2014 20:24, Rob Windgassen wrote:
On Thu, 06 Mar 2014 16:20:27 +, 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
On 07/03/2014 12:24, Harlan Stenn wrote:
David Taylor writes:
[]
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
Hi--
On Mar 7, 2014, at 7:30 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
[ ... ]
No, still getting an ntpd which is 2.87 MB in size, whereas on the Raspberry
Pi native build it's 2.0 MB. The Intel Debian version is 2.74 MB.
Run 'file ntpd' to see which architecture it's
In article lfcomm$at5$1...@dont-email.me David Taylor
david-tay...@blueyonder.co.uk.invalid writes:
There's a discrepancy here I am unsure about. When I run the script:
sntp/libevent/build-aux/config.guess
on the Raspberry Pi, for host I get:
armv6l-unknown-linux-gnueabihf
but, as
David Taylor writes:
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/
On 2014-03-07 13:42, David Taylor wrote:
On 07/03/2014 18:10, Charles Swiger wrote:
Hi--
On Mar 7, 2014, at 7:30 AM, David Taylor
david-tay...@blueyonder.co.uk.invalid wrote:
[ ... ]
No, still getting an ntpd which is 2.87 MB in size, whereas on the Raspberry Pi
native build it's 2.0 MB.
--target should not be needed.
Only --build (where is it being built) and --host (where will it be
running) should matter.
H
--
Brian Inglis writes:
On 2014-03-07 13:42, David Taylor wrote:
On 07/03/2014 18:10, Charles Swiger wrote:
Hi--
On Mar 7, 2014, at 7:30 AM, David Taylor
I am trying to cross-compile NTP for the Raspberry Pi, and I am
following the instructions for NTP here:
http://support.ntp.org/bin/view/Dev/Cross-compilingNTP
and the successful cross-compile I did for the RPi kernel here:
http://www.satsignal.eu/raspberry-pi/kernel-cross-compile.html
David Taylor writes:
I am trying to cross-compile NTP for the Raspberry Pi, and I am
following the instructions for NTP here:
http://support.ntp.org/bin/view/Dev/Cross-compilingNTP
and the successful cross-compile I did for the RPi kernel here:
On Wed, 05 Mar 2014 09:43:34 +, David Taylor wrote:
I am trying to cross-compile NTP for the Raspberry Pi, and I am
following the instructions for NTP here:
http://support.ntp.org/bin/view/Dev/Cross-compilingNTP
and the successful cross-compile I did for the RPi kernel here:
20 matches
Mail list logo
