Bug #74265 [Asn->Csd]: Build problems after 7.0.17 release: undefined reference to `isfinite'

[email protected]
Newsgroups php.bugs
Message-ID <[email protected]>
Edit report at https://bugs.php.net/bug.php?id=74265&edit=1

 ID:                 74265
 Updated by:         [email protected]
 Reported by:        deferraz at terra dot com dot br
 Summary:            Build problems after 7.0.17 release: undefined
                     reference to `isfinite'
-Status:             Assigned
+Status:             Closed
 Type:               Bug
 Package:            Compile Failure
 Operating System:   CentOS-5
 PHP Version:        7.0.17
 Assigned To:        nikic
 Block user comment: N
 Private report:     N

 New Comment:

I had the problem with PHP 7.1.3 on AIX, and the patch fixed it. thanks.


Previous Comments:
------------------------------------------------------------------------
[2017-03-17 22:27:29] deferraz at terra dot com dot br

I think i found the problem on the rpm build server:

In the new pristine server i had installed autoconf-2.59-12 m4-1.4.5-3 , and in the rpm build server i had installed autoconf-2.65 and m4-1.4.13, for that reason , on CentOS 5 that chack for isfinite function using autoconf2.65 that test doesnt fail and with autoconf-2.59 it fails (Right now I can't say why).

Using the distribution vanilla packages of autoconf/m4 that isfinite test fails and the patch that you sent builds successfully.

I am including this information on this bug report so anyone with the same problem can fix the situation

Thanks for the quick patch response and information about this issue

------------------------------------------------------------------------
[2017-03-17 21:01:31] deferraz at terra dot com dot br

I think that i found the possible issue, on the vanilla build the config.log says that isfinite is not found, and my other build server that i do my rpm builds finds the function:

Upstream config.log snippet:
configure:131360: $? = 0
configure:131362: ./conftest
configure:131365: $? = 0
configure:131384: result: no
configure:131398: checking whether isfinite is declared
configure:131423: cc -c -I/usr/include -g -O2 -fvisibility=hidden  conftest.c >&5
conftest.c: In function 'main':
conftest.c:383: error: 'isfinite' undeclared (first use in this function)
conftest.c:383: error: (Each undeclared identifier is reported only once
conftest.c:383: error: for each function it appears in.)
configure:131429: $? = 1


My rpm build server:

configure:95014: checking whether isfinite is declared
configure:95014: cc -c -I/usr/include -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -fno-strict-aliasing -Wno-pointer-sign -fvisibility=hidden  conftest.c >&5
configure:95014: $? = 0
configure:95014: result: yes


The funny thing on this situation that for what I understand those functions are related to math.h and math library that I use the original ones from CentOS distro

------------------------------------------------------------------------
[2017-03-17 20:48:49] deferraz at terra dot com dot br

Indeed, the buildconf --force solved the problem , but i only got a successfull build against the upstream source without any patches , on my rpm spec build the problem persisted and the buildconf --force executes for every build.

There is something that I can analyze to catch the possible problem on my rpm build? The patch had applied and buildconf executes without problem, right now I am without any clues

Thanks in advance

------------------------------------------------------------------------
[2017-03-17 19:50:50] [email protected]

Did you run ./buildconf --force prior to running ./configure?

------------------------------------------------------------------------
[2017-03-17 19:34:16] deferraz at terra dot com dot br

Hi,

unfortunately i had the same problem on the rpm build and on a different vm using ./configure ; make after applying the patch

------------------------------------------------------------------------


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

    https://bugs.php.net/bug.php?id=74265


--
Edit this bug report at https://bugs.php.net/bug.php?id=74265&edit=1
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.