pspp-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: strnlen on Mingw [Was Re: Stable 20090129 compiled to windows]


From: Michel Boaventura
Subject: Re: strnlen on Mingw [Was Re: Stable 20090129 compiled to windows]
Date: Thu, 5 Feb 2009 02:05:04 -0200

nothing either. I'm starting to think that its maybe a bug on
configure because of this:
on configure.log I get:

configure:34377: result: no
configure:34395: checking whether strnlen is declared
configure:34424: i686-mingw32-gcc -std=gnu99 -c -g -O2
-Wdeclaration-after-statement -fgnu89-inline  conftest.c >&5
conftest.c: In function 'main':
conftest.c:163: error: 'strnlen' undeclared (first use in this function)
conftest.c:163: error: (Each undeclared identifier is reported only once
conftest.c:163: error: for each function it appears in.)
configure:34431: $? = 1

and then this:

configure:58374: checking for working strnlen
configure:58449: result: yes

and on the very bottom, this:

ac_cv_func_strnlen_working=yes


So configure can't find strnlen, and then tells that it works. If you
look at configure script there is:

  { $as_echo "$as_me:$LINENO: checking for working strnlen" >&5
$as_echo_n "checking for working strnlen... " >&6; }
if test "${ac_cv_func_strnlen_working+set}" = set; then
  $as_echo_n "(cached) " >&6
else
  if test "$cross_compiling" = yes; then
  ac_cv_func_strnlen_working=no
else

as far as I understand this, ac_cv_func_strnlen_working from the first
if should be the return of the compile of the strnlen test, and
because its 1 (configure:34431: $? = 1) the first if should return
false, and how we are doing cross_compiling the
ac_func_strnlen_working should be set to 'no', but it is set to yes.

Am I interpreting it wrong?




reply via email to

[Prev in Thread] Current Thread [Next in Thread]