Re: Fix a passel of libintl/libiconv issues

[Alexandre Oliva <aoliva at redhat dot com>]

On Jul  8, 2003, "Zack Weinberg" <zack@codesourcery.com> wrote:

> The scheme used here is to configure libintl first, then have gcc's
> configure script examine the results of that configuration rather than
> repeating all the work.

Excellent!

> One final note, I would like to come up with a policy for throwing .m4
> files in the top level config directory.  In this patch I did that for
> one of the two .m4 files I slurped out of the gettext distro; but the
> other one I inlined into gcc/aclocal.m4, because it seemed awfully
> small.  However, an all-or-nothing policy probably makes more sense.
> There are other things than aclocal fragments in the top level config
> directory but I suspect they are not long for this world.  Thoughts?

top-level config is the right place for m4 code that we might want to
use in multiple projects that use the top-level tree (I like to think
of it as our aclocal repository), but it's especially useful for code
imported from other projects.  libtool.m4, for example, should
probably be moved in there.  The chunk you copied to GCC's aclocal.m4
would make sense there, as small as it is, such that, when we decide
to start using a new version of gettext, we know exactly which pieces
we may have to update.

> -	-subdirs="$(SUBDIRS)"; for dir in $subdirs; \
> +	-subdirs="$(SUBDIRS)"; for dir in $$subdirs; \

Thanks for fixing this too

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer