How to upgrade the GLIBCXX and GLIBC to the specific version

[Greg Wooledge]

Hi,
Would you pls help give tips about how to upgrade the GLIBCXX and GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian?
I am using the Raspberry Pi 4B with the Raspbian OS “Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux”, which is Debian based OS.
When running a SW I met the problem missing the required versions of GLIBCXX and GLIBC, with the details below.
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./blueriver_bitmap_streamer)

Your libc6 and libstdc++6 packages are too old to run this program.
Your choices are:

1) Find another, older, build of this program that's suitable for your
system.

2) Recompile it yourself, if source code is available.

3) Find a substitute program.

4) Upgrade your operating system to a newer release.

Debian 12 (bookworm) should be new enough:

hobbit:~$ nm -D /lib/x86_64-linux-gnu/libc.so.6 | grep 'A GLIBC_2\.3[0-9]'
0000000000000000 A GLIBC_2.30
0000000000000000 A GLIBC_2.31
0000000000000000 A GLIBC_2.32
0000000000000000 A GLIBC_2.33
0000000000000000 A GLIBC_2.34
0000000000000000 A GLIBC_2.35
0000000000000000 A GLIBC_2.36

hobbit:~$ nm -D /lib/x86_64-linux-gnu/libstdc++.so.6 | grep 'A GLIBCXX_3\.4\.[23][0-9]'
0000000000000000 A GLIBCXX_3.4.20
0000000000000000 A GLIBCXX_3.4.21
0000000000000000 A GLIBCXX_3.4.22
0000000000000000 A GLIBCXX_3.4.23
0000000000000000 A GLIBCXX_3.4.24
0000000000000000 A GLIBCXX_3.4.25
0000000000000000 A GLIBCXX_3.4.26
0000000000000000 A GLIBCXX_3.4.27
0000000000000000 A GLIBCXX_3.4.28
0000000000000000 A GLIBCXX_3.4.29
0000000000000000 A GLIBCXX_3.4.30

[Arno Lehmann]

Hi all,

Hi,
Would you pls help give tips about how to upgrade the GLIBCXX and GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian?
I am using the Raspberry Pi 4B with the Raspbian OS “Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux”, which is Debian based OS.

That's a problem -- it is not Debian.

Expecting insight here is a bit of a stretch. It would be much better to
check with the actual distribution provider.

Greg's advice about upgrading is demonstrating the versions for the
x86_64 platform. This may or may not be directly applicable to your
distribution. However, trying to upgrade something non-Debian with
Debian packages may be exciting and provide great learning experience,
but rarely is a smooth process.

I would propose to head over to https://www.raspberrypi.com/software/ if
you do not get very clear advice here.

Also, the actual software you want to use should be considered. If it's
not packaged for your distribution, it's at least clear the packager
does not guarantee anything. Rebuilding for your platform requires
access to source code and (possibly) build environment. Suggestions or
advice require you to disclose what you're actually looking at.

Good luck!

Arno

[Gremlin]

Post by Arno Lehmann
Hi all,

Hi,
Would you pls help give tips about how to upgrade the GLIBCXX and
GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian?
I am using the Raspberry Pi 4B with the Raspbian OS “Linux
raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST
2022 aarch64 GNU/Linux”, which is Debian based OS.

That's a problem -- it is not Debian.

The new version for Rpi is and would not matter in his case as he is
looking to update glibc. That isn't platform pacific and doesn't matter.

Rpi 5:

uname -a
Linux scott 6.1.0-rpi8-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1
(2024-01-25) aarch64 GNU/Linux

cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Post by Arno Lehmann
Expecting insight here is a bit of a stretch. It would be much better to
check with the actual distribution provider.

The provider is raspberry foundation and Raspian has been dis-continued.

Post by Arno Lehmann
Greg's advice about upgrading is demonstrating the versions for the
x86_64 platform. This may or may not be directly applicable to your
distribution. However, trying to upgrade something non-Debian with
Debian packages may be exciting and provide great learning experience,
but rarely is a smooth process.

sudo find /usr/lib -name '*libc.so*'
/usr/lib/aarch64-linux-gnu/libc.so.6
/usr/lib/aarch64-linux-gnu/libc.so

nm -D /usr/lib/aarch64-linux-gnu/libc.so.6 | grep 'A GLIBC_2\.3[0-9]'
0000000000000000 A GLIBC_2.30
0000000000000000 A GLIBC_2.31
0000000000000000 A GLIBC_2.32
0000000000000000 A GLIBC_2.33
0000000000000000 A GLIBC_2.34
0000000000000000 A GLIBC_2.35
0000000000000000 A GLIBC_2.36

sudo find /usr/lib -name '*libstdc++.so*'
/usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.30
/usr/lib/aarch64-linux-gnu/libstdc++.so.6
/usr/lib/gcc/aarch64-linux-gnu/12/libstdc++.so


nm -D /usr/lib/aarch64-linux-gnu/libstdc++.so.6.0.30 | grep 'A
GLIBCXX_3\.4\.[23][0-9]'
0000000000000000 A GLIBCXX_3.4.20
0000000000000000 A GLIBCXX_3.4.21
0000000000000000 A GLIBCXX_3.4.22
0000000000000000 A GLIBCXX_3.4.23
0000000000000000 A GLIBCXX_3.4.24
0000000000000000 A GLIBCXX_3.4.25
0000000000000000 A GLIBCXX_3.4.26
0000000000000000 A GLIBCXX_3.4.27
0000000000000000 A GLIBCXX_3.4.28
0000000000000000 A GLIBCXX_3.4.29
0000000000000000 A GLIBCXX_3.4.30

Post by Arno Lehmann
I would propose to head over to https://www.raspberrypi.com/software/ if
you do not get very clear advice here.
Also, the actual software you want to use should be considered. If it's
not packaged for your distribution, it's at least clear the packager
does not guarantee anything. Rebuilding for your platform requires
access to source code and (possibly) build environment. Suggestions or
advice require you to disclose what you're actually looking at.
Good luck!
Arno

The correct solution is to download the latest and install that.
That is simple as rpi has an imager program that will d/l and install
the image to the sdcard or USB drive.

Updating glibc can be difficult and may cause more breakage.
You should take that project lightly.

He is most likely using armv7 and that comes with its own issues, ie cpu
type and floating point (hard/soft, neon and simd). aarch64 much easier
to build on.

Building custom OS for rpi since the rpi 1. Will be building a custom
OS for my rpi 4/5 servers and abandoning debian shortly, Desktop to follow.

[Greg Wooledge]

Post by Gremlin

I am using the Raspberry Pi 4B with the Raspbian OS “Linux
raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44
BST 2022 aarch64 GNU/Linux”, which is Debian based OS.

He is most likely using armv7 and that comes with its own issues, ie cpu
type and floating point (hard/soft, neon and simd). aarch64 much easier to
build on.

It looks like he's using aarch64.

[Gremlin]

Post by Greg Wooledge

Post by Gremlin

I am using the Raspberry Pi 4B with the Raspbian OS “Linux
raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44
BST 2022 aarch64 GNU/Linux”, which is Debian based OS.

He is most likely using armv7 and that comes with its own issues, ie cpu
type and floating point (hard/soft, neon and simd). aarch64 much easier to
build on.

It looks like he's using aarch64.

You can not tell from that as he could be using a armv7 system and run a
aarch64 kernel, The foundation always run the 64 bit kernel on the 32
bit system. The 32 bit installation script sets the flag in the
config.txt file to run a 64 bit kernel on the 32 bit system on the rpi4.

From /boot/config.txt

# Run in 64-bit mode
arm_64bit=1

[Stefan Monnier]

Post by Gremlin
He is most likely using armv7 and that comes with its own issues, ie
cpu type and floating point (hard/soft, neon and simd). aarch64 much
easier to build on.

I'm using Debian armhf here on various machines (most of them with ARMv7
CPUs but some one of them with an ARMv8 CPU (and kernel)).
I haven't encountered any particular problem (both in terms of using and
installing Debian and in terms of "manually" building software from
source) that seems related to ARMv7 vs ARMv8.


Stefan

[Gremlin]

Post by Stefan Monnier

Post by Gremlin
He is most likely using armv7 and that comes with its own issues, ie
cpu type and floating point (hard/soft, neon and simd). aarch64 much
easier to build on.

I'm using Debian armhf here on various machines (most of them with ARMv7
CPUs but some one of them with an ARMv8 CPU (and kernel)).
I haven't encountered any particular problem (both in terms of using and
installing Debian and in terms of "manually" building software from
source) that seems related to ARMv7 vs ARMv8.
Stefan

Building binaries when you have a 32-bit system and using a 64-bit
kernel will never work.

Ask me how I know.

[Stefan Monnier]

Building binaries when you have a 32-bit system and using a 64-bit kernel
will never work.

And yet I do it every day,


Stefan

[Gremlin]

Post by Stefan Monnier

Building binaries when you have a 32-bit system and using a 64-bit kernel
will never work.

And yet I do it every day,
Stefan

Build the GNU tool chain and you will get an education.
You would have to have a multilib system and then you will still have
issues.

Try building an entire OS from scratch and you will get another education.

[Gremlin]

Post by Stefan Monnier

Post by Gremlin
He is most likely using armv7 and that comes with its own issues, ie
cpu type and floating point (hard/soft, neon and simd). aarch64 much
easier to build on.

I'm using Debian armhf here on various machines (most of them with ARMv7
CPUs but some one of them with an ARMv8 CPU (and kernel)).
I haven't encountered any particular problem (both in terms of using and
installing Debian and in terms of "manually" building software from
source) that seems related to ARMv7 vs ARMv8.
Stefan

The following options are target specific:
-mabi= lp64
-march= armv8.2-a+crypto+fp16+rcpc+dotprod
-mbig-endian [disabled]
-mbionic [disabled]
-mbranch-protection=
-mcmodel= small
-mcpu= generic
-mfix-cortex-a53-835769 [enabled]
-mfix-cortex-a53-843419 [enabled]
-mgeneral-regs-only [disabled]
-mglibc [enabled]
-mharden-sls=
-mlittle-endian [enabled]
-mlow-precision-div [disabled]
-mlow-precision-recip-sqrt [disabled]
-mlow-precision-sqrt [disabled]
-mmusl [disabled]
-momit-leaf-frame-pointer [enabled]
-moutline-atomics [enabled]
-moverride=<string>
-mpc-relative-literal-loads [enabled]
-msign-return-address= none
-mstack-protector-guard-offset=
-mstack-protector-guard-reg=
-mstack-protector-guard= global
-mstrict-align [disabled]
-msve-vector-bits=<number> scalable
-mtls-dialect= desc
-mtls-size= 24
-mtrack-speculation [disabled]
-mtune= generic
-muclibc [disabled]
-mverbose-cost-dump [disabled]

Known AArch64 ABIs (for use with the -mabi= option):
ilp32 lp64

Supported AArch64 return address signing scope (for use with
-msign-return-address= option):
all non-leaf none

The code model option names for -mcmodel:
large small tiny

Valid arguments to -mstack-protector-guard=:
global sysreg

The possible SVE vector lengths:
1024 128 2048 256 512 scalable

The possible TLS dialects:
desc trad

[d***@howorth.org.uk]

Post by Gremlin
The provider is raspberry foundation and Raspian has been
dis-continued.

There is such a thing as the Raspberry Pi Foundation but they are an
educational charity. Pis are supplied by Raspberry Pi Ltd. Raspbian has
NOT been discontinued, it has simply been renamed Raspberry Pi OS. I
don't know who releases it, though it is released from teh Ltd company
website rather than the Foundation. Perhaps somebody else knows more
detail.

[Gremlin]

Post by d***@howorth.org.uk

