[etherlab-users] Cross Compile for ARM
Thomas Bitsky Jr
tbj at automateddesign.com
Fri Jun 28 01:36:09 CEST 2013
Thank you again.
Thomas C. Bitsky Jr. | Lead Developer
ADC | automateddesign.com<http://automateddesign.com/>
P: 630-783-1150 F: 630-783-1159 M: 630-632-6679
From: Gavin Lambert [mailto:gavinl at compacsort.com]
Sent: Thursday, June 27, 2013 6:12 PM
To: Thomas Bitsky Jr; etherlab-users at etherlab.org
Subject: RE: [etherlab-users] Cross Compile for ARM
DESTDIR=/path/to/target/root/fs make install
INSTALL_MOD_PATH=/path/to/target/root/fs make modules_install
depmod -b /path/to/target/root/fs 3.2.46
From: Thomas Bitsky Jr [mailto:tbj at automateddesign.com]
Sent: Friday, 28 June 2013 11:04
To: Gavin Lambert; etherlab-users at etherlab.org<mailto:etherlab-users at etherlab.org>
Subject: RE: [etherlab-users] Cross Compile for ARM
Ah, thanks.
I've gotten as far as "make" and "make modules" successfully. How does one "depmod" into the target file system I've set up for the ARM board instead of into the development file system?
Thanks!
Thomas C. Bitsky Jr. | Lead Developer
ADC | automateddesign.com<http://automateddesign.com/>
P: 630-783-1150 F: 630-783-1159 M: 630-632-6679
From: Gavin Lambert [mailto:gavinl at compacsort.com]
Sent: Thursday, June 27, 2013 5:34 PM
To: Thomas Bitsky Jr; etherlab-users at etherlab.org<mailto:etherlab-users at etherlab.org>
Subject: RE: [etherlab-users] Cross Compile for ARM
IIRC, the --with-linux-dir option cannot cope with relative paths nor ~ prefixed paths. Specify the absolute path from / instead.
From: etherlab-users-bounces at etherlab.org<mailto:etherlab-users-bounces at etherlab.org> [mailto:etherlab-users-bounces at etherlab.org] On Behalf Of Thomas Bitsky Jr
Sent: Thursday, 27 June 2013 13:41
To: etherlab-users at etherlab.org<mailto:etherlab-users at etherlab.org>
Subject: [etherlab-users] Cross Compile for ARM
I'm trying to cross-compile the EtherCAT master for an ARM board. I successfully built a Linux RT Prempt kernel for the device. On my development machine, the source tree where I built the kernel is at: ~/srcroot/linux/linux-3.2.46
I moved into the EtherLAB directory and issued:
./configure --host=arm-linux --enable-generic --with-linux-dir=~/srcroot/linux/linux-3.2.46
The result is:
No configured Linux kernel sources in ~/srcroot/linux/linux-3.2.46/
But I just built a kernel there. Is there something I have to do to the source tree to get it ready to build the ethercat master?
Thanks in advance,
Tome
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20130627/95abd6b7/attachment-0004.htm>
More information about the Etherlab-users
mailing list