Tiny Core Linux

Tiny Core Extensions => TCE Talk => Topic started by: batnas on May 30, 2010, 08:08:44 AM

Title: compiling using boost - link problem
Post by: batnas on May 30, 2010, 08:08:44 AM

Hi all

Im trying to compila a program, but got a error;

Code: [Select]

checking for boostlib >= 1.34.1... yes
checking whether the Boost::Signals library is available... yes
configure: error: Could not link against   !

I have installed boost-dev.tcz

Does anyone have any idea how to fix this?

EDIT:
looking in the configure.log tells me:

Code: [Select]

onfigure:10163: checking for boostlib >= 1.34.1
configure:10227: g++ -c -g -O2  -DBUILT_BY_root -I/usr/local/include conftest.cpp >&5
configure:10233: $? = 0
configure:10239: result: yes
configure:10442: checking whether the Boost::Signals library is available
configure:10477: g++ -c -g -O2  -DBUILT_BY_root -I/usr/local/include conftest.cpp >&5
configure:10483: $? = 0
configure:10505: result: yes
configure:10731: error: Could not link against  !
Batnas

Title: Re: compiling using boost - link problem
Post by: batnas on May 30, 2010, 09:53:30 AM

Found this forum:
http://code.google.com/p/vmware-view-open-client/issues/detail?id=51 (http://code.google.com/p/vmware-view-open-client/issues/detail?id=51)

But every directory i have tried fails

\\Batnas

Title: Re: compiling using boost - link problem
Post by: curaga on May 30, 2010, 10:14:14 AM

Did you know of vmware-view.tcz?

Title: Re: compiling using boost - link problem
Post by: batnas on May 30, 2010, 10:34:10 AM

Aaargh. Doh. Please shoot me.  ;)

No. That is exactly what i was trying to compile. Thanks a lot.

I really have to remember to check appbrowser first..

\\Batnas

Title: Re: compiling using boost - link problem
Post by: peterc on June 14, 2010, 03:03:33 PM

For future reference, I had a similar problem; it was asking for Boost::Serialization and Boost::Filesystem. I solved it by passing --with-boost-serialization=boost_serialization and --with-boost-filesystem=boost_filesystem to ./configure. So perhaps --with-boost-signals=boost_signals would have worked for you. (I see that there's also a boost_signals2 available as well, but I have no idea what is what...)