[SciPy-User] Build Problems On SLES11SP1 64-Bit

[Wempa, Kristofer]

Scipy Users,

            I ran into a build problem and I didn't see this particular problem in the bug database or in the mailing list.  I get a build failure when attempting to build scipy 0.8.0 on a SLES11SP1 64-bit server.  Previously, I've built scipy the exact same way on 6 different SLES10 platforms (SP1, SP2 and SP3, both 32-bit and 64-bit).  None of those builds had problems.  However, on SLES11, I got the following errors:

creating build/temp.linux-x86_64-2.7/scipy/sparse/sparsetools
compile options: '-I/siglinux/tc/sles11sp1_gcc-4.3.4_x86-64/sig1/Python-2.7/lib/python2.7/site-packages/numpy/core/include -I/siglinux/tc/sles11sp1_gcc-4.3.4_x86-64/sig1/Python-2.7/include/python2.7 -c'
g++: scipy/sparse/sparsetools/csr_wrap.cxx
scipy/sparse/sparsetools/csr_wrap.cxx: In function âint require_size(PyArrayObject*, npy_intp*, int)â:
scipy/sparse/sparsetools/csr_wrap.cxx:2910: error: expected `)' before âPRIdPTRâ
scipy/sparse/sparsetools/csr_wrap.cxx:2910: warning: spurious trailing â%â in format
scipy/sparse/sparsetools/csr_wrap.cxx:2910: warning: too many arguments for format
scipy/sparse/sparsetools/csr_wrap.cxx:2917: error: expected `)' before âPRIdPTRâ
scipy/sparse/sparsetools/csr_wrap.cxx:2917: warning: spurious trailing â%â in format
scipy/sparse/sparsetools/csr_wrap.cxx:2917: warning: too many arguments for format
scipy/sparse/sparsetools/csr_wrap.cxx: In function âint require_size(PyArrayObject*, npy_intp*, int)â:
scipy/sparse/sparsetools/csr_wrap.cxx:2910: error: expected `)' before âPRIdPTRâ
scipy/sparse/sparsetools/csr_wrap.cxx:2910: warning: spurious trailing â%â in format
scipy/sparse/sparsetools/csr_wrap.cxx:2910: warning: too many arguments for format
scipy/sparse/sparsetools/csr_wrap.cxx:2917: error: expected `)' before âPRIdPTRâ
scipy/sparse/sparsetools/csr_wrap.cxx:2917: warning: spurious trailing â%â in format
scipy/sparse/sparsetools/csr_wrap.cxx:2917: warning: too many arguments for format
error: Command "g++ -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O3 -Wall -fPIC -I/siglinux/tc/sles11sp1_gcc-4.3.4_x86-64/sig1/Python-2.7/lib/python2.7/site-packages/numpy/core/include -I/siglinux/tc/sles11sp1_gcc-4.3.4_x86-64/sig1/Python-2.7/include/python2.7 -c scipy/sparse/sparsetools/csr_wrap.cxx -o build/temp.linux-x86_64-2.7/scipy/sparse/sparsetools/csr_wrap.o" failed with exit status 1

The commands I ran to build were:

export ATLAS=/siglinux/tc/sles11sp1_gcc-4.3.4_x86-64/sig1/atlas-3.8.3/lib
export ATLAS_LPATH= /siglinux/tc/sles11sp1_gcc-4.3.4_x86-64/sig1/atlas-3.8.3/lib
export ATLAS_IPATH=` /siglinux/tc/sles11sp1_gcc-4.3.4_x86-64/sig1/atlas-3.8.3/include
export LDFLAGS=" -Wl,-rpath -Wl,${ATLAS_LPATH} -shared"
python setup.py build

Apparently, the PRIdPTR from inttypes.h isn't getting expanded.  I dug a little deeper and found that I could force it to expand them by defining the __STDC_FORMAT_MACROS macro.  The workaround I used was to set my CFLAGS as follows:

            export CFLAGS=" -D__STDC_FORMAT_MACROS"

Even though this workaround resolved the issue, I am wondering if there is something else that I should have done.  If not, then the build process should be defining this macro automatically to avoid this error.  Thanks.

            Kris


________________________________
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20101007/12c39ec5/attachment.html>