This is the mail archive of the gdb-prs@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb/1458: compile failed on hpux11


The following reply was made to PR build/1458; it has been noted by GNATS.

From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: heppe@techsoftamerica.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/1458: compile failed on hpux11
Date: Tue, 16 Dec 2003 13:08:37 -0500 (EST)

 [Sorry Travis, you just got a copy of this in your mailbox,
  and this one is slightly different].
 
 The problem might already be fixed in the CVS version of gdb.
 Can you try this snapshot and see if it gets past the problem
 in intl/
 
   ftp://sources.redhat.com/pub/gdb/snapshots/current/gdb+dejagnu-weekly-20031216.tar.bz2
 
 Here is a better analysis:
 
   gdb 6.0 has an old copy of intl/
   gdb 6.0 also has libiberty/ that was autoconf'ed with autoconf 2.13.
   libiberty/configure is the first configure script to run,
     so it checks for 'inline' and caches the result
   libiberty/configure checks for 'inline'
   libiberty/configure does not check for 'static inline'
   libiberty/configure decides that 'inline' is supported
   later on, intl/gettextP.h uses 'static inline'
 
 gcc -std=iso9899:1990 does not allow 'static inline',
 so I think that 'static inline' is not in the standard.
 
 gdb 6.1 will have a new libiberty/configure that checks for both
 'inline' and 'static inline'.  This ought to disallow 'inline' on hpux
 11.00 with the particular ansi c compiler that you have.
 
 As a separate issue, gdb has a version of intl/ from 1998.
 That should not affect this problem because libiberty/ runs first
 so the test in libiberty/configure for 'inline' matters.
 
 Michael C


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]