I got another buildbot notification and as far as I can tell it has nothing to do with my last commit. The stdio output is at http://buildbot.scipy.org/MacOSX%20x86/builds/49/step-shell/0 And the errors seem to be of this sort: _configtest.c: In function 'main': _configtest.c:4: error: 'isnan' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.) _configtest.c: In function 'main': _configtest.c:4: error: 'isnan' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.) _configtest.c: In function 'main': _configtest.c:4: error: 'isinf' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.) _configtest.c: In function 'main': _configtest.c:4: error: 'isinf' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.) I haven't had any problems compiling on my own machine. Chuck
Charles R Harris wrote:
I got another buildbot notification and as far as I can tell it has nothing to do with my last commit. The stdio output is at
http://buildbot.scipy.org/MacOSX%20x86/builds/49/step-shell/0 <http://buildbot.scipy.org/MacOSX%20x86/builds/49/step-shell/0>
That's not the output of the thing that failed. The build succeeded, but the following step, trying to run the unit tests, failed. http://buildbot.scipy.org/MacOSX%20x86/builds/49/step-shell_2/0 It appears to me that there is some confusion about which Python is being executed. The tests seem to expect Python 2.5: sys.path=["numpy-install/lib/python2.5/site-packages"] whereas the install is picking up Python 2.3: byte-compiling ../numpy-install/lib/python2.3/site-packages/numpy/dual.py to dual.pyc Barry, can you check this and make sure that the correct Python gets picked up during the build? Thanks.
And the errors seem to be of this sort:
_configtest.c: In function 'main': _configtest.c:4: error: 'isnan' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once
_configtest.c:4: error: for each function it appears in.) _configtest.c: In function 'main': _configtest.c:4: error: 'isnan' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once
_configtest.c:4: error: for each function it appears in.)
_configtest.c: In function 'main': _configtest.c:4: error: 'isinf' undeclared (first use in this function)
_configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.) _configtest.c: In function 'main': _configtest.c:4: error: 'isinf' undeclared (first use in this function)
_configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.)
I haven't had any problems compiling on my own machine.
Those aren't errors that would stop the build; they just tell the config command that isnan() and isinf() aren't available on the platform. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
Sorry about the hassle. It was working fine before a reboot. I'll try to fix it this evening. barry On 9/14/07, Robert Kern <robert.kern@gmail.com> wrote:
Charles R Harris wrote:
I got another buildbot notification and as far as I can tell it has nothing to do with my last commit. The stdio output is at
http://buildbot.scipy.org/MacOSX%20x86/builds/49/step-shell/0 <http://buildbot.scipy.org/MacOSX%20x86/builds/49/step-shell/0>
That's not the output of the thing that failed. The build succeeded, but the following step, trying to run the unit tests, failed.
http://buildbot.scipy.org/MacOSX%20x86/builds/49/step-shell_2/0
It appears to me that there is some confusion about which Python is being executed. The tests seem to expect Python 2.5:
sys.path=["numpy-install/lib/python2.5/site-packages"]
whereas the install is picking up Python 2.3:
byte-compiling ../numpy-install/lib/python2.3/site-packages/numpy/dual.py to dual.pyc
Barry, can you check this and make sure that the correct Python gets picked up during the build? Thanks.
And the errors seem to be of this sort:
_configtest.c: In function 'main': _configtest.c:4: error: 'isnan' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once
_configtest.c:4: error: for each function it appears in.) _configtest.c: In function 'main': _configtest.c:4: error: 'isnan' undeclared (first use in this function) _configtest.c:4: error: (Each undeclared identifier is reported only once
_configtest.c:4: error: for each function it appears in.)
_configtest.c: In function 'main': _configtest.c:4: error: 'isinf' undeclared (first use in this function)
_configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.) _configtest.c: In function 'main': _configtest.c:4: error: 'isinf' undeclared (first use in this function)
_configtest.c:4: error: (Each undeclared identifier is reported only once _configtest.c:4: error: for each function it appears in.)
I haven't had any problems compiling on my own machine.
Those aren't errors that would stop the build; they just tell the config command that isnan() and isinf() aren't available on the platform.
-- Robert Kern
"I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
participants (3)
-
Barry Wark -
Charles R Harris -
Robert Kern