POV-Ray : Newsgroups : povray.unix : Compiling POVRay RC6 for the Stampede Cluster : Re: Compiling POVRay RC6 for the Stampede Cluster Server Time
30 Apr 2024 01:11:19 EDT (-0400)
  Re: Compiling POVRay RC6 for the Stampede Cluster  
From: clipka
Date: 10 Jan 2013 20:15:49
Message: <50ef67c5$1@news.povray.org>
Am 11.01.2013 00:53, schrieb waggy:

> Configure recognizes that I am attempting to cross-compile when I add the -mmic
> flag.
>
> export CFLAGS="-O3 -mmic"
> export CXXFLAGS="${CFLAGS}"
>
> .../configure COMPILED_BY="My Name <abc### [at] myutsaedu>" \
> --host=x86_64-unknown-linux-gnu \
> --prefix=$HOME/mic/bin \
> --with-boost=$TACC_BOOST_DIR \
> --without-libjpeg \
> --without-libtiff \
> --enable-static
>
> But configure aborts with this.
>
> checking for boostlib >= 1.37... yes
> checking whether the Boost::Thread library is available... yes
> checking for exit in -lboost_thread... no
> checking for exit in -lboost_thread... (cached) no
> checking for exit in -lboost_thread... (cached) no
> configure: error: Could not link against boost_thread !

Cross-compiling POV-Ray might be tricky: To my knowledge, the 
./configure script tries to compile, link /and/ run various short test 
programs with the chosen settings to see whether everything works as 
expected, and/or to auto-detect which settings it needs to use. 
Obviously, if those test programs are cross-compiled for a different 
target they won't run on the machine you're compiling on, and 
./configure will think something went wrong, and/or will be unable to 
auto-detect certain settings. Maybe this is what's happening to you there.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.