This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [rfa] PROBLEMS (i[3456]86-*-linux*): Require glibc 2.1.3 or later
- From: Joel Brobecker <brobecker at gnat dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: ac131313 at redhat dot com, gdb-patches at sources dot redhat dot com
- Date: Tue, 25 Feb 2003 10:10:15 -0800
- Subject: Re: [rfa] PROBLEMS (i[3456]86-*-linux*): Require glibc 2.1.3 or later
- References: <200302251710.h1PHAhv07449@duracef.shout.net>
> This could be detected at autoconf time, something like:
>
> AC_MSG_CHECKING(for uintptr_t support in glibc)
> AC_CACHE_VAL(ac_cv_c_uintptr_t,
> [AC_TRY_COMPILE(, [
> #include <stdint.h>
> uintptr_t foo;
> ],
> ac_cv_c_uintptr_t=yes, ac_cv_c_uintptr_t=no)])
> AC_MSG_RESULT($ac_cv_c_uintptr_t)
> if test $ac_cv_c_uintptr_t = yes; then
> AC_DEFINE(HAVE_UINTPTR_T)
> fi
>
> Then gdb_thread_db.h could produce a better error message if it
> gets compiled. It's used only on *-*-*linux* and s390-*-*,
> not everywhere.
Why not even fail at autoconf time?
--
Joel