[Xenomai-help] xenomai test problem

[Xenomai-help] xenomai test problem

[federico lolli]

[-- Attachment #1: Type: text/plain, Size: 824 bytes --]


 Hi all,I'm trying to install Xenomai on ARM sam9g20.
I compiled the kernel with Xenomai patch and create the filesystem with buildroot.
crosscompiling Xenomai with these commands:

fede@domain.hid$ ./configure --host=arm-linux-gnueabi --enable-arm-eabi --enable-arm-mach=at91sam9 --disable-arm-tsc --enable-static
make DESTDIR=/home/fede/foxg20/kernel/l/ install
I copy the file in the arm-filesystem
but when I try to run / usr / Xenomai / bin
for example, the file latency
get:
./latency
-sh: ./latency:not found
any suggestions?

Federico Lolli
Tel:+39  3476802428
E-mail: federicololli@domain.hid
web: www.federicololli.com


 		 	   		  
_________________________________________________________________
Importa i tuoi amici di Facebook su Messenger
http://www.windowslive.it/importaAmici.aspx

[-- Attachment #2: Type: text/html, Size: 1769 bytes --]

Re: [Xenomai-help] xenomai test problem

[Gilles Chanteperdrix]

federico lolli wrote:
>  Hi all,
> 
> I'm trying to install Xenomai on ARM sam9g20.
> I compiled the kernel with Xenomai patch and create the filesystem with
> buildroot.
> crosscompiling Xenomai with these commands:
> 
> fede@domain.hid$ ./configure
> --host=arm-linux-gnueabi --enable-arm-eabi --enable-arm-mach=at91sam9
> --disable-arm-tsc --enable-static
> make DESTDIR=/home/fede/foxg20/kernel/l/ install
> I copy the file in the arm-filesystem
> but when I try to run / usr / Xenomai / bin
> for example, the file latency
> get:
> ./latency
> -sh: ./latency:not found
> any suggestions?

Could you try compiling with dynamic libraries, to see if
--enable-static could be the issue? Also, you should try running make
DESTDIR=/path/to/buildroot/nfsroot install to install the binaries.

-- 
					    Gilles.

Re: [Xenomai-help] xenomai test problem

[Wolfgang Denk]

Dear federico lolli,

In message <SNT119-W494F38A017E8C5258B4B21B0FB0@domain.hid> you wrote:
>
>  Hi all,I'm trying to install Xenomai on ARM sam9g20.
...
> crosscompiling Xenomai with these commands:
>
> fede@domain.hid$ ./configure --host=arm-linux-gnueabi --enable-arm-eabi --enable-arm-mach=at91sam9 --disable-arm-tsc --enable-static
> make DESTDIR=/home/fede/foxg20/kernel/l/ install

Hm... I see you running "make", but where to you tell it to use a
cross compiler?

> ./latency
> -sh: ./latency:not found

Try running "file ./latency" and verify that this actually an ARM
binary - I guess you used the native compilers, and your ARM system
refuses to run x86 binaries.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@domain.hid
Karl's version of Parkinson's Law: Work expands to  exceed  the  time
alloted it.

Re: [Xenomai-help] xenomai test problem

[Gilles Chanteperdrix]

Wolfgang Denk wrote:
> Dear federico lolli,
> 
> In message <SNT119-W494F38A017E8C5258B4B21B0FB0@domain.hid> you wrote:
>>  Hi all,I'm trying to install Xenomai on ARM sam9g20.
> ...
>> crosscompiling Xenomai with these commands:
>>
>> fede@domain.hid$ ./configure --host=arm-linux-gnueabi --enable-arm-eabi --enable-arm-mach=at91sam9 --disable-arm-tsc --enable-static
>> make DESTDIR=/home/fede/foxg20/kernel/l/ install
> 
> Hm... I see you running "make", but where to you tell it to use a
> cross compiler?

The --host argument passed to configure is used as a compiler prefix.


-- 
					    Gilles.

Re: [Xenomai-help] xenomai test problem

[Gilles Chanteperdrix]

federico lolli wrote:
> 
> I tried with  static libraries and dynamic libraries,  but nothing has
> changed.
> 
> also the command "make DESTDIR = / path / to / buildroot / nfsroot
> install" was not successful.....

Of course /path/to/buildroot/nfsroot is not meant to be used literally,
you were supposed to replace it with the path where you installed
buildroot on your system.

And please do not forget to CC the mailing list.


-- 
					    Gilles.

Re: [Xenomai-help] xenomai test problem

[federico lolli]

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]


federico lolli wrote:
> 
> I tried with  static libraries and dynamic libraries,  but nothing has
> changed.
> 
> also the command "make DESTDIR = / path / to / buildroot / nfsroot
> install" was not successful.....
 
>Of course /path/to/buildroot/nfsroot is not meant to be used literally,
>you were supposed to replace it with the path where you installed
>buildroot on your system.
 

yes yes
I used the command: sudo make DESTDIR=~/buildroot/output/rootfs install
I also put directly on memory card
sudo make DESTDIR=/media/rootfs/  install
but nothing has changed
you may blame the shared library in the /rootfs/lib generated by builroot?




 		 	   		  
_________________________________________________________________
MSN ti offre esattamente quello che cerchi: il tuo browser personale
http://www.pimpit.it/ie8msn/

[-- Attachment #2: Type: text/html, Size: 1827 bytes --]

Re: [Xenomai-help] xenomai test problem

[Gilles Chanteperdrix]

federico lolli wrote:
> federico lolli wrote:
>> I tried with  static libraries and dynamic libraries,  but nothing has
>> changed.
>>
>> also the command "make DESTDIR = / path / to / buildroot / nfsroot
>> install" was not successful.....
>  
>> Of course /path/to/buildroot/nfsroot is not meant to be used literally,
>> you were supposed to replace it with the path where you installed
>> buildroot on your system.
>  
> 
> yes yes
> I used the command: sudo make DESTDIR=~/buildroot/output/rootfs install
> I also put directly on memory card
> sudo make DESTDIR=/media/rootfs/  install
> but nothing has changed
> you may blame the shared library in the /rootfs/lib generated by builroot?

Usually
./latency: not found
means that the loader that would be ld-linux.so.3 with glibc, or
something a bit different with uclibc is not found in the filesystem. If
you have ldd on the filesystem, you may try it. Or run readelf on the
host and see that all the libraries are found in the filesystem.

Are you sure you are not mixing the outputs of two different toolchains,
or something along the line?


-- 
					    Gilles.