On Wed, 2 Nov 2011, Ian Lance Taylor wrote:
> David Daney <david.da...@cavium.com> writes:
>
> > On MIPS we fail because of those. I was going to create a patch to
> > move those two to libcall_linux_{386,amd64}.go. An alternative would
> > be to remove them too.
>
> Moving them sounds good to me. libgo already has a framework for
> architecture specific system calls. It doesn't have a framework for
> glibc version.
autoconf detection of available functions (for functions that aren't
always available for a given target) would be better than basing things on
glibc version, anyway - and in libgo, just as in libstdc++, you can safely
assume target libc is available for running link tests. autoconf
detection will probably be required if anyone wants to build libgo with
uClibc, for example.
--
Joseph S. Myers
jos...@codesourcery.com
