Re: [Discuss-gnuradio] Multiple Versions of Libraries / Virtualenv (was: Re: PYBOMBs Testing)

[Dan CaJacob]

Thanks, Marcus.  It seemed too good to be true ;)

Very Respectfully,

Dan CaJacob

On Fri, Jan 10, 2014 at 1:20 PM, Marcus Müller <address@hidden> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Dan,

no, Virtualenv is "virtualenv is a tool to create isolated Python
environments." only.

For unix systems, having multiple versions of the same library is not
a problem by itself, especially since there are several environment
variables that control the behaviour of the dynamic run time linker.

A nice method to employ this is described in
http://gnuradio.org/redmine/projects/gnuradio/wiki/FAQ#Experts-only-How-can-I-deliberately-install-GNU-Radio-multiple-times-different-versions
; just install your application specific libraries, headers etc into
~/.usrlocal.

Also, if you need to capsulate your system more thoroughly, consider
using chroot; although this has become less popular over the last few
years due to the fact that virtualization has become so easy.

Hope that was a little insightful. If someone comes up with something
interesting on this topic, a new thread should be started; although I
consider this problem to be of a typical linux distribution concern,
and not very much specific to GR.

Greetings,
Marcus

On 10.01.2014 16:45, Dan CaJacob wrote:
> Thanks, Tom!
>
> Digression warning: While we're on the topic, I've always wondered
> if virtualenv would help with build dependency problems and
> multiple installed versions (e.g. for devs).  I have never immersed
> myself into the tool, but I know that it is intended for things
> like this where you want to install specific package versions for a
> specific application without affecting other things on your system.
> It's a sandbox, I guess.  What I've never been clear on is whether
> it works for C/C++ applications, since it seems to be a python
> tool.  Do you have any thoughts on that?
>
> Very Respectfully,
>
> Dan CaJacob
>
>
> On Fri, Jan 10, 2014 at 10:14 AM, Tom Rondeau <address@hidden>
> wrote:
>
>> On Thu, Jan 9, 2014 at 12:09 PM, Dan CaJacob
>> <address@hidden> wrote:
>>> Hey Tom,
>>>
>>> Thanks.  I didn't know how or what to search for, so that was
>>> useful. Here's the result:
>>>
>>>> i   libzeroc-ice34                             - Ice for C++
>>>> runtime library
>>
>> That there confirms that the Ice 3.4.2 library is installed on
>> your system, which is what I was expecting.
>>
>>
>>> Here's what I found in the gnuradio CMakeCache.txt file:
>>>
>>>> ICE_CONFIG_INCLUDE_DIR:PATH=/usr/include //Path to a
>>>> library. ICE_GLACIER2:FILEPATH=/usr/lib/libGlacier2.so //Path
>>>> to a library. ICE_ICE:FILEPATH=/usr/lib/libIce.so //Path to a
>>>> library. ICE_ICEGRID:FILEPATH=/usr/lib/libIceGrid.so //Path
>>>> to a library. ICE_ICESTORM:FILEPATH=/usr/lib/libIceStorm.so
>>>> //Path to a library.
>>>> ICE_ICEUTIL:FILEPATH=/usr/lib/libIceUtil.so //Path to a
>>>> file. ICE_INCLUDE_DIR:PATH=/usr/include //Path to a library.
>>>> ICE_PTHREAD:FILEPATH=/usr/lib/x86_64-linux-gnu/libpthread.so
>>>> //Path to a program.
>>>> ICE_SLICE2CPP:FILEPATH=/usr/bin/slice2cpp //Path to a
>>>> program. ICE_SLICE2PY:FILEPATH=/usr/bin/slice2py //Details
>>>> about finding ICE
>>>>
>>>>
>> FIND_PACKAGE_MESSAGE_DETAILS_ICE:INTERNAL=[/usr/lib/libIce.so;/usr/lib/libIceUtil.so][/usr/include][v()]
>>
>>>
>>
Very Respectfully,
>>>
>>> Dan CaJacob
>>
>>
>> And that tells us that GNU Radio is trying to build using the Ice
>> libs in /usr/lib, which is where apt-get would have installed
>> ICE, so yeah, it's trying to build off Ice 3.4.2.
>>
>> You could solve this pretty easily by doing an "aptitude remove
>> libzeroc-ice" to get rid of Ice 3.4.2 altogether on your system.
>> But I'm more interested in solving this issue in general.
>>
>> I've brought up a VM that has this behavior. Let me see about
>> working out a solution.
>>
>> Tom
>>
>
>
>
> _______________________________________________ Discuss-gnuradio
> mailing list address@hidden
> https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJS0Dn7AAoJEAFxB7BbsDrLEOwH/RTC+kW1/vgQ6NQxaoTDYFTv
vxz9B5PbOxocH9/dnINdqtctJw63f/gfIqwUzZK2uuZOJKR1HYbbeIm6diheOexU
B+KVgGDyMbcCIw2Xioo+B/Gr8b7sQPZjOnJNztg1Se1wpOLPtCcwP6fTv9j6xZog
olcyQ1cxezRikja/DX/E52DxJ/fVgDawMoR+KoMQOQ4SvL98KiTuD/X6vRuc2TOz
xt81GwAs6LJh8HVr+kMBXFq1UaN3WxrMPHXtg/db0uxWZXgvKoQYLv6fpCMb+9BZ
eAXgzDkh1SXyaB9K6G6Q6qTO95el6W/VRDgbRyUC8SvP4IN72i4R+jhG6cwwCKg=
=M0JC
-----END PGP SIGNATURE-----

_______________________________________________
Discuss-gnuradio mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/discuss-gnuradio