>> Do you really consider it a good idea that a4local.m4 is part of
>> the build system (i.e, stepmake) instead of the package itself? Or
>> is there a different m4 file used for package specific
>> configuration?
>
> Yes, the package-specific stuff goes in configure.in.
Hmm. Local M4 routines s
On wo, 2009-07-22 at 00:15 +0200, Werner LEMBERG wrote:
> Do you really consider it a good idea that a4local.m4 is part of the
> build system (i.e, stepmake) instead of the package itself? Or is
> there a different m4 file used for package specific configuration?
Yes, the package-specific stuff
> However, note that aclocal.m4 is part of stepmake/, which was once
> designed to be a lilypond-independent modular simple makefile-build
> system.
>
> Forcing c++ would remove that feature...
Do you really consider it a good idea that a4local.m4 is part of the
build system (i.e, stepmake) inste
On vr, 2009-06-05 at 09:38 +0200, Werner LEMBERG wrote:
> > After having applied my patch and called autogen.sh, I no longer get
> > the warning, but it seems from config.log that gettext test is done
> > with gcc and not g++:
>
> There is an explicit call to AC_LANG_C in the top-level `configure.
2009/6/5 Werner LEMBERG :
> There is an explicit call to AC_LANG_C in the top-level `configure.in'
> file, which should be removed IMHO. Ideally, everything should be run
> with C++ (we only use g++), and the AC_LANG_PUSH/POP trickery -- `also
> in aclocal.m4' -- should be removed, too.
Although
> After having applied my patch and called autogen.sh, I no longer get
> the warning, but it seems from config.log that gettext test is done
> with gcc and not g++:
There is an explicit call to AC_LANG_C in the top-level `configure.in'
file, which should be removed IMHO. Ideally, everything shoul
Werner LEMBERG a écrit :
Without testing it actually: It looks good.
After having applied my patch and called autogen.sh, I no longer get the
warning,
but it seems from config.log that gettext test is done with gcc and not g++:
configure:7001: checking for gettext
configure:7057: gcc -o con
>> The STEPMAKE_GETTEXT function in aclocal.m4 is missing a test for the
>> autoconf version. For the above tool versions I still get the message
>>
>> autoconf <= 2.59 with g++ >= 3.3 gettext test broken.
>> Trying gcc, cross fingers.
>>
>> which is completely bogus.
>
> What do you think of
Werner LEMBERG a écrit :
[autoconf 2.63]
[g++ 4.3.2]
The STEPMAKE_GETTEXT function in aclocal.m4 is missing a test for the
autoconf version. For the above tool versions I still get the message
autoconf <= 2.59 with g++ >= 3.3 gettext test broken.
Trying gcc, cross fingers.
which is comple
[autoconf 2.63]
[g++ 4.3.2]
The STEPMAKE_GETTEXT function in aclocal.m4 is missing a test for the
autoconf version. For the above tool versions I still get the message
autoconf <= 2.59 with g++ >= 3.3 gettext test broken.
Trying gcc, cross fingers.
which is completely bogus.
Werner
10 matches
Mail list logo