Debian Jessie update

GNU Radio
1

Hi,

I am not able to run GRC after updating my Debian Jessie. (apt-get
update,
apt-get dist-upgrade, apt-get autoremove)
I am using Debian jessie. Before this GRC run well.

user1@pc1: ~ $ gnuradio-config-info -v
gnuradio-config-info: error while loading shared libraries:
libboost_program_options.so.1.54.0: cannot open shared object file: No
such
file or directory

~ $ uname -a
Linux rsLAPTOP 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64
GNU/Linux

~ $ gcc --version
gcc (Debian 4.8.2-21) 4.8.2
Copyright © 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

Probably the latest libboost doesn’t work very well with gnuradio
v3.7.3.
How to solve this? How to fall back?

2

I guess you will have to re-build everything regarding gnuradio. I did
this yesterday due to an update from libboost 1.53 to 1.54.

Ralph.

From: discuss-gnuradio-bounces+ralph=removed_email_address@domain.invalid
[mailto:discuss-gnuradio-bounces+ralph=removed_email_address@domain.invalid] On Behalf Of
Activecat
Sent: Wednesday, May 28, 2014 5:32 AM
To: [email protected]
Subject: [Discuss-gnuradio] Debian Jessie update

Hi,

I am not able to run GRC after updating my Debian Jessie. (apt-get
update, apt-get dist-upgrade, apt-get autoremove)

I am using Debian jessie. Before this GRC run well.

user1@pc1: ~ $ gnuradio-config-info -v
gnuradio-config-info: error while loading shared libraries:
libboost_program_options.so.1.54.0: cannot open shared object file: No
such file or directory

~ $ uname -a
Linux rsLAPTOP 3.14-1-amd64 #1 SMP Debian 3.14.4-1 (2014-05-13) x86_64
GNU/Linux

~ $ gcc --version
gcc (Debian 4.8.2-21) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There
is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

Probably the latest libboost doesn’t work very well with gnuradio
v3.7.3.

How to solve this? How to fall back?

3

On Wed, May 28, 2014 at 2:22 PM, Ralph A. Schmid, dk5ras
[email protected]wrote:

I guess you will have to re-build everything regarding gnuradio. I did
this yesterday due to an update from libboost 1.53 to 1.54.

Ralph.

Yes, re-installation solves the problem.
Thanks.

4

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

To explain: Binaries are generally linked against binaries, ie.
against a certain set of symbols only present in a certain build of a
binary; thus, usually libraries link against specific versionized
libraries.

If you update a library, binaries linked against the old version are
bound to stop working. In most unixoid systems, this is circumvented
(sometimes) by having the ability to have multiple libraries in
different versions installed [1](libgrandmascheesecake.so.1.0.0,
libgrandmascheesecake.so.1.1.2) and a symlink from the general name to
the recent one (libgrandmascheesecake.so →
libgrandmascheesecake.so.1.1.2). However, usually you don’t want to
have conflicting versions, so package management usually goes miles to
ensure that all packages in a certain distribution version are built
against the same library version.

Greetings,
Marcus

[1] windows-y systems usually ship all the libraries in the same
directory as the executable, which is --from a storage point of view–
quite like static linking.
On 28.05.2014 11:09, Activecat wrote:

Yes, re-installation solves the problem. Thanks.

_______________________________________________ Discuss-gnuradio
mailing list [email protected]
Discuss-gnuradio Info Page

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTham2AAoJEBQ6EdjyzlHtDcwIAItAbigJQVIVc/FKgaFIUCM/
dm8LoLnZOFAov5ssERAdcRIkWD1eu9lzEkZ3pjo7UEUZGepvAWgw6BuSGDilg38K
PlCkVH9pdbwTj6Uvhj+ZXDf4i+NM9E5ZVyIxrrl9kM9C1aj+bxFEX4g4oq5ey0Hc
Q5/Joct7e0/UJ93UobBdeooQdiy40pZ14KH3xsWTJtXRQ3PDv8cskbvckr+ba6lb
dJI8I+tRhAIF6EBtkfJB3hSyt9qzIW1YTi9Sb3cC2XjO+50s0f/60/ZNwKjQ1q+m
Zan/5nJ3ikOrmOcsHLmjpekjrzCgFhyzipmFC8i1XKYfDSBd4GlHw/wg9su/IUY=
=pGQ/
-----END PGP SIGNATURE-----

5

On Wed, May 28, 2014 at 5:17 PM, Marcus Müller [email protected]
wrote:

(sometimes) by having the ability to have multiple libraries in

[1] windows-y systems usually ship all the libraries in the same
directory as the executable, which is --from a storage point of view–
quite like static linking.

Thank you very much.