Oh, sorry, I post a wrong patch:-(
I'll post the right one next day.

在 2012年3月30日 下午11:32,Zhihua Che <[email protected]> 写道:
> Hi, Pervez
> Thanks for your patience. I guess I find a solution:-)
>
> Previously, I added LDFLAGS=-L<build-dir>/src/.libs, not <src-dir>/src/.libs.
> .libs is generated during building, it's where built libraries are outputed.
>
> The following is my solution. Wish It would help others.
>
> I apply the attchment patch and export LDFLAGS=-L<build-dir>/src/.libs.
> This patch solve the link problem which complains "cannot find
> libboost_program_options etc.
> export LDFLAGS solve the "make install" problem.
>
> The patch is originated from Cajus Pollmeier. Thanks for his work.
> And this one is applicable to qpid higher than 0.14
>
> 在 2012年3月30日 下午10:25,Pervez, Salman <[email protected]> 写道:
>> Hi Zhihua, can you please post your build commands including configure and 
>> make? I am curious how you chose to build this and it might help solve the 
>> problem.
>>
>> When you say LDFLAGS=-L<build-dir>/src/.libs to "make install", do you 
>> really mean LDFLAGS=-L<source-dir>/src/.libs to "make install"? There is no 
>> .libs dir in my build directory that I could find. Perhaps linking with the 
>> actual build dir might help, I'm not sure.
>>
>> But ideally make install should just find stuff. So maybe the problem is 
>> with something you might have done earlier?
>>
>> Salman
>>
>> -----Original Message-----
>> From: Zhihua Che [mailto:[email protected]]
>> Sent: Friday, March 30, 2012 3:41 AM
>> To: [email protected]
>> Subject: Re: [Building Error] cannot find 
>> boost_program_option/boost_filesystem
>>
>> Thanks for your reply.
>>
>> I guess I've solved this problem and I also meet that typical link
>> problem and address it using that fix-explicit-link-problem.patch:-)
>> and finally make succeeded.
>>
>> But I'm struggling with "make install":-)
>> which complains can't find -lqpidbroker. I'm sure qpidbroker is built
>> and stored in src/.libs, and it still fails even if I add
>> LDFLAGS=-L<build-dir>/src/.libs to "make install" command line.
>>
>> this is what I get.
>>
>> /usr/bin/ld: cannot find -lqpidbroker
>> collect2: ld returned 1 exit status
>> libtool: install: error: relink `ha.la' with the above command before
>> installing it
>>
>>
>>
>>
>> 在 2012年3月29日 下午10:13,Pervez, Salman <[email protected]> 写道:
>>> What specific error do you get?
>>>
>>> You can try adding <path-to-boost-lib-dir> to your LDFLAGS.
>>>
>>> LDFLAGS="-L<path>" ...
>>>
>>> You can also try adding the flags -lboost_system and -lboost_filesystem to 
>>> your CXXFLAGS.
>>>
>>> It will work eventually. :)
>>>
>>> Salman
>>>
>>> -----Original Message-----
>>> From: Zhihua Che [mailto:[email protected]]
>>> Sent: Thursday, March 29, 2012 2:23 AM
>>> To: [email protected]
>>> Subject: [Building Error] cannot find boost_program_option/boost_filesystem
>>>
>>> Hi, everyone
>>>
>>>    I'm building qpid from  git code repository and version is
>>> 5c5088749ba26b1d3d6fb8132c14d3be0b20b959. I built it using automake
>>> and configure succeeded in creating Makefile. I guess the compiling is
>>> ok, but linking failed due to lack of libraries boost_program_option
>>> and boost_filesystem. I've installed libboost-dev, but I cannot find
>>> the two libraries in my system. I've searched a lot and have no clue
>>> how to get this around.
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>>
>>>
>>> CONFIDENTIALITY AND SECURITY NOTICE
>>>
>>> The contents of this message and any attachments may be confidential and 
>>> proprietary and also may be covered by the Electronic Communications 
>>> Privacy Act. This message is not intended to be used by, and should not be 
>>> relied upon in any way, by any third party.  If you are not an intended 
>>> recipient, please inform the sender of the transmission error and delete 
>>> this message immediately without reading, disseminating, distributing or 
>>> copying the contents. Citadel makes no assurances that this e-mail and any 
>>> attachments are free of viruses and other harmful code.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to