Hi,
I had problem building make files for existing project because autconf
was falling, we had look around I found
the autoconf was falling because macro definition which looks like this
AC_DEFUN([NAME],
[
some code
],
[
more code
Hello Husam,
* Husam Senussi wrote on Sun, Sep 06, 2009 at 11:00:58AM CEST:
> I had problem building make files for existing project because
> autconf was falling, we had look around I found
> the autoconf was falling because macro definition which looks like this
>
> AC_DEFUN([NAME],
> [
>
How do you test to see if the compiler supports a given option?
Specifically, gcc -municode
___
Autoconf mailing list
Autoconf@gnu.org
http://lists.gnu.org/mailman/listinfo/autoconf
How do you test to see if the compiler supports a given option?
Specifically, gcc -municode
i would do that:
CFLAGS_save="${CFLAGS}"
CFLAGS="${CFLAGS} -municode"
AC_COMPILE_IFELSE(
[AC_LANG_PROGRAM([[]])],
[have_unicode="yes"],
[have_unicode="no"])
AC_MSG_CHECKING([whether the compi
* NightStrike wrote on Sun, Sep 06, 2009 at 12:08:23PM CEST:
> How do you test to see if the compiler supports a given option?
You could temporarily add it to CFLAGS and either do a compile or link
test, to find out. That won't catch (non-GCC) compilers though that
only produce a warning upon unk
Hi,
On Sun, 6 Sep 2009 06:08:23 -0400
NightStrike wrote:
>How do you test to see if the compiler supports a given option?
>
>Specifically, gcc -municode
I guess vanilla autoconf does not have a generic macro
to check the availability of the options. For example,
the availability of "-g", "-std=
Yes. The latter is the public API. The third argument is currently
used by some code, but is not part of the public API, so you should
not use it.
OK will change them because with third argument result on having
autconf
inserting the macro as is instead of executing the macro.
Do you know
