Compile BlueZ without updating glib - compilation

I try to compile Bluez 5.33, but after a try to configure the package, the error message configure: error: GLib >= 2.28 is required appears.
But the problem is, i am not allowed to update or install anything on this machine. How can i compile BlueZ 5.33 without updating GLib?

It depends on a newer version of GLib for a reason, it won't compile with an older version. You either build against a newer version of GLib or you stay with an older version of BlueZ.
ps: By the way, if you can't install anything on the machine, why could you use a newer version of BlueZ?

Related

latest version glibc not configured properly on my Linux distro image

Recently, I have installed glibc-2.35 version on my Linux distribution, before I have glibc-2.27 version. After Installing I am not able to use latest version glibc as a default for compiling source code.
As a sample trail, I have successfully compiled sample program with the latest version glibc by using following command.
gcc sample.c -o out -Wl,--rpath=/usr/lib -Wl,--dynamic-linker=/usr/lib/ld-linux-riscv64-lp64d.so.1
Here, I am facing a big difficulty is how to set latest glibc as a default glibc so that I can compile source packages normally like .configure and make -j8 and make install.
Please help me to solve this issue. I am not aware of pathcelf stuff how to use exactly.

Install older version of gcc cross compiler for arm on Ubuntu

I need to use gcc-arm-linux-gnueabi version 6.5, along with a version of libc that came out around the same period (I believe is libc-2.26). My host system is Ubuntu 18.04.
If I go with just a simple
sudo apt-get install gcc-arm-linux-gnueabi g++-arm-linux-gnueabi binutils-arm-linux-gnueabi
I'll get v7 for the gcc cross compiler and v2.30 for binutills, which does not work for me, since I'll end up with errors similar to the one described here.
If I try to download the deb packages, I get unmet dependencies.
I have also tried to force apt-get to install specific versions, using something like described here but I get error messages that the version I'm looking for cannot be found.
Is there a way to force ubuntu to install specific (older) version of gcc, libc, etc.?
I know that gcc v 6 is obsolete, but I cannot do otherwise.
You could give a try to the Linaro release of gcc 6.5, available here, which comes with glibc version 2.23.

Run or use GCC without install

Can I use GCC for e.g GCC4.0.3 without installation
In my macOS I have installed Clang xcode , and GCC from Homebrew
In my Linux they are installed as well
But I want to use GCC (Specially older version) besides most updated version
Like NVM that manage Node version and it lets you install many nodejs with different version on your system
I want to use GCC4 specially for science and compiling Old FORTRAN to make my Source codes run and see the results
In new OS both macOS and Linux when you install gcc it will install most updated and that is not useful for old fortran or old codes.
So In my solution i think its better to use gcc without install or even install gcc to custom directory folder and copy the codes in that directory and compile them but not to install as wide system and make incompatibility with default GCC and CLANG on system
Thanks in advance

XCODE GCC6 Compatibility

I downloaded the latest version of GCC (6.2.0) using homebrew. It works great from the command line (you have to make sure you really use it and not the g++ override that XCODE does)
If I try to tell XCODE to use this version of GCC as the compiler, it says it is incompatible.
Did I download the wrong thing? Is this just because it's so new?

Update libstdc++.so.6 without updating gcc? Rhel 6.7

I'm trying to install a package that requires GLIBCXX_3.4.20. GCC version is 4.4, the highest version yum lists. Is there a way to upgrade to 4.9 without building it from source or just update libstdc++?
you probably could just grab a recent Fedora libstdc++ rpm, unpack it using something like rpm2targz, and then move the two shared libs into /usr/local/lib/, then run ldconfig.
you might need to adjust the rpm (x86_64-vs-i686) and lib-vs-lib64 paths depending on your setup.
using a newer libstdc++.so with an older gcc version shouldn't usually be too much of a problem. they're good about backwards compat support in the shared libs.

Resources