I can't quite make much of the error you're getting. In what I'm seeing seems 
that gcc is complaining about a function "a-circumflex" near some macro 
expansions.

Here are some suggestions nonetheless, based on the other bits of output:

- Definitely shave the last "boost" off your BOOST_INC_DIR.

- It's strange that the boost headers would be in /usr/local, but the matching 
libraries would be in /usr/lib64.

- You appear to be using gcc 4.1. This here may apply to you: 
http://is.gd/12CmW

Andreas

On Montag 15 Juni 2009, Adlar Kim wrote:
> no, it did not. here's what I'm getting:
>
>
> siteconf.py
> ===========
>
> BOOST_INC_DIR = ['/usr/local/include/boost-1_39/boost']
> BOOST_LIB_DIR = ['/usr/lib64']
> BOOST_COMPILER = 'gcc41'
> BOOST_PYTHON_LIBNAME = ['boost_python-gcc41-mt']
> BOOST_THREAD_LIBNAME = ['boost_thread-gcc41-mt']
> CUDA_TRACE = False
> CUDA_ENABLE_GL = False
> CUDADRV_LIB_DIR = ['/usr/local/cuda/lib']
> CUDADRV_LIBNAME = ['cuda']
> CXXFLAGS = []
> LDFLAGS = []
>
>
> Error
> =====
>
> *** Cannot find Boost headers. Checked locations:
>    /usr/local/include/boost-1_39/boost/boost/python.hpp
> *** Cannot find Boost Python library. Checked locations:
>    /usr/lib64/libboost_python-gcc41-mt.so
>    /usr/lib64/libboost_python-gcc41-mt.dylib
>    /usr/lib64/libboost_python-gcc41-mt.lib
>    /usr/lib64/boost_python-gcc41-mt.so
>    /usr/lib64/boost_python-gcc41-mt.dylib
>    /usr/lib64/boost_python-gcc41-mt.lib
> *** Cannot find Boost Thread library. Checked locations:
>    /usr/lib64/libboost_thread-gcc41-mt.so
>    /usr/lib64/libboost_thread-gcc41-mt.dylib
>    /usr/lib64/libboost_thread-gcc41-mt.lib
>    /usr/lib64/boost_thread-gcc41-mt.so
>    /usr/lib64/boost_thread-gcc41-mt.dylib
>    /usr/lib64/boost_thread-gcc41-mt.lib
>    /usr/lib64/boost_thread-gcc41-mt.so
>    /usr/lib64/boost_thread-gcc41-mt.dylib
>    /usr/lib64/boost_thread-gcc41-mt.lib
> *** Cannot find CUDA driver library. Checked locations:
>    /usr/local/cuda/lib/libcuda.so
>    /usr/local/cuda/lib/libcuda.dylib
>    /usr/local/cuda/lib/libcuda.lib
>    /usr/local/cuda/lib/cuda.so
>    /usr/local/cuda/lib/cuda.dylib
>    /usr/local/cuda/lib/cuda.lib
>    /usr/local/cuda/lib/cuda.so
>    /usr/local/cuda/lib/cuda.dylib
>    /usr/local/cuda/lib/cuda.lib
>    /usr/local/cuda/lib/cuda.so
>    /usr/local/cuda/lib/cuda.dylib
>    /usr/local/cuda/lib/cuda.lib
> *** Note that this may not be a problem as this component is often
> installed system-wide.
> running build
> running build_py
> running build_ext
> building '_driver' extension
> creating build/temp.linux-x86_64-2.4
> creating build/temp.linux-x86_64-2.4/src
> creating build/temp.linux-x86_64-2.4/src/cpp
> creating build/temp.linux-x86_64-2.4/src/wrapper
> gcc -pthread -fno-strict-aliasing -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -
> fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -
> mtune=generic -D_GNU_SOURCE -fPIC -O3 -DNDEBUG -fPIC -Isrc/cpp -I/usr/
> local/include/boost-1_39/boost -I/usr/local/cuda/include -I/usr/lib/
> python2.4/site-packages/numpy-1.3.0-py2.4-linux-x86_64.egg/numpy/core/
> include -I/usr/include/python2.4 -c src/cpp/cuda.cpp -o build/
> temp.linux-x86_64-2.4/src/cpp/cuda.o
> gcc -pthread -fno-strict-aliasing -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -
> fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -
> mtune=generic -D_GNU_SOURCE -fPIC -O3 -DNDEBUG -fPIC -Isrc/cpp -I/usr/
> local/include/boost-1_39/boost -I/usr/local/cuda/include -I/usr/lib/
> python2.4/site-packages/numpy-1.3.0-py2.4-linux-x86_64.egg/numpy/core/
> include -I/usr/include/python2.4 -c src/cpp/bitlog.cpp -o build/
> temp.linux-x86_64-2.4/src/cpp/bitlog.o
> gcc -pthread -fno-strict-aliasing -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -
> fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -
> mtune=generic -D_GNU_SOURCE -fPIC -O3 -DNDEBUG -fPIC -Isrc/cpp -I/usr/
> local/include/boost-1_39/boost -I/usr/local/cuda/include -I/usr/lib/
> python2.4/site-packages/numpy-1.3.0-py2.4-linux-x86_64.egg/numpy/core/
> include -I/usr/include/python2.4 -c src/wrapper/wrap_cudadrv.cpp -o
> build/temp.linux-x86_64-2.4/src/wrapper/wrap_cudadrv.o
> src/wrapper/wrap_cudadrv.cpp: In function â:
> src/wrapper/wrap_cudadrv.cpp:165: error: ârnExâ was not declared in
> this scope
> src/wrapper/wrap_cudadrv.cpp: In function â:
> src/wrapper/wrap_cudadrv.cpp:166: error: ârnExâ was not declared in
> this scope
> src/wrapper/wrap_cudadrv.cpp: In function â:
> src/wrapper/wrap_cudadrv.cpp:167: error: ârnExâ was not declared in
> this scope
> src/wrapper/wrap_cudadrv.cpp: In function â:
> src/wrapper/wrap_cudadrv.cpp:310: error: ârnExâ was not declared in
> this scope
> src/wrapper/wrap_cudadrv.cpp: In function â:
> src/wrapper/wrap_cudadrv.cpp:357: error: ârnExâ was not declared in
> this scope
> error: command 'gcc' failed with exit status 1
>
> On Jun 15, 2009, at 12:13 PM, Andreas Klöckner wrote:
> > On Dienstag 09 Juni 2009, Adlar Kim wrote:
> >> Hi,
> >>
> >> I'm getting the following error when I try to build pycuda-0.93rc.
> >> Could anybody help? Thanks.
> >
> > Did 0.93rc4 work for you? If so, that would be one data point to
> > help me
> > figure out if we're ready for 0.93.
> >
> > Thanks,
> > Andreas
> > _______________________________________________
> > PyCUDA mailing list
> > [email protected]
> > http://tiker.net/mailman/listinfo/pycuda_tiker.net


Attachment: signature.asc
Description: This is a digitally signed message part.

_______________________________________________
PyCUDA mailing list
[email protected]
http://tiker.net/mailman/listinfo/pycuda_tiker.net

Reply via email to