This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] Replacing gcc's dependence on libiberty's fnmatch to gnulib's fnmatch
- From: Manuel López-Ibáñez <lopezibanez at gmail dot com>
- To: ayush goel <ayushgoel1610 at gmail dot com>
- Cc: Gcc Patch List <gcc-patches at gcc dot gnu dot org>, Joseph Myers <joseph at codesourcery dot com>
- Date: Mon, 25 Jul 2016 23:08:19 +0100
- Subject: Re: [PATCH] Replacing gcc's dependence on libiberty's fnmatch to gnulib's fnmatch
- Authentication-results: sourceware.org; auth=none
- References: <CAGp8FVXDpmi_WF2EUAtV2jFX5GJctE_-mfLnORDbn9ptfkSkyQ@mail.gmail.com>
On 25 July 2016 at 18:18, ayush goel <firstname.lastname@example.org> wrote:
> On top of the previously filed patch for importing gnulib (the link
> isn’t available on the archive yet, however this contains some of the
> information: http://gcc.1065356.n5.nabble.com/Importing-gnulib-into-the-gcc-tree-td1275807.html#a1279573)
> now I have replaced another function from libiberty with the
> corresponding version from gnulib.
> Even though in both OSX and GNU/Linux, fnmatch is provided by the GNU
> libc already, so the copy in libiberty is not used in your systems.
> However since the objective is to replace whatever functions can be
> leveraged by gnulib, these changes have been made.
Why the change from "fnmatch.h" to <fnmatch.h>?
Also, are the files in gnulib and libiberty semantically identical?
The wiki page does not say anything about this. How did you check
GCC can run on other systems besides OSX and GNU/Linux, how can you
test that your change does not break anything on those systems?