public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <fischerm42@t-online.de>
To: development@lists.ipfire.org
Subject: Re: boost 1_58_0 - rootfile
Date: Mon, 18 May 2015 20:16:49 +0200	[thread overview]
Message-ID: <555A2C91.5080104@t-online.de> (raw)
In-Reply-To: <1431942415.16602.6.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

On 18.05.2015 11:46, Michael Tremer wrote:
> Hi,
>
> On Sat, 2015-05-16 at 13:59 +0200, Matthias Fischer wrote:
>> Hi,
>>
>> is there a specific reason for commenting the line
>>
>> ...
>> #usr/lib/libboost_math_c99l.so.1.55.0
>> ...
>>
>> in rootfile for 'boost 1_55_0'?
>
> No. I must have overlooked that when I created that file.
>
>> All other '/usr/lib/libboost*'-files are uncommented, only this one is
>> ~deactivated.
>>
>> This came to me while building an update to 'boost 1_58_0'.
>
> Updating boost requires to ship everything that is linked against it
> again and you will need to have something that removes the old
> libraries.

This is seems to be more complex than I thought. How do I find which 
parts of IPFire are "linked against boost"? I can run 'ldd' against a 
binary to find which libraries it needs, but how to work the other way 
around?

> An other strategy would be to leave the old libraries there and just
> ship the new ones. Every time when something that uses boost is updated,
> it will switch from using the old libraries to the new ones.

If I get you right then in this case old and new libs are left in 
'/usr/lib'. Sounds more like some kind of 'patchwork', IMHO.

Regards
Matthias


  reply	other threads:[~2015-05-18 18:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-16 11:59 Matthias Fischer
2015-05-18  9:46 ` Michael Tremer
2015-05-18 18:16   ` Matthias Fischer [this message]
2015-05-19  9:19     ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=555A2C91.5080104@t-online.de \
    --to=fischerm42@t-online.de \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox