Building o32 glibc on mips64
Anyone got any ideas on how to fix this. I'm using binutils 2.16, gcc 3.4.4, and glibc-2.3.5 with the syscall patch. Looks like socket.S is not being generated.
mips64el-unknown-linux-gnu-gcc -mabi=32 ../sysdeps/unix/sysv/linux/recv.S -c - I../include -I. -I/usr/src/glibc-build/socket -I.. -I../libio -I/usr/src/glibc- build -I../sysdeps/mips/elf -I../libidn/sysdeps/unix -I../linuxthreads/sysdeps/u nix/sysv/linux/mips -I../linuxthreads/sysdeps/unix/sysv/linux -I../linuxthreads/ sysdeps/pthread -I../sysdeps/pthread -I../linuxthreads/sysdeps/unix/sysv -I../li nuxthreads/sysdeps/unix -I../linuxthreads/sysdeps/mips -I../sysdeps/unix/sysv/li nux/mips/mips32 -I../sysdeps/unix/sysv/linux/mips -I../sysdeps/unix/sysv/linux - I../sysdeps/gnu -I../sysdeps/unix/common -I../sysdeps/unix/mman -I../sysdeps/uni x/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/mips/mips32 -I../sysdeps/unix/mi ps -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/mips/mips32 -I../sysdeps/mi ps -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/wordsize -32 -I../sysdeps/mips/fpu -I../sysdeps/ieee754 -I../sysdeps/generic/elf -I../sys
deps/generic -D_LIBC_REENTRANT -include ../include/libc-symbols.h -DPIC -D
ASSEMBLER -g -o /usr/src/glibc-build/socket/recv.o -MD -MP -MF /usr/src/glibc
-build/socket/recv.o.dt -MT /usr/src/glibc-build/socket/recv.o ../sysdeps/unix/sysv/linux/recv.S:5:20: socket.S: No such file or directory make[2]: *** [/usr/src/glibc-build/socket/recv.o] Error 1
make[2]: Leaving directory `/usr/src/glibc-2.3.5/socket'
make[1]: *** [socket/subdir_lib] Error 2
make[1]: Leaving directory `/usr/src/glibc-2.3.5'
make: *** [all] Error 2
root:/usr/src/glibc-build#
Signature · 3 lines
---- Jim Gifford [email protected]
Quoted 3 lines · Jim Gifford
Anyone got any ideas on how to fix this. I'm using binutils 2.16, gcc 3.4.4, and glibc-2.3.5 with the syscall patch. Looks like
socket.Sis not being generated.
I have not tried the 2.3.x series glibcs on MIPS64. I recommend you use glibc HEAD for now instead, unless you're interested in tracking down this sort of problem.
Signature · 2 lines
Daniel Jacobowitz CodeSourcery, LLC
Quoted 3 lines · Daniel Jacobowitz
I have not tried the 2.3.x series glibcs on MIPS64. I recommend you use glibc HEAD for now instead, unless you're interested in tracking down this sort of problem.
FYI, I've been able to build glibc 2.3.5 with GCC 4.0.0 for
mips64el-linux (n64) with minimal patching. I think what's only really required is that patch by Richard Sandiford that stays suspended in the glibc Bugzilla.
For o32 glibc may have to be configured for "mips{,el}-linux" (as o32
isn't MIPS64 at all), but that's a pure guess -- I haven't checked the scripts for that requirement.
Do you think HEAD is stable enough for a non-glibc developer? It's soon
after a fork after all, so I'd expect more serious changes to be applied nowadays.
Maciej
Quoted 11 lines · Maciej W. Rozycki
Quoted 3 lines · Daniel Jacobowitz
I have not tried the 2.3.x series glibcs on MIPS64. I recommend you use glibc HEAD for now instead, unless you're interested in tracking down this sort of problem.
FYI, I've been able to build glibc 2.3.5 with GCC 4.0.0 for
mips64el-linux (n64) with minimal patching. I think what's only really required is that patch by Richard Sandiford that stays suspended in the glibc Bugzilla.
Quoted 7 lines
For o32 glibc may have to be configured for "mips{,el}-linux" (as o32
isn't MIPS64 at all), but that's a pure guess -- I haven't checked the scripts for that requirement.Do you think HEAD is stable enough for a non-glibc developer? It's soon
after a fork after all, so I'd expect more serious changes to be applied nowadays.
Btw, what is the chance to see a biarch toolchain for mips? It seems all linux architectures with 32bit and 64bit variants seem to have one these days, except mips.
Quoted 7 lines · Christoph Hellwig
Quoted 3 lines
Do you think HEAD is stable enough for a non-glibc developer? It's soon
after a fork after all, so I'd expect more serious changes to be applied nowadays.Btw, what is the chance to see a biarch toolchain for mips? It seems all linux architectures with 32bit and 64bit variants seem to have one these days, except mips.
What do you mean? Multilib, per chance? If so, please feel free to
build one yourself -- as of 4.0.0 GCC will build libraries for all three ABIs (o32, (n)64 and n32) if configured for mips64{,el}-linux and --enable-multilib is in effect (I think it is by default). Bi-endian is probably tougher, but it should be possible -- GCC itself supports the "-mabi=" and "-mel" and "-meb" switches all the time AFAIK.
Of course you may need to have system libraries installed in place for
all requested configurations as appropriate; at least glibc, but perhaps others as well (gmp, mpfr for Fortran; zlib for Java).
Maciej
Quoted 3 lines · Christoph Hellwig
Btw, what is the chance to see a biarch toolchain for mips? It seems all linux architectures with 32bit and 64bit variants seem to have one these days, except mips.
As Maciej wrote, mips64-linux is already triarch. It's possible to build a multiarch mips-linux toolchain, or a mips64-linux toolchain which supports multilibs but defaults to o32, but neither's real easy. I build mips64-linux toolchains all the time, though.
Signature · 2 lines
Daniel Jacobowitz CodeSourcery, LLC
From my understanding it's only supported when using IRIX shared libraries, but the standard MIPS64 still only builds n32 and n64 only, and not the o32 libraries.
I don't see why GCC didn't just allow all MIPS have that capability.
Signature · 3 lines
---- Jim Gifford [email protected]
Quoted 3 lines · Jim Gifford
From my understanding it's only supported when using IRIX shared libraries, but the standard MIPS64 still only builds n32 and n64 only, and not the o32 libraries.
No, that's not true (assuming "MIPS64" == mips64-linux-gnu). What makes you think so?
Richard