Re: branch-1_4 allow C++ on Linux

[Gary V. Vaughan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Eric!

On 2 Nov 2006, at 07:17, Eric Blake wrote:
> > On 1 Nov 2006, at 16:28, Eric Blake wrote:
> > > > allowing a C++ compilation on Linux can catch
> > > > type errors.  Most other platforms suck in too much of gnulib,
> > > > including bits
> > > > that won't work with C++, but this patch allows a Linux system to
> > > > complete the
> > > > testsuite with './configure CC=g++ --enable-changeword
> > > > --without-included-
> > > > regex'.
> >
> > Have you tried HEAD too?
>
> Not yet - head has changed enough from branch that I am not sure  
> how a C++
> build will fare; plus the fact that it pulls in libtool and more of
> gnulib, so it has more potential points of failure.  It's not my  
> highest
> priority, but it is on the list of cool things to try before 2.0.

Okay, cool.  ISTR that Libtool HEAD builds with C++ already, but even
if gnulib trips up M4 HEAD, forward porting the changes from the branch
is probably a good thing to do anyway.

> > I'll have to get Gettext-0.16 building on
> > Mac OS X before I can build m4 again :-(
>
> Good luck with that.  Actually, if you were to hack configure.ac to  
> drop
> the requirement back to gettext 0.15 in your build tree, Mac might  
> give a
> successful build.  0.15 is only incompatible with automake 1.10+ in  
> the
> sense that it fails to install on systems that lack a decent mkdir 
> (1), but
> I don't think Mac falls in that category.

Good tip, thanks.  I can always install coreutils if Apple's mkdir is
lacking.

> >  http://blog.azazil.net
>
> Your road-trip sounds fun!

It is! :-D

Cheers,
        Gary
- --
Gary V. Vaughan      ())_.  address@hidden
Research Scientist   ( '/   http://blog.azazil.net
GNU Hacker           / )=   http://www.gnu.org/software/{libtool,m4}
Technical Author   `(_~)_   http://sources.redhat.com/autobook




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFFS3FPFRMICSmD1gYRAp9LAJ4oaW2WgXdbQ97FcvteS2vFQ8oriQCfQpdT
G6N/hSfk4yAN9VW/sN4JoJY=
=L71j
-----END PGP SIGNATURE-----