Hi,
Le mardi 05 février 2013 à 19:15 +0100, Jan Engelhardt a écrit :
On Sunday 2013-02-03 10:49, Yann Droneaud wrote:
So to create a valid --build argument, I was going to use
--build=`uname -p`-`uname -s` but its producing 'x86_64-Linux' which is
not recognized by config.sub.
--build
[Moving the discussion to autoconf@gnu.org]
Hi,
I've recently sent two patches against config.sub to
config-patc...@gnu.org
http://lists.gnu.org/archive/html/config-patches/2013-02/msg0.html
http://lists.gnu.org/archive/html/config-patches/2013-02/msg1.html
Yann Droneaud (2
with the following patches on config.sub:
http://lists.gnu.org/archive/html/config-patches/2013-02/msg0.html
http://lists.gnu.org/archive/html/config-patches/2013-02/msg1.html
Yann Droneaud (2):
config.sub: use $name instead of $1
config.sub: be more liberal on input case: accept
Le mardi 01 décembre 2009 à 19:25 +0100, Ralf Wildenhues a écrit :
Hello Yann,
* Yann Droneaud wrote on Tue, Dec 01, 2009 at 03:09:11PM CET:
If AC_PROG_CC_C99 successfully found a C99 compliant C compiler,
AC_C_INLINE and AC_C_RESTRICT should use this result.
Testing for inline
Le mardi 01 décembre 2009 à 19:18 +0100, Ralf Wildenhues a écrit :
Hello Yann,
* Yann Droneaud wrote on Tue, Dec 01, 2009 at 03:19:00PM CET:
With any C99 compliant compiler (gcc -std=c99 or clang), restrict
keyword test always found __restrict instead of plain restrict,
eg. config.h
Hi,
If AC_PROG_CC_C99 successfully found a C99 compliant C compiler,
AC_C_INLINE and AC_C_RESTRICT should use this result.
Testing for inline and restrict keywords is redundant,
eg, checking ac_cv_prog_cc_c99 = yes should be enough.
Regards.
--
Yann Droneaud
, there should be no #define for restrict
keyword in this case.
Regards.
--
Yann Droneaud
