On Tue, May 20, 2008 at 10:22 AM, Gilles Chanteperdrix <[EMAIL PROTECTED]> wrote: > On Tue, May 20, 2008 at 10:20 AM, Gilles Chanteperdrix > <[EMAIL PROTECTED]> wrote: >> On Tue, May 20, 2008 at 10:19 AM, Paradoxxa <[EMAIL PROTECTED]> wrote: >>> Gilles Chanteperdrix schrieb: >>>> >>>> paradoxxa wrote: >>>> > Gilles Chanteperdrix schrieb: >>>> > > On Mon, May 19, 2008 at 4:28 PM, paradoxxa <[EMAIL PROTECTED]> >>>> wrote: >>>> > > > >> Gilles Chanteperdrix schrieb: >>>> > >> > >>> On Mon, May 19, 2008 at 3:04 PM, paradoxxa >>>> <[EMAIL PROTECTED]> wrote: >>>> > >>> >>>> > >>> > >>>> Gilles Chanteperdrix schrieb: >>>> > >>>> >>>> > >>>> > >>>>> On Mon, May 19, 2008 at 2:17 PM, paradoxxa >>>> <[EMAIL PROTECTED]> wrote: >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> No, you are talking about CONFIG_DEBUG_LL, I am talking about >>>> > >>>>> CONFIG_DEBUG_INFO. These are two different options. So, this make >>>> at >>>> > >>>>> least two options that you changed. Could you check if a kernel >>>> with >>>> > >>>>> an unmodified defconfig boots ? >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> >>>> > >>>>> > >>>> The CONFIG_DEBUG_INFO is already set in the >>>> defconfig. The >>>> > >>>> CONFIG_DEBUG_LL i >>>> > >>>> set manually. >>>> > >>>> As well I had to changed the AT91 Master Clock Frequency. >>>> > >>>> >>>> > >>>> Here are the logs of a unmodified defconfig boot: >>>> > >>>> >>>> > >>>> > >>> Ok. But this is a boot with your old compiler. >>>> Could you try a >>>> > >>> defconfig build (with I-pipe AT91 master clock frequency modified) >>>> > >>> with CodeSourcery compiler ? >>>> > >>> If you can not get CodeSourcery compiler to compile correctly a >>>> Linux >>>> > >>> kernel, I can send you the 2007q3 compiler, or you could try to >>>> > >>> compile the kernel with your old compiler, and to compile >>>> user-space >>>> > >>> with CodeSourcery compiler. >>>> > >>> >>>> > >>> > >> I tried it with the both compiler. When i execute >>>> /usr/xenomai/bin/latency i >>>> > >> get the message "sh: /usr/xenomai/bin/latency: not found" >>>> > >> > > >>>> > > Have you tried running file, ldd, or readelf on the binary to see >>>> what >>>> > > it is made of ? >>>> > > >>>> > > > >> By the way, how i can figure out if the binary or the >>>> compiler is a >>>> > >> oabi/eabi file/compiler? >>>> > >> > > >>>> > > codesourcery compiles for eabi by default. So, you have to enable >>>> eabi >>>> > > in kernel configuration to be able to run binaries generated by >>>> > > codesourcery compiler. >>>> > > >>>> > > > The eabi was disabled in the kernel configuration. But to enable >>>> it make > no changes. >>>> > > > $ file usr/xenomai/bin/latency >>>> > usr/xenomai/bin/latency: ELF 32-bit LSB executable, ARM, version 1 > >>>> (SYSV), for GNU/Linux 2.6.14, dynamically linked (uses shared libs), not > >>>> stripped >>>> > > > $ ldd usr/xenomai/bin/latency >>>> > not a dynamic executable >>>> >>>> This is wrong. ldd should be run on the target, not on the host. Also >>>> check that /usr/xenomai/lib is in the ld.so.conf on your target (and >>>> that you have run ldconfig) or use LD_LIBRARY_PATH >>>> >>>> > > $ readelf --sections /usr/xenomai/bin/latency >>>> >>>> I was rather thinking about readelf -d /usr/xenomai/bin/latency >>>> >>>> >>> >>> I actuall don't have ldd and readelf on the target. I did a ldconfig -p. The >>> Xenomai Libraries were listed there. >> >> readelf can work on the host. But ldd on the target is the best way to >> know if the installation worked correctly. If you are looking for ldd, >> it is compiled as part of the glibc. You may even found it in the >> toolchain files. > > Actually ldd is a script, it is not compiled.
All what it does is launching LD_TRACE_LOADED_OBJECTS=1 /usr/xenomai/bin/latency So, you do not even need the script. -- Gilles _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
