This is the mail archive of the
mailing list for the GCC project.
Re: strverscmp for libiberty
DJ Delorie <email@example.com> writes:
> > It's a GNU extension. At this time there's no other user than GCC,
> > but there might be other users in the future. Should I just put it
> > in GCC? It would still need to be a separate file; I guess I would
> > call the function gcc_strverscmp so as not to conflict with glibc.
> Normally we wait until more than one project uses a given function,
> but as this is something that GNU systems will normally have, that's
> an argument for putting it in libiberty. Ian? Thoughts?
I guess my feeling is that since the function is in glibc, it's OK to
put an implementation into libiberty. It's kind of a weird function,
but what the heck.
Note that the second iteration of the patch has a chance to
Makefile.in, in the stamp-functions target, which seems to require GNU
make. libiberty shouldn't require GNU make, since the other projects
which use it do not.