This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: Likely incorrect patch: remove the faulty basename() prototype from libiberty
- From: Ed Schouten <ed at nuxi dot nl>
- To: DJ Delorie <dj at redhat dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Sun, 29 May 2016 18:36:05 +0200
- Subject: Re: Likely incorrect patch: remove the faulty basename() prototype from libiberty
- Authentication-results: sourceware.org; auth=none
- References: <CABh_MKn1yUfKjtZO4nZ+XyvVXHUgtD7QE-hAM-AP6FNH=zKooQ at mail dot gmail dot com> <xnh9dg3jw0 dot fsf at greed dot delorie dot com>
Hi there,
2016-05-29 18:32 GMT+02:00 DJ Delorie <dj@redhat.com>:
> Most likely, you're not calling configure right, else it would have seen
> the right prototype and skipped this part of the header. Or libiberty's
> configure and tests need to check for libgen.h as well as the other
> headers it's checking for.
Exactly. ./configure does not check for the existence of libgen.h, nor
does it try to include it anywhere in its codebase.
> Either way, you can't blindly depend on a header being present and
> useful. "Seems to" is insufficient evidence that a patch is correct.
For the local change I'm going to make to the FreeBSD base system and
ports collection, this works for me. I'm merely forwarding the patch
that I'm currently using.
That said, we can easily validate whether <libgen.h> is always
present. What's the official list on which GDB is supposed to build?
It's merely a matter of going down that list and looking at
documentation/source files.
--
Ed Schouten <ed@nuxi.nl>
Nuxi, 's-Hertogenbosch, the Netherlands
KvK-nr.: 62051717