yade-users team mailing list archive
-
yade-users team
-
Mailing list archive
-
Message #02446
Re: compile YADE on OpenSUSE 11.2 64 bit OS
Hi,
You can change the path (put the full path to ndarrayobject.h)in the
file "SConstruct" located in the yade folder that you loaded with bazar.
I think that the new versions of python are not depakaged in the same
way for all linux distributions, and on the other hand downgrading
python may lead your system to not behave normally.
You'll meet other path problems while building scons, so you need to
make changes manually but no more in this file, error messages will
tell you on which file changes should be done.
Le mercredi 03 mars 2010 à 10:44 -0500, Peiying Hsieh a écrit :
> Hi,
>
> Attached is the output from scons. Basically, it cannot find
> numpy/ndarrayobject.h, but, it is in my path.
> How to tell scons the complete path of ndarrayobject.h?
>
> Thanks!
> Pei
> --------------
> phsieh@jupiter:~/dem/yade-trunk> echo $PATH
> /usr/lib64/python2.6/site-packages/numpy/core/include/numpy/:/usr/lib64/mpi/gcc/openmpi/bin:/home/phsieh/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin
> phsieh@jupiter:~/dem/yade-trunk> export
> PATH=/usr/lib64/python2.6/site-packages/numpy:$PATH
> phsieh@jupiter:~/dem/yade-trunk> scons version=trunk
> PREFIX=/home/phsieh/YADE optimize=1
> features=gts,vtk,opengl,openmp,cgal
> scons: Reading SConscript
> files ...
> @@@ Using profile default (scons.profile-default)
> @@@
> Yade version is `trunk' (unknown), installed files will be suffixed
> with `-trunk'.
> All intermediary files will be in
> `/home/phsieh/dem/build-trunk'.
> Checking whether c++ compiler "g++"
> works...yes
> Finding libstdc++ library...
> (cached) /usr/lib64/gcc/x86_64-suse-linux/4.4/libstdc
> ++.so
> Checking for pthread_exit(NULL) in C library pthread...
> yes
> Checking for boost::system::error_code(); /* non-essential */ in C++
> library boost_system-mt... yes
> Checking for boost::thread::thread() in C++ library boost_thread-mt...
> yes
> Checking for boost::posix_time::time_duration::time_duration() in C++
> library boost_date_time-mt... yes
> Checking for boost::filesystem::path() in C++ library
> boost_filesystem-mt... yes
> Checking for boost::iostreams::file_sink("") in C++ library
> boost_iostreams-mt... yes
> Checking for boost::regex("") in C++ library boost_regex-mt...
> yes
> Checking for try{} catch (const boost::archive::archive_exception& e)
> {} in C++ library boost_serialization-mt... yes
> Checking for boost::program_options::options_description o in C++
> library boost_program_options-mt... yes
> Checking for C++ header file boost/foreach.hpp...
> yes
> Checking for sqlite3_close(0L) in C++ library sqlite3...
> yes
> Checking for Python development files...
> yes
> Checking for python module `IPython' ...(cached)
> yes
> Checking for boost::python::scope() in C++ library boost_python-mt...
> yes
> Checking for C++ header file numpy/ndarrayobject.h...
> no
>
> One of the essential libraries above was not found, unable to
> continue.
>
> Check `/home/phsieh/dem/build-trunk/config.log' for possible causes,
> note that there are options that you may need to customize:
>
>
> PREFIX: Install path prefix
> default: /usr/local
> actual: /home/phsieh/YADE
>
> runtimePREFIX: Runtime path prefix; DO NOT USE, inteded for packaging
> only.
> default:
> None
>
> actual: /home/phsieh/YADE
>
> variant: Build variant, will be suffixed to all files, along with
> version (beware: if PREFIX is the same, headers of the older version
> will still be overwritten
>
> default:
>
> actual:
>
> debug: Enable debugging information and disable optimizations (yes|no)
> default: 0
> actual: False
>
> gprof: Enable profiling information for gprof (yes|no)
> default: 0
> actual: False
>
> optimize: Turn on heavy optimizations (yes|no)
> default: 1
> actual: True
>
> exclude: Yade components that will not be built
> (all|none|comma-separated list of names)
> allowed names: gui extra common dem lattice snow
> default: none
> actual:
>
> PGO: Whether to "gen"erate or "use" Profile-Guided Optimization (|gen|
> use)
>
> default:
>
> actual:
>
> features: Optional features that are turned on
> (all|none|comma-separated list of names)
> allowed names: opengl log4cxx cgal openmp gts vtk python eigen
> nowm3 never_use_this_one
> default:
> log4cxx,opengl,gts,openmp,vtk
> actual: cgal gts opengl openmp
> vtk
>
> jobs: Number of jobs to run at the same time (same as -j, but saved)
> default: 2
> actual: 2
>
> buildPrefix: Where to create build-[version][variant] directory for
> intermediary files
>
> default: ..
>
> actual: ..
>
> linkStrategy: How to link plugins together (per-class|per-pkg[broken]|
> monolithic|static[broken])
> default:
> monolithic
> actual:
> monolithic
>
> chunkSize: Maximum files to compile in one translation unit when
> building plugins.
> default:
> 7
> actual:
> 7
>
> version: Yade version (if not specified, guess will be attempted)
> default: None
> actual: trunk
>
> CPPPATH: Additional paths for the C preprocessor (colon-separated)
>
> default: /usr/include/vtk-5.2:/usr/include/vtk-5.4:/usr/include/eigen2
>
> actual: /usr/include/vtk-5.2 /usr/include/vtk-5.4 /usr/include/eigen2 /home/phsieh/dem/build-trunk/include/yade-trunk /home/phsieh/dem/build-trunk/include/yade-trunk/yade/lib-miniWm3 /usr/include/python2.6
>
> LIBPATH: Additional paths for the linker (colon-separated)
> default: None
> actual:
>
> QTDIR: Directories where to look for qt3
>
> default: /usr/share/qt3:/usr/lib/qt:/usr/lib/qt3:/usr/qt/3:/usr/lib/qt-3.3
>
> actual: /usr/share/qt3 /usr/lib/qt /usr/lib/qt3 /usr/qt/3 /usr/lib/qt-3.3
>
> PATH: Path (not imported automatically from the shell)
> (colon-separated)
> default: None
> actual: None
>
> CXX: The c++ compiler
> default: g++
> actual: g++
>
> CXXFLAGS: Additional compiler flags for compilation (like
> -march=core2).
> default: None
> actual:
>
> march: Architecture to use with -march=... when optimizing
> default: native
> actual: native
>
> SHCCFLAGS: Additional compiler flags for linking (for plugins).
> default: None
> actual: -fPIC
>
> QUAD_PRECISION: typedef Real as long double (=quad) (yes|no)
> default: 0
> actual: False
>
> brief: Don't show commands being run, only what files are being
> compiled/linked/installed (yes|no)
> default: True
> actual: True
>
> useMiniWm3: use local miniWm3 library instead of Wm3Foundation (yes|
> no)
> default: 1
> actual: True
>
> phsieh@jupiter:~/dem/yade-trunk>
>
>
>
> On Wed, Mar 3, 2010 at 9:58 AM, Sergei D. <dorofeenko@xxxxxxxxx>
> wrote:
> 03.03.2010 16:44, Peiying Hsieh пишет:
>
> > Dear YADE group,
> > I saw some installation instruction of compiling YADE on
> > Ubuntu/fedora. I am using OpenSUSE 11.2 64 bit OS. Is there
> any
> > written installation instruction on compiling YADE on
> OpenSUSE 11.2 64
> > bit?
> > I have installed both openmpi and mpich2. Is there any place
> to tell
> > YADE which mpi version to use?
> > Pei-Ying
> >
>
>
> Hello. I use OpenSUSE 11.2 x86-64 too.
> I haven't instruction for installation, but here nothing
> special.
> I can answer to you questions if any.
>
> Best regards, Sergei D.
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-users
> Post to : yade-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-users
> More help : https://help.launchpad.net/ListHelp
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-users
> Post to : yade-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-users
> More help : https://help.launchpad.net/ListHelp
Follow ups
References
