Thanks for the suggestions Peter, these are good ones.
What I have done is remove the ltib installation completely and start from a fresh start with the CD iso image. I then more carefully checked the settings as I went through ./ltib --configure and the build progressed through u-boot, the kernel, uclibc and bombed on busybox/applets this time.
So, ... I am doing that again and trying to find a more conservative set of settings with ..ltib configure. I *think* at this point that my configure settings are to blame and I blindly went ahead without checking them more carefully.
I'll report back when I make a bit more progress.
Charles
On Thu, Feb 3, 2011 at 1:10 PM, Peter Barada <address@hidden> wrote:
On 02/03/2011 02:54 PM, Charles Krinke wrote:
I'm having a little trouble with a different LTIB on a
different computer then I have been working with and I think the
environment is not quite set right.
The new ltib is "mpc8323x_rdb-20081112" downloaded from
Freescale's web site. This is loaded into a different Linux
computer recently formatted with Debian. After running the install
and then running "./ltib", I get this error:
+ make ARCH=powerpc CROSS_COMPILE= 'HOSTCC=/usr/bin/gcc
-B/usr/bin//' oldconfig
HOSTCC scripts/basic/docproc
/bin/sh: scripts/basic/fixdep: cannot execute binary file
make[1]: *** [scripts/basic/docproc] Error 126
make: *** [scripts_basic] Error 2
error: Bad exit status from
/opt/ltib-mpc832x_rdb-20081112/tmp/rpm-tmp.8465 (%build)
So, ... I think since the CROSS_COMPILE variable is empty *and* I
see scripts/basic/fixdep having a problem, this is probably an
environment issue.
It does look like the ltib installation did add to my path as the
last line in ~/.bashrc now reads:
So, .... I wonder if someone could give me a hint or two, please?
Do a "file scripts/basic/fixdep" to see what it is. Is it an
executable you can actually run on your host? Are you running on an
x64 machine and don't have the 32-bit libraries installed (which can
be solved in Ubuntu by "sudo apt-get install ia32-libs")?