* Cannot run N32 binaries.
@ 2006-11-01 2:08 ` Kaz Kylheku
0 siblings, 0 replies; 6+ messages in thread
From: Kaz Kylheku @ 2006-11-01 2:08 UTC (permalink / raw)
To: linux-mips
Before I start debugging this, I thought I'd poll the mailing list.
I've built an N32 root filesystem: all binaries and libs are "ELF 32-bit
N32 MSB MIPS-III ..."
The kernel (2.6.17.7, 64 bit) that I built does have:
CONFIG_MIPS32_N32=y
The filesystem doesn't boot: init cannot be found.
I copied the N32 filesystem into a subdirectory of an O32 filesystem in
order to have a look.
Basically, for any executable that I try to run, the error is: "No such
file or directory".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Cannot run N32 binaries.
@ 2006-11-01 2:08 ` Kaz Kylheku
0 siblings, 0 replies; 6+ messages in thread
From: Kaz Kylheku @ 2006-11-01 2:08 UTC (permalink / raw)
To: linux-mips
Before I start debugging this, I thought I'd poll the mailing list.
I've built an N32 root filesystem: all binaries and libs are "ELF 32-bit
N32 MSB MIPS-III ..."
The kernel (2.6.17.7, 64 bit) that I built does have:
CONFIG_MIPS32_N32=y
The filesystem doesn't boot: init cannot be found.
I copied the N32 filesystem into a subdirectory of an O32 filesystem in
order to have a look.
Basically, for any executable that I try to run, the error is: "No such
file or directory".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Cannot run N32 binaries.
2006-11-01 2:08 ` Kaz Kylheku
(?)
@ 2006-11-01 4:17 ` Ilya A. Volynets-Evenbakh
-1 siblings, 0 replies; 6+ messages in thread
From: Ilya A. Volynets-Evenbakh @ 2006-11-01 4:17 UTC (permalink / raw)
To: Kaz Kylheku; +Cc: linux-mips
Could be looking for non-existant ld.so.1 (do you have N32 version of it
in /lib32?)
Kaz Kylheku wrote:
> Before I start debugging this, I thought I'd poll the mailing list.
>
> I've built an N32 root filesystem: all binaries and libs are "ELF 32-bit
> N32 MSB MIPS-III ..."
>
> The kernel (2.6.17.7, 64 bit) that I built does have:
>
> CONFIG_MIPS32_N32=y
>
> The filesystem doesn't boot: init cannot be found.
>
> I copied the N32 filesystem into a subdirectory of an O32 filesystem in
> order to have a look.
>
> Basically, for any executable that I try to run, the error is: "No such
> file or directory".
>
>
--
Ilya A. Volynets-Evenbakh
Total Knowledge. CTO
http://www.total-knowledge.com
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Cannot run N32 binaries.
2006-11-01 2:08 ` Kaz Kylheku
(?)
(?)
@ 2006-11-01 13:24 ` Maciej W. Rozycki
-1 siblings, 0 replies; 6+ messages in thread
From: Maciej W. Rozycki @ 2006-11-01 13:24 UTC (permalink / raw)
To: Kaz Kylheku; +Cc: linux-mips
On Tue, 31 Oct 2006, Kaz Kylheku wrote:
> I've built an N32 root filesystem: all binaries and libs are "ELF 32-bit
> N32 MSB MIPS-III ..."
>
> The kernel (2.6.17.7, 64 bit) that I built does have:
>
> CONFIG_MIPS32_N32=y
>
> The filesystem doesn't boot: init cannot be found.
[...]
> Basically, for any executable that I try to run, the error is: "No such
> file or directory".
For a start you could try running a statically linked shell as your
"init", like specifying "init=/bin/bash.static" at your kernel command
line. If that works, check that your shared libraries are where the
shared loader expects them to be -- for n32 that could be "/lib32",
"/usr/lib32", etc., but it depends on how it has been built. Note you can
invoke the loader manually to examine its behaviour (run it without
arguments to get some help) and then there are a couple of LD_*
environment variables that it recognizes that may aid you with figuring
out what is wrong (you may have to look at the sources for how to use them
though).
Maciej
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Cannot run N32 binaries.
@ 2006-11-01 16:32 ` Kaz Kylheku
0 siblings, 0 replies; 6+ messages in thread
From: Kaz Kylheku @ 2006-11-01 16:32 UTC (permalink / raw)
To: linux-mips
Ilya A. Volynets-Evenbakh wrote:
> Could be looking for non-existant ld.so.1 (do you have N32
> version of it
> in /lib32?)
That is correct. If I make a /lib32 -> lib symbolic link, everything
runs.
I actually built the libs under /lib, but I did not realize that ld
simply writes a hard-coded path for the dynamic linker into executables.
That is to say, I built an all-n32 system, using /lib and /usr/lib.
This is elegant, but probably a bad idea, so I will go back to the
/lib32 scheme.
^ permalink raw reply [flat|nested] 6+ messages in thread
* RE: Cannot run N32 binaries.
@ 2006-11-01 16:32 ` Kaz Kylheku
0 siblings, 0 replies; 6+ messages in thread
From: Kaz Kylheku @ 2006-11-01 16:32 UTC (permalink / raw)
To: linux-mips
Ilya A. Volynets-Evenbakh wrote:
> Could be looking for non-existant ld.so.1 (do you have N32
> version of it
> in /lib32?)
That is correct. If I make a /lib32 -> lib symbolic link, everything
runs.
I actually built the libs under /lib, but I did not realize that ld
simply writes a hard-coded path for the dynamic linker into executables.
That is to say, I built an all-n32 system, using /lib and /usr/lib.
This is elegant, but probably a bad idea, so I will go back to the
/lib32 scheme.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2006-11-01 16:32 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-01 2:08 Cannot run N32 binaries Kaz Kylheku
2006-11-01 2:08 ` Kaz Kylheku
2006-11-01 4:17 ` Ilya A. Volynets-Evenbakh
2006-11-01 13:24 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2006-11-01 16:32 Kaz Kylheku
2006-11-01 16:32 ` Kaz Kylheku
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.