From: Ed Schouten <ed@nuxi.nl>
To: DJ Delorie <dj@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Likely incorrect patch: remove the faulty basename() prototype from libiberty
Date: Sun, 29 May 2016 16:36:00 -0000 [thread overview]
Message-ID: <CABh_MKkAhDsyXGZ51zgwbMPe3EftsVvWf_fPz45QovhaBhPmww@mail.gmail.com> (raw)
In-Reply-To: <xnh9dg3jw0.fsf@greed.delorie.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
next prev parent reply other threads:[~2016-05-29 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 14:58 Ed Schouten
2016-05-29 16:32 ` DJ Delorie
2016-05-29 16:36 ` Ed Schouten [this message]
2016-05-29 17:06 ` DJ Delorie
2016-05-29 17:24 ` Ed Schouten
2016-05-29 17:35 ` DJ Delorie
2016-06-02 21:27 ` Joseph Myers
2016-06-03 9:37 ` Ed Schouten
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABh_MKkAhDsyXGZ51zgwbMPe3EftsVvWf_fPz45QovhaBhPmww@mail.gmail.com \
--to=ed@nuxi.nl \
--cc=dj@redhat.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox