[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnash] Gnash-0.8.1 configure error : boost libraries
From: |
fruity |
Subject: |
Re: [Gnash] Gnash-0.8.1 configure error : boost libraries |
Date: |
Fri, 04 Jan 2008 12:47:17 +0100 |
User-agent: |
Icedove 1.5.0.14pre (X11/20071018) |
fruity wrote:
> Rob Savoye wrote:
>
>> strk wrote:
>>
>>
>>
>>>> *checking for the Boost Version... 1_34_1
>>>> checking for Boost libraries... -lboost_date_time-gcc33-mt
>>>> -lboost_thread-gcc33-mt
>>>> checking boost/thread.hpp usability... no
>>>> checking boost/thread.hpp presence... no
>>>> checking for boost/thread.hpp... no*
>>>>
>>>>
>> It does appear to have found your installation.
>>
>>
>>
>>> Benoit Sigoure gave us this link:
>>> http://repo.or.cz/w/boost.m4.git
>>>
>>>
>> We don't use that one. We have our own boost macro that support cross
>> compiling, unlike the other one.
>>
>>
>>
>>>> I have libraries *libboost_date_time-gcc33-mt.so, libboost_thread-gcc33-mt
>>>> libraries.so in /usr/local/include/* but still it is not able to pickup
>>>> those i think.
>>>>
>>>>
>> If you get the name like "-lboost_date_time-gcc33-mt", it was found. It
>> looks more like some error. The easiest way to debug configure problems
>> is to set CONFIG_SHELL to "sh -x" in your environment, and then run
>> configure like "$CONFIG_SHELL ./configure.... blah". This will turn on
>> all the debugging output, and then one of us can look at it and see what
>> happened. At that point fixing it is easy.
>>
>> I have boost 34 build from source, and I also work on a Fedora 7
>> machine, and it all works fine for me. If you do the above, we can
>> figure out what the issue is.
>>
>> btw, is this is a stock 0.8.1 release ? If so, I'd try cvs, as our
>> boost macro has changed heavily since the last release.
>>
>> - rob -
>>
>>
>>
Sorry rob i sented you this mail by mistake
Did you solve the problem?
did you as rob told you?
CONFIG_SHELL="sh -x" ./configure.... blah
whats the output?
don't paste it all in a mail, better in an attachment.
just to know if is all about the m4 macro
bye