From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16361 invoked by alias); 26 Feb 2003 00:08:12 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 16352 invoked from network); 26 Feb 2003 00:08:11 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by 172.16.49.205 with SMTP; 26 Feb 2003 00:08:11 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 18nr0Z-0000Dm-00 for ; Tue, 25 Feb 2003 20:09:20 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 18np7J-0008GA-00 for ; Tue, 25 Feb 2003 19:08:09 -0500 Date: Wed, 26 Feb 2003 00:08:00 -0000 From: Daniel Jacobowitz To: gdb-patches@sources.redhat.com Subject: Re: [rfc] configury: CC_HAS_UINTPTR_T Message-ID: <20030226000809.GA31684@nevyn.them.org> Mail-Followup-To: gdb-patches@sources.redhat.com References: <200302252321.h1PNLfa13347@duracef.shout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200302252321.h1PNLfa13347@duracef.shout.net> User-Agent: Mutt/1.5.1i X-SW-Source: 2003-02/txt/msg00678.txt.bz2 On Tue, Feb 25, 2003 at 05:21:41PM -0600, Michael Elizabeth Chastain wrote: > This is my first 'configure' patch, so I don't expect it to pass on > the first draft. If there's anything I need to know about this > kind of stuff, tell me please. > > This patch just adds CC_HAS_UINTPTR_T. After this patch, I'll write > patches to procfs.c and gdb_thread_db.h to use the new variable, so that > they can put out a more informative compile error than the dreck that > they cough up right now. I've seen several reports from the field where > this actually happens (pr gdb/660 is one case). Could you call it something different? Autoconfism for this would be HAVE_UINTPTR_T. You say yourself that it's a property of the C library, not of the CC. > +dnl See if C library supports "uintptr_t" type. > +dnl AC_CHECK_TYPE is not enough because this type lives in a header file. > + > +AC_MSG_CHECKING(for uintptr_t in C library) > +AC_CACHE_VAL(gdb_cv_c_uintptr_t, > +[AC_TRY_RUN([ No no. Use AC_TRY_COMPILE; never run a test that you don't actually need runtime output for. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer