bug-m4
[Top][All Lists]
Advanced

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

Re: M4 checking failed.


From: chunyee
Subject: Re: M4 checking failed.
Date: Tue, 29 Apr 2008 20:56:25 -0700 (PDT)

Hi Eric,

   OK.  I've run "./configure
gl_cv_func_strtod_works=no" and then "make -f check". 
It seems work & I think I've install the package.

   May I know how can I confirm if the package is
installed ? I saw that there is a 'm4' in
/usr/ccs/bin/ & /usr/xpg4/bin.  However, their file
date are in year 2003 !

Regards,
Ko
--- Eric Blake <address@hidden> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> According to address@hidden on 4/21/2008 4:18 AM:
> | Hi,
> |
> |    I've compiled M4 and then run 'make check' to
> run
> | the self-tests.  However, the following errors are
> | shown.
> |
> | PASS: test-strstr
> | test-strtod.c:738: assertion failed
> |
> |     May I know how to fix this problem ?
> 
> Thanks for the report.  You are not the first to
> notice this; the
> configure test for a working strtod failed to detect
> the particular C99
> strtod() bugs in Solaris.  You can use
> 'gl_cv_func_strtod_works=no
> ./configure' to work around it.  In the meantime,
> the bug in configure has
> been fixed in gnulib.
> 
> Also, you may want to run 'make -k check' to
> continue on with the rest of
> M4's testsuite.
> 
> - --
> Don't work too hard, make some time for fun as well!
> 
> Eric Blake             address@hidden
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (Cygwin)
> Comment: Public key at
> home.comcast.net/~ericblake/eblake.gpg
> Comment: Using GnuPG with Mozilla -
> http://enigmail.mozdev.org
> 
>
iEYEARECAAYFAkgNXM8ACgkQ84KuGfSFAYATUgCgrIsPqyYzyACNDohlmJ0QVXM8
> SsgAoLUMPvXswfJ41WLhruoL8girJUFO
> =zs+7
> -----END PGP SIGNATURE-----
> 



      
____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ




reply via email to

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