Post by Gremlin
The provider is raspberry foundation and Raspian has been
dis-continued.

There is such a thing as the Raspberry Pi Foundation but they are an
educational charity. Pis are supplied by Raspberry Pi Ltd. Raspbian has
NOT been discontinued, it has simply been renamed Raspberry Pi OS. I
don't know who releases it, though it is released from teh Ltd company
website rather than the Foundation. Perhaps somebody else knows more
detail.

Nope that is just wrong.


https://www.raspbian.org/


Welcome to Raspbian

Raspbian is a free operating system based on Debian optimized for the
Raspberry Pi hardware. An operating system is the set of basic programs
and utilities that make your Raspberry Pi run. However, Raspbian
provides more than a pure OS: it comes with over 35,000 packages,
pre-compiled software bundled in a nice format for easy installation on
your Raspberry Pi.

The initial build of over 35,000 Raspbian packages, optimized for best
performance on the Raspberry Pi, was completed in June of 2012. However,
Raspbian is still under active development with an emphasis on improving
the stability and performance of as many Debian packages as possible.

Note: Raspbian is not affiliated with the Raspberry Pi Foundation.
Raspbian was created by a small, dedicated team of developers that are
fans of the Raspberry Pi hardware, the educational goals of the
Raspberry Pi Foundation and, of course, the Debian Project.


Why are you trying to tell someone that has used raspberry pi since the
original pi came out things that are just not true.

I also build custom OS for the raspberry pi platform and I am well
versed with them. I have approx a dozen of them from rpi to rpi 5

I have used them for servers on the network including the original pi.

Yes I am aware of theis in the foundation page:

Your Raspberry Pi needs an operating system to work. This is it.
Raspberry Pi OS (previously called Raspbian) is our official supported
operating system.

The new OS called Raspberry Pi OS is a new animal. The foundation used
raspian and the the Raspberry Pi OS is the foundations, developed by the
foundation.

[gene heskett]

Post by Gremlin

Post by d***@howorth.org.uk

Post by Gremlin
The provider is raspberry foundation and Raspian has been
dis-continued.

There is such a thing as the Raspberry Pi Foundation but they are an
educational charity. Pis are supplied by Raspberry Pi Ltd. Raspbian has
NOT been discontinued, it has simply been renamed Raspberry Pi OS. I
don't know who releases it, though it is released from teh Ltd company
website rather than the Foundation. Perhaps somebody else knows more
detail.

Nope that is just wrong.
https://www.raspbian.org/
Welcome to Raspbian
Raspbian is a free operating system based on Debian optimized for the
Raspberry Pi hardware. An operating system is the set of basic programs
and utilities that make your Raspberry Pi run. However, Raspbian
provides more than a pure OS: it comes with over 35,000 packages,
pre-compiled software bundled in a nice format for easy installation on
your Raspberry Pi.
The initial build of over 35,000 Raspbian packages, optimized for best
performance on the Raspberry Pi, was completed in June of 2012. However,
Raspbian is still under active development with an emphasis on improving
the stability and performance of as many Debian packages as possible.
Note: Raspbian is not affiliated with the Raspberry Pi Foundation.
Raspbian was created by a small, dedicated team of developers that are
fans of the Raspberry Pi hardware, the educational goals of the
Raspberry Pi Foundation and, of course, the Debian Project.
Why are you trying to tell someone that has used raspberry pi since the
original pi came out things that are just not true.
I also build custom OS for the raspberry pi platform and I am well
versed with them. I have approx a dozen of them from rpi to rpi 5
I have used them for servers on the network including the original pi.
Your Raspberry Pi needs an operating system to work. This is it.
Raspberry Pi OS (previously called Raspbian) is our official supported
operating system.
The new OS called Raspberry Pi OS is a new animal.  The foundation used
raspian and the the Raspberry Pi OS is the foundations, developed by the
foundation.

