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: Joseph Myers <joseph at codesourcery dot com>
- To: Prathamesh Kulkarni <prathamesh dot kulkarni at linaro dot org>
- Cc: ayush goel <ayushgoel1610 at gmail dot com>, Manuel López-Ibáñez <lopezibanez at gmail dot com>, Gcc Patch List <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 29 Jul 2016 22:10:46 +0000
- 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> <CAESRpQD4RXHD6ZL3vwQc0tH7zb2NXyQpPNT8uLgH2orUVPECmg@mail.gmail.com> <CAGp8FVVZiCJ3y2XXzGBpo1x5NpOAqdPzASapP=rYyv=O8oWUSQ@mail.gmail.com> <CAAgBjMnwPzGJd-EDgsUYfRHxOkdg=A_fBrmgdtR+OOT4gRPbMw@mail.gmail.com>
On Tue, 26 Jul 2016, Prathamesh Kulkarni wrote:
> >> 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?
> > Well I have access to these two systems only. How would you suggest I
> > test my patches on all possible systems?
> Maybe building contrib/config-list.mk could help ? AFAIK, it will cross build
> the gcc tree for different targets, but not run the testsuite, however
> I could be wrong.
Building for different targets is fairly irrelevant here; the issue is
building for different hosts, which is harder.
(It's possible there are some portability interfaces only used on
particular targets, but that's not the main use case for libiberty in
Joseph S. Myers