On Thursday 17 April 2008 02:40, Denys Vlasenko wrote:
> I believe I solved it with --with-sysroot...
> Will try again and let you know.
So far I only discovered that --with-as="$CROSS-as" is not going to work.
Fixing configure is not enough:
23651 access("x86_64-linux-uclibc-as", X_OK) = -1 ENOENT (No such file or
directory)
Why? You can just try execvp'ing (instead of access()),
and only if that fails, go try other variants...
23651
stat64("/.share/usr/app/gcc-4.3.0-x86_64-linux-uclibc/bin/../libexec/gcc/x86_
23651
stat64("/.share/usr/app/gcc-4.3.0-x86_64-linux-uclibc/bin/../libexec/gcc/as",
23651
stat64("/.share/usr/app/gcc-4.3.0-x86_64-linux-uclibc/bin/../lib/gcc/x86_64-l
23651
stat64("/.share/usr/app/gcc-4.3.0-x86_64-linux-uclibc/bin/../lib/gcc/x86_64-l
23651 vfork() = 23653
23653 execve("/usr/bin/as", ["as", "-v", "-Iinclude", "-Ilibbb",
"-I/.1/usr/srcdev
and *this* as, being native one, makes 32-bit .o files. :(
What happened to the good old concept of looking up executables'
location in $PATH if they have no slashes on the name?
(Oh well)^2. Recompiling with --with-as="/usr/bin/$CROSS-as"...
--
vda
