1

Topic: Downgrade boost in Ubuntu

Something I was tangled in how correctly to address with versions  under Linux.) briefly, a situation such: it was necessary for me  the big another's project with set of dependences under Linux. There apt-get puts the version  1.55, the project demanded a minimum 1.57, I downloaded also hands  1.61 after that it appeared that the project we combine a maximum from 1.60, and here now I do not manage to install the version less than 1.61.) Now a situation such: in/usr/include lies installed apt-get'om boost 1.55, in/usr/local/include - boost 1.61, installed at the help./b2 install at the assembly boost 1.61 from source codes. If I launch now the assembly boost 1.60 with the same./b2 install changes nothing, in/usr/local/include there is version 1.61, probably, more low version does not fray higher. (That with it now to do? To delete hands? For this purpose it is enough to delete in include and lib? It would not be desirable to break absolutely this , I use it for the assembly of many projects, will long drag all.) thankful in advance for councils.)

2

Re: Downgrade boost in Ubuntu

Hello, jahr, you wrote: J> If I launch now the assembly boost 1.60 with the same./b2 install changes nothing, in/usr/local/include there is version 1.61, probably, more low version does not fray higher. (You confused something. At setting over any another  - correspond , but  are not deleted. One more will simply be added  and correspond . J> That with it now to do? To delete hands? For this purpose it is enough to delete in include and lib? It would not be desirable to break absolutely this , I use it for the assembly of many projects, will long drag all.) hands. Safely take down/usr/local/include/boost. Well and sudo rm-f/usr/local/lib/libboost_* and nothing  from  in/usr

3

Re: Downgrade boost in Ubuntu

Hello, niXman, you wrote: Thanks, are more clear now,  almost I do not know, so I feel uncertainly when it is necessary to correct something hands.) X> and nothing  from  in/usr And how it is correct? I them there not itself supposed, I collected  at myself in a house directory and in/usr they got as a result of performance target' install at the assembly (sudo./b2 install)

4

Re: Downgrade boost in Ubuntu

Hello, jahr, you wrote: J> And how it is correct? I them there not itself supposed, I collected  at myself in a house directory and in/usr they got as a result of performance target' install at the assembly (sudo./b2 install) you speak about/usr/local. By default, all collected by hands should use/usr/local as a prefix. (- prefix =/usr/local) I  about that it not wanted to you to use suddenly - prefix =/usr

5

Re: Downgrade boost in Ubuntu

Clearly, thanks.)

6

Re: Downgrade boost in Ubuntu

Hello, niXman, you wrote: X> by default, all collected by hands should use/usr/local as a prefix. (- prefix =/usr/local) By the way, install in/usr/local it is not convenient - then normally you will not delete ONE packet. For  this problem I use Stow - you install each packet in a separate folder then you launch stow which places  in/usr/local.

7

Re: Downgrade boost in Ubuntu

Hello, Evgeny. Panasyuk, you wrote: EP> By the way, install in/usr/local it is not convenient - then normally you will not delete ONE packet. For  this problem I use Stow - you install each packet in a separate folder then you launch stow which places  in/usr/local. Did not know that is such . Itself I do so: at setting of any packet (for example, ): touch $HOME/markers/before-boost-install.marker./b2 release && sudo./b2 install - prefix =/usr/local//all files which have been created after marker creation will be deleted: sudo find/usr/local-type f-newer $HOME/markers/before-boost-install.marker | xargs rm-rf>/dev/null 2>&1 i.e. if after  installed still any packets - they too will be deleted. Simply, conveniently. Well and Stow it will be, of course, more convenient. Thanks.

8

Re: Downgrade boost in Ubuntu

Hello, Evgeny. Panasyuk, you wrote: X>> by default, all collected by hands should use/usr/local as a prefix. (- prefix =/usr/local) EP> By the way, install in/usr/local it is not convenient - then normally you will not delete ONE packet. For  this problem I use Stow - you install each packet in a separate folder then you launch stow which places  in/usr/local. Or simply you install through checkinstall.

9

Re: Downgrade boost in Ubuntu

Hello, andrey.desman, you wrote: AD> Or simply you install through checkinstall. I so understand it was less general-purpose - how much I see there is no support Gentoo, BSD, OS X. For  thanks. But the title familiar, is possible I even tried, but I do not remember why did not get accustomed (can conflicts to similar packets from the core repo?), it will be necessary to try once again on CentOS.

10

Re: Downgrade boost in Ubuntu

Hello, Evgeny. Panasyuk, you wrote: EP> Hello, andrey.desman, you wrote: AD>> Or simply you install through checkinstall. EP> I so understand it was less general-purpose - how much I see there is no support Gentoo, BSD, X. because  support Gentoo, here is not necessary and is not present... In Gentoo and without this  any complexities with creation of "" "packets"... And "it is is less general-purpose" owing to that `./configure && make && make install DESTDIR = '... ' ` +  installed in  a format it is far not a high-grade packet (i.e. the most stupid variant of a packet) RPM or DEB..." Present  "can be able hardly more than simply to unpack archive in file system... But yes,""for those the clod should  make hastily something similar to a native packet. EP> for  thanks. But the title familiar, is possible I even tried, but I do not remember why did not get accustomed (can conflicts to similar packets from the core repo?), it will be necessary to try once again on CentOS.

11

Re: Downgrade boost in Ubuntu

Hello, zaufi, you wrote: AD>>> Or simply you install through checkinstall. EP>> I so understand it was less general-purpose - how much I see there is no support Gentoo, BSD, X. Z> because  support Gentoo, here is not necessary and is not present... In Gentoo and without this  any complexities with creation of "" "packets"... High-grade packets demand more efforts - dependences, USE-flags, to suppose ebuild in local overlay, etc. Z> and it is "is less general-purpose" owing to that `./configure && make && make install DESTDIR = '... ' ` +  installed in  a format it is far not a high-grade packet (i.e. the most stupid variant of a packet) RPM or DEB... "Present " can be able hardly more than simply to unpack archive in file system... But yes, "" for those the clod should  make hastily something similar to a native packet. I meant that "was less general-purpose" than Stow, instead of than "native present" a packet.