Segmentation fault in __uClibc_main on m68k

[Jaromír Cápík]

"On 29 May 2015 at 13:11, Jaromír Cápík <tavvva at seznam.cz> wrote:
> Hello.
>
> I'm trying to port my uClibc based distro to m68k and experience
> SIGSEGV in __uClibc_main even when linking binaries statically.
>
> I tried to crosscompile the m68k toolchain on i386 (uClibc based)
> and m68k (glibc based) and in both cases the resulting binaries
> segfault.
>
> My biggest sin is that I'm building version 0.9.28 and not the latest
> one as the i386 version of my distro has that version and I didn't
> want to be inconsistent. Anyway, I'm not against the idea of trying
> the latest version, but before doing so I'd like to know whether
> someone on this mailing list can confirm this is a known issue,
> that has been fixed somewhere between 0.9.28 and 0.9.33.2.
> I noticed changes in the libc/sysdeps/linux/m68 directory, but
> I'm unsure whether that can play a role. At least the syscall is
> redesigned completely (it was missing in 0.9.28 and I had to
> hack it using a C source from Internet).
>
> I would appreciate your help / hints / anything.

A m68k (cf) smallish distro bootstrapped fine with current master a
couple of weeks ago.
I did not run it through aranym though. Patches are of course welcome!
"



Hello Bernhard.




I tried all versions from 0.9.28 tll 0.9.33.2

but except 0.9.28 each of them fails

with different error during the build.

The only buildable is 0.9.28, but it segfaults.




It might be caused by component versions on the host

system, but hard to guess. I'm slowly losing a hope.

I'm thinking about backporting the __uclibc_main

stuff to 0.9.28, but that's quite courageous plan.




You mentioned a distro you boottrapped a couple of weeks
ago. Do you have a working rootfs environment I could
test? 

Thanks,
Jaromir.