[etherlab-users] install on non-PC

[Jeff Krasky]

> Try this:
>
> ./configure --prefix=/home/user1/buildroot-2011.05/output/target/opt \ 

> --with-linux-dir=/home/user1/buildroot-2011.05/output/build/linux-2.6.33 \

> --enable-generic --host=arm-unknown-linux-uclibcgnueabi-

 
 
Here is the latest output:
 

user1 at dhcppc15:~/Desktop/EtherCAT4Atmel/etherlabmaster-4adb56c4198d>
./configure --prefix=/home/user1/buildroot-2011.05/output/target/opt
--with-linux-dir=/home/user1/buildroot-2011.05/output/build/linux-2.6.33
--enable-generic --host=arm-unknown-linux-uclibcgnueabi-

configure: WARNING: if you wanted to set the --build type, don't use --host.

    If a cross compiler is detected then cross compile mode will be used

checking for a BSD-compatible install... /usr/bin/install -c

checking whether build environment is sane... yes

checking for arm-unknown-linux-uclibcgnueabi--strip... no

checking for strip... strip

checking for a thread-safe mkdir -p... /bin/mkdir -p

checking for gawk... gawk

checking whether make sets $(MAKE)... yes

checking for arm-unknown-linux-uclibcgnueabi--g++... no

checking for arm-unknown-linux-uclibcgnueabi--c++... no

checking for arm-unknown-linux-uclibcgnueabi--gpp... no

checking for arm-unknown-linux-uclibcgnueabi--aCC... no

checking for arm-unknown-linux-uclibcgnueabi--CC... no

checking for arm-unknown-linux-uclibcgnueabi--cxx... no

checking for arm-unknown-linux-uclibcgnueabi--cc++... no

checking for arm-unknown-linux-uclibcgnueabi--cl.exe... no

checking for arm-unknown-linux-uclibcgnueabi--FCC... no

checking for arm-unknown-linux-uclibcgnueabi--KCC... no

checking for arm-unknown-linux-uclibcgnueabi--RCC... no

checking for arm-unknown-linux-uclibcgnueabi--xlC_r... no

checking for arm-unknown-linux-uclibcgnueabi--xlC... no

checking for g++... g++

checking whether the C++ compiler works... yes

checking for C++ compiler default output file name... a.out

checking for suffix of executables... 

checking whether we are cross compiling... no

checking for suffix of object files... o

checking whether we are using the GNU C++ compiler... yes

checking whether g++ accepts -g... yes

checking for style of include used by make... GNU

checking dependency style of g++... gcc3

checking build system type... i686-suse-linux-gnu

checking host system type... Invalid configuration
`arm-unknown-linux-uclibcgnueabi-': machine
`arm-unknown-linux-uclibcgnueabi' not recognized

configure: error: /bin/sh autoconf/config.sub
arm-unknown-linux-uclibcgnueabi- failed

user1 at dhcppc15:~/Desktop/EtherCAT4Atmel/etherlabmaster-4adb56c4198d> 

 

 

 

I then did this to show that the compiler is at least in the PATH:

 

user1 at dhcppc15:~/Desktop/EtherCAT4Atmel/etherlabmaster-4adb56c4198d>
arm-unknown-linux-uclibcgnueabi-gcc

arm-unknown-linux-uclibcgnueabi-gcc: no input files

user1 at dhcppc15:~/Desktop/EtherCAT4Atmel/etherlabmaster-4adb56c4198d>
 
 
Does EtherCAT not like the compiler I am pointing it to?  That compiler, as
far as I know, was what compiled the entire Linux kernel and file system, so
it should be good enough, right?
 
Thanks again,
 
 
Jeff
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.etherlab.org/pipermail/etherlab-users/attachments/20111117/51b016c5/attachment-0004.htm>