From: Maik Steuer <Maik.Steuer@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] no file will execute - shell said always not found
Date: Wed, 21 May 2008 10:58:39 +0200 [thread overview]
Message-ID: <20080521085839.230490@gmx.net> (raw)
Hello,
at the moment I build a toolchain with buildroot for arm xscale (pxa270) with the following config:
Using built-in specs.
Target: arm-linux-uclibc
Configured with: /usr/src/buildroot/toolchain_build_arm/gcc-4.2.3/configure --prefix=/usr --build=i386-pc-linux-gnu --host=i386-pc-linux-gnu --target=arm-linux-uclibc --enable-languages=c,c++ --with-sysroot=/usr/src/buildroot/build_arm/staging_dir --with-build-time-tools=/usr/src/buildroot/build_arm/staging_dir/usr/arm-linux-uclibc/bin --enable-__cxa_atexit --enable-c99 --enable-long-long --enable-symvers=gnu --enable-shared --with-gmp=/usr/src/buildroot/toolchain_build_arm/gmp --with-mpfr=/usr/src/buildroot/toolchain_build_arm/mpfr --disable-nls --enable-threads --disable-multilib --with-float=soft
Thread model: posix
gcc version 4.2.3
I can compile different things, but the shell on the embedded system says only "-sh: ./FILE_TO_EXECUTE: not found" after execute.
Are my gcc configs wrong?
Other toolchains (gcc 4.0.0) for example ELDK from DENX works fine.
My rootfilesystem is an image from toradex and works also fine.
Is it possible that I have to copy something else to the rootfilesystem, which is specific to the actually gcc-version?
I hope sb can help me.
Regards
Maik
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
next reply other threads:[~2008-05-21 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 8:58 Maik Steuer [this message]
2008-05-21 13:15 ` [Buildroot] no file will execute - shell said always not found Rex Ashbaugh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080521085839.230490@gmx.net \
--to=maik.steuer@gmx.de \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox