This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils 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: Problems with gcc + exceptions + -pedantic + libiberty.h

From: DJ Delorie <dj at delorie dot com>
To: levon at movementarian dot org
Cc: gcc-patches at gcc dot gnu dot org, binutils at sources dot redhat dot com
Date: Tue, 8 Jan 2002 14:23:02 -0500
Subject: Re: Problems with gcc + exceptions + -pedantic + libiberty.h
References: <20020107235319.GA93680@compsoc.man.ac.uk> <200201080007.g08074U02537@envy.delorie.com> <20020108001602.GC21859@bubble.sa.bigpond.net.au> <200201080028.g080SPb02685@envy.delorie.com> <20020108041738.GG21859@bubble.sa.bigpond.net.au> <200201080428.g084Sl905133@envy.delorie.com> <20020108182657.GA18394@compsoc.man.ac.uk>


> 1) teaching GNU libc string.h to set HAVE_DECL_BASENAME

We have no control over libc.

> 2) including string.h (+ stdio.h) in libiberty.h

What about older platforms that don't have string.h?

> That way the headers will "just work" in C++ without my application having to
> worry about setting HAVE_DECL_BASENAME myself.

Perhaps libiberty could provide a config.h that libiberty.h uses?

References:
- Problems with gcc + exceptions + -pedantic + libiberty.h
  - From: John Levon
- Re: Problems with gcc + exceptions + -pedantic + libiberty.h
  - From: DJ Delorie
- Re: Problems with gcc + exceptions + -pedantic + libiberty.h
  - From: Alan Modra
- Re: Problems with gcc + exceptions + -pedantic + libiberty.h
  - From: DJ Delorie
- Re: Problems with gcc + exceptions + -pedantic + libiberty.h
  - From: Alan Modra
- Re: Problems with gcc + exceptions + -pedantic + libiberty.h
  - From: DJ Delorie
- Re: Problems with gcc + exceptions + -pedantic + libiberty.h
  - From: John Levon

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