o32 glibc-2.3.5
hi,
Trying to compile glibc-2.3.5 for o32 patched with syscall, I get an
error for socket.S, socket/recv.o. This is the exact same error mentioned on this list last month. In that thread there was reference to a patch by Richard sandiford. This is with gcc-3.4.4. If anyone knows where I can find said patch, and if that'll fix my problem, I'd greatly appreciate it. I've been looking in glibc's bugzilla but can't find the right bug. Thanks!
-Dave
Signature · 1 line
The way that can be named is not the Way.
Quoted 2 lines · David Cummings
greatly appreciate it. I've been looking in glibc's bugzilla but can't find the right bug. Thanks!
#758
Maciej
Quoted 9 lines · Maciej W. Rozycki
Quoted 2 lines · David Cummings
greatly appreciate it. I've been looking in glibc's bugzilla but can't find the right bug. Thanks!
#758
Maciej
Alright, thanks. I had found that, but it didn't seem to apply to the problem with socket, as that had already been applied when the socket happened. I'm also now having a problem with n32 which is similar if not the same as the one Rolf had not too long ago. Something about a __fork_block not being found. Anyplace else I should look? Thanks, -Dave
Signature · 1 line
The way that can be named is not the Way.
Quoted 3 lines · David Cummings
Alright, thanks. I had found that, but it didn't seem to apply to the problem with socket, as that had already been applied when the socket happened. I'm also now having a problem with n32 which is similar if
socket.S shouldn't be needed as recv.o is expected to be built as a stub
based on syscalls.list. Have you regenerated the configure script corresponding to the changed configure.in template?
Quoted 2 lines
not the same as the one Rolf had not too long ago. Something about a
__fork_blocknot being found. Anyplace else I should look? Thanks,
Check if the symbol is defined where it's expected to.
Source and binary RPM packages of glibc 2.3.5 built for o32 and (n)64 are
available at my site; built with GCC 4.0.0 which is even pickier than 3.4.4. Availability of binary packages means successful builds are possibile. Figuring out how is left as an exercise for the reader; source packages are provided as an aid to that.
Maciej