Sven <[EMAIL PROTECTED]> writes:
|> also i think at least in the non glibc part everything is fine, since i
|> was able to boot from a cross compiled linux/apus kernel.
Please take a look at the libc.so linker script (perhaps
/usr/local/ppc-linux/lib/libc.so) and check that the paths in there are
> Using sys-include instead of include is at least unusual...
in binutils, ./configure --target=ppc --with-headers=/other/usr/include
create /usr/local/ppc/sys-include and copies /other/usr/include/* in it.
> Seems so, yes. Do you also have cross-binutils? (You need them.)
i compiled a cross bi
> /usr/local/arch_specific_name/sys-include and not include, like it
> is the default in dpkg-cross.
Using sys-include instead of include is at least unusual... Don't know
if there's a reason for this. You can either make a symlink include ->
sys-include, or change the crossinc variable in
/etc/d
3 matches
Mail list logo
