This is the mail archive of the libc-ports@sources.redhat.com mailing list for the libc-ports project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Multilib mips build question


I have a question about building a mips glibc multiple times for a multilib
target.  I want to build glibc for mips with 3 targets (more actually, but 3
will serve to explain my question), mips32r2 with the old 32 bit ABI, mips64r2
with the new 32 bit ABI, and mips64r2 with the 64 bit ABI.

My first thought was to build each in a different location and that works
but it since the libraries for each of these targes wind up in lib, lib32,
and lib64, it seems clear that the intent is to build them into a single
sysroot location with a single set of header files, and have lib, lib32,
and lib64 under that one sysroot location.  That also avoids having duplicate
header files but that leads to my question.

Before rebuilding to a single sysroot I looked at the usr/include directories
for each of these builds and while the include files for the two mips64r2
builds match, the usr/include/huge_vall.h and usr/include/ieee754.h files in
the mips32r2 include directory are different then the mips64r2 ones.  I think
this is due to the Implies files.

The ports/sysdeps/mips directory and the ports/sysdeps/mips/mips64 directory
have Implies that contain:

        # MIPS uses IEEE 754 floating point.
        ieee754/flt-32
        ieee754/dbl-64

But in ports/sysdeps/mips/mips32 directory there is:

        mips
        wordsize-32

I am not sure why this difference exists or if it should.  Can anyone
help me understand why the mips setup is this way?

Steve Ellcey
sellcey@mips.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]