Re: [boost] bjam stage forgot symlinks FIX BEFORE RELEASE

From: Neal Becker (ndbecker2_at_[hidden])
Date: 2005-07-29 10:59:24

Rene Rivera wrote:

> Neal Becker wrote:
>> I just built from a recent cvs using:
>> ICU_PATH=/usr ICU_LINK="-licuuc -licui18n" PYTHON_ROOT=/usr
>> PYTHON_VERSION=2.3 bjam -sTOOLS=gcc stage
>> 
>> I noticed that symlinks are missing.  for each lib "x", in stage/lib
>> there is
>> 
>> libx.so.1.0.0 (actual binary)
>> libx.so -> libx.so.1.0.0 (link)
>> 
>> but there must be also
>> libx.so.1 -> libx.so.1.0.0
>> 
>> This is because (I guess) soname of the library is set to libx.so.1, and
>> when you link to libx then at runtime it will look for libx.so.1 (which
>> it won't find)
> 
> With GCC, we set the soname to "libx-1_33.so.1.33.0". So I don't see why
> we need the symlink you mention.
> 
> 

Sorry, my mistake.  My version had been patched to do this.