Just one huge problem with all this, the NIH syndrome rules supreme as
far as your forum is concerned, I asked about a realtime kernel 3 times
so I could run linuxcnc on an rpi3b many years ago. Some body took
umbrage and I have been blackholed from posting to the forum since,
about 6 or 7 years ago. But I managed to get a realtime 4.19 built and
ran it for quite sometime, 6 years, 2 on the rpi3b, now 4 years on a 4b.
After I figured out how to install it. Uptimes in years from my method.
The forum supports music video to the near exclusion of a heck of a lot
of other stuff the pi can do. So when I got into 3d printers, it was on
bananapi-m5's running armbian. Support by Igor and friends has been so
good I throw a $20 bill in the armbian kitty every month. TANSTAAFL
folks. Natures only 100% true law.

Cheers, Gene Heskett, CET.

[d***@howorth.org.uk]

Post by Gremlin

Post by Gremlin
The provider is raspberry foundation and Raspian has been
dis-continued.

Nope that is just wrong.
https://www.raspbian.org/

[snip]

Post by Gremlin
Note: Raspbian is not affiliated with the Raspberry Pi Foundation.

[Thomas Pircher]

Post by Gremlin
The new OS called Raspberry Pi OS is a new animal. The foundation
used raspian and the the Raspberry Pi OS is the foundations, developed
by the foundation.

Yet it is still based on Debian, according to their changelog
https://downloads.raspberrypi.com/raspios_arm64/release_notes.txt

| 2023-10-10:
| * Based on Debian bookworm release

[Jeffrey Walton]

Would you pls help give tips about how to upgrade the GLIBCXX and GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian?
I am using the Raspberry Pi 4B with the Raspbian OS “Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux”, which is Debian based OS.
When running a SW I met the problem missing the required versions of GLIBCXX and GLIBC, with the details below.
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./blueriver_bitmap_streamer)

Another option is to rebuild blueriver_bitmap_streamer. Before the
build, rip out that useless symbol versioning. All that symbol
versioning does is to cause a DoS and frustrate users.

You can find the ASM directives to rip out the versioning by grepping
for '.symver'. It will be in an ASM block.

Jeff

[Gremlin]

Post by Jeffrey Walton

Would you pls help give tips about how to upgrade the GLIBCXX and GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian?
I am using the Raspberry Pi 4B with the Raspbian OS “Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux”, which is Debian based OS.
When running a SW I met the problem missing the required versions of GLIBCXX and GLIBC, with the details below.
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./blueriver_bitmap_streamer)

Another option is to rebuild blueriver_bitmap_streamer. Before the
build, rip out that useless symbol versioning. All that symbol
versioning does is to cause a DoS and frustrate users.
You can find the ASM directives to rip out the versioning by grepping
for '.symver'. It will be in an ASM block.
Jeff

https://info.semtech.com/blueriver-av-manager

The source:

https://semtech.my.salesforce.com/sfc/p/#E0000000JelG/a/RQ000001m7Hx/ptDTNUqlZvD_8F_SbhjtoHaX9jOZ_fKxuauW0cZp5ag?utm_referrer=https%3A%2F%2Finfo.semtech.com%2F

Unable to Process Request
We couldn't access the content delivery.


This content has been deleted, doesn't exist, or can't be previewed.


Gonna be hard to do that

[Jeffrey Walton]

Post by Gremlin

Post by Jeffrey Walton

Would you pls help give tips about how to upgrade the GLIBCXX and GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian?
I am using the Raspberry Pi 4B with the Raspbian OS “Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux”, which is Debian based OS.
When running a SW I met the problem missing the required versions of GLIBCXX and GLIBC, with the details below.
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./blueriver_bitmap_streamer)

Another option is to rebuild blueriver_bitmap_streamer. Before the
build, rip out that useless symbol versioning. All that symbol
versioning does is to cause a DoS and frustrate users.
You can find the ASM directives to rip out the versioning by grepping
for '.symver'. It will be in an ASM block.

https://info.semtech.com/blueriver-av-manager
https://semtech.my.salesforce.com/sfc/p/#E0000000JelG/a/RQ000001m7Hx/ptDTNUqlZvD_8F_SbhjtoHaX9jOZ_fKxuauW0cZp5ag?utm_referrer=https%3A%2F%2Finfo.semtech.com%2F
Unable to Process Request
We couldn't access the content delivery.
This content has been deleted, doesn't exist, or can't be previewed.
Gonna be hard to do that

OP might then take a look at editing the elf file directly. `objdump
--remove-section .symver blueriver_bitmap_streamer` should do the
trick.

Jeff

[Gremlin]

Post by Jeffrey Walton

Post by Gremlin

Post by Jeffrey Walton

Would you pls help give tips about how to upgrade the GLIBCXX and GLIBC to the specific version (GLIBCXX_3.4.29, GLIBC_2.34) on Debian?
I am using the Raspberry Pi 4B with the Raspbian OS “Linux raspberrypi 5.15.61-v8+ #1579 SMP PREEMPT Fri Aug 26 11:16:44 BST 2022 aarch64 GNU/Linux”, which is Debian based OS.
When running a SW I met the problem missing the required versions of GLIBCXX and GLIBC, with the details below.
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./blueriver_bitmap_streamer)
./blueriver_bitmap_streamer: /lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./blueriver_bitmap_streamer)

Another option is to rebuild blueriver_bitmap_streamer. Before the
build, rip out that useless symbol versioning. All that symbol
versioning does is to cause a DoS and frustrate users.
You can find the ASM directives to rip out the versioning by grepping
for '.symver'. It will be in an ASM block.

https://info.semtech.com/blueriver-av-manager
https://semtech.my.salesforce.com/sfc/p/#E0000000JelG/a/RQ000001m7Hx/ptDTNUqlZvD_8F_SbhjtoHaX9jOZ_fKxuauW0cZp5ag?utm_referrer=https%3A%2F%2Finfo.semtech.com%2F
Unable to Process Request
We couldn't access the content delivery.
This content has been deleted, doesn't exist, or can't be previewed.
Gonna be hard to do that

OP might then take a look at editing the elf file directly. `objdump
--remove-section .symver blueriver_bitmap_streamer` should do the
trick.
Jeff

Why?

Install a supported up to date OS and it should just work.
Raspian is an unsupported OS and has zero future.

[Jeffrey Walton]

Post by Jeffrey Walton

Post by Gremlin
[...]

Post by Jeffrey Walton
Another option is to rebuild blueriver_bitmap_streamer. Before the
build, rip out that useless symbol versioning. All that symbol
versioning does is to cause a DoS and frustrate users.
You can find the ASM directives to rip out the versioning by grepping
for '.symver'. It will be in an ASM block.

https://info.semtech.com/blueriver-av-manager
https://semtech.my.salesforce.com/sfc/p/#E0000000JelG/a/RQ000001m7Hx/ptDTNUqlZvD_8F_SbhjtoHaX9jOZ_fKxuauW0cZp5ag?utm_referrer=https%3A%2F%2Finfo.semtech.com%2F
Unable to Process Request
We couldn't access the content delivery.
This content has been deleted, doesn't exist, or can't be previewed.
Gonna be hard to do that

OP might then take a look at editing the elf file directly. `objdump
--remove-section .symver blueriver_bitmap_streamer` should do the
trick.

Why?

The OP wants to run his software.

Surely you have a better question than "Why," but I don't know what it is.

Jeff

[Gremlin]

Post by Jeffrey Walton

Post by Jeffrey Walton

Post by Gremlin
Unable to Process Request
We couldn't access the content delivery.
This content has been deleted, doesn't exist, or can't be previewed.
Gonna be hard to do that

OP might then take a look at editing the elf file directly. `objdump
--remove-section .symver blueriver_bitmap_streamer` should do the
trick.

Why?

The OP wants to run his software.
Surely you have a better question than "Why," but I don't know what it is.
Jeff

Nope it is exactly WHY?

Why not install the latest OS for raspberry pi and you won't have an
issue. Get it?