This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Tue, 2002-12-10 at 14:10, Alex Bennee wrote: > Having built my bootstrap gcc and going through the process of building > the beast that is glibc I finally come to a linker error complaining > about some __NR_(socket function) symbols: <snip> I did a bit more digging and I see they are the system call numbers for the Linux kernel, which do not exist in the SuperH's kernels unistd.h. I think the reason is that all socket calls for Linux-SH are multiplexed through the sys_socketcall function. However I'm having a bit of trouble trying to work out how glibc's socket config has come to the decision to use the other method. I think I've applied all the patches I need to. Has anyone else hit this problem building glibc for a sh target? -- Alex Bennee Senior Hacker, Braddahead Ltd The above is probably my personal opinion and may not be that of my employer ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |