[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

glibc-2.3.1 for cris

From: Uwe Reimann
Subject: glibc-2.3.1 for cris
Date: Thu, 05 Jun 2003 10:33:46 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030516


I'm trying to make glibc-2.3.1 work for the cris architecture (cris-axis-linux-gnu). With a couple of patches I managed to cross compile the lib using gcc-3.2.3. However, I encounter many segfaults, so I decided to do a native build to be able to make check. Glibc seems to behave different when doing a native compile.

First of all, sysdeps/generic/uname.c complained about a missing config-name.h When doing a cross compilation, config-name.h is not beeing created either. uname.c includes it unconditionally, so I guess, uname.c isn't compiled when doing a cross compilation. What IS compiled then?

However, to get my native build, I manually created config-name.h.

The next error I got was about illegal assembler opcodes in sysdeps/unix/fork.S. That's OK, it contains m68k assembler (why is that at this place, btw?). But during cross-compilation, some fork.(S|c) must have been compiled, probably sysdeps/generic/fork.c. Why would glibc use a different fork when doing a native compile?

When doing a diff over config.h from the native and the cross-compilation, I can't see any difference which might cause this behaviour.

Could anybody tell me what could be going wrong?

Best regards, Uwe

reply via email to

[Prev in Thread] Current Thread [Next in Thread]