Open-source News

Surfshark VPN Now Offers a Full-fledged GUI App for Linux  It's FOSS News

Dynamically linking libraries while compiling code Seth Kenlon Mon, 05/30/2022 - 03:00 Register or Login to like Register or Login to like

Compiling software is something that developers do a lot, and in open source some users even choose to do it themselves. Linux podcaster Dann Washko calls source code the "universal package format" because it contains all the components necessary to make an application run on any platform. Of course, not all source code is written for all systems, so it's only "universal" within the subset of targeted systems, but the point is that source code is extremely flexible. With open source, you can decide how code is compiled and run.

When you're compiling code, you're usually dealing with multiple source files. Developers tend to keep different classes or modules in separate files so that they can be maintained separately, and possibly even used by different projects. But when you're compiling these files, many of them get compiled into a single executable.

This is usually done by creating shared libraries, and then dynamically linking back to them from the executable. This keeps the executable small by keeping modular functions external, and ensures that libraries can be updated independently of the applications that use them.

Programming and development Red Hat Developers Blog Programming cheat sheets Try for free: Red Hat Learning Subscription eBook: An introduction to programming with Bash Bash shell scripting cheat sheet eBook: Modernizing Enterprise Java Locating a shared object during compilation

When you're compiling with GCC, you usually need a library to be installed on your workstation for GCC to be able to locate it. By default, GCC assumes that libraries are in a system library path, such as /lib64 and /usr/lib64. However, if you're linking to a library of your own that's not yet installed, or if you need to link to a library that's not installed in a standard location, then you have to help GCC find the files.

There are two options significant for finding libraries in GCC:

• -L (capital L) adds an additional library path to GCC's search locations.
• -l (lowercase L) sets the name of the library you want to link against.

For example, suppose you've written a library called libexample.so, and you want to use it when compiling your application demo.c. First, create an object file from demo.c:
 

$ gcc -I ./include -c src/demo.c

The -I option adds a directory to GCC's search path for header files. In this example, I assume that custom header files are in a local directory called include. The -c option prevents GCC from running a linker, because this task is only to create an object file. And that's exactly what happens:
 

$ ls
demo.o   include/   lib/    src/

Now you can use the -L option to set a path for your library, and compile:
 

$ gcc -L`pwd`/lib -o myDemo demo.o -lexample

Notice that the -L option comes before the -l option. This is significant, because if -L hasn't been added to GCC's search path before you tell GCC to look for a non-default library, GCC won't know to search in your custom location. The compilation succeeds as expected, but there's a problem when you attempt to run it:
 

$ ./myDemo
./myDemo: error while loading shared libraries:
libexample.so: cannot open shared object file:
No such file or directoryTroubleshooting with ldd

The ldd utility prints shared object dependencies, and it can be useful when troubleshooting issues like this:

$ ldd ./myDemo
        linux-vdso.so.1 (0x00007ffe151df000)
        libexample.so => not found
        libc.so.6 => /lib64/libc.so.6 (0x00007f514b60a000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f514b839000)

You already knew that libexample couldn't be located, but the ldd output at least affirms what's expected from a working library. For instance, libc.so.6 has been located, and ldd displays its full path.

LD_LIBRARY_PATH

The LD_LIBRARY_PATH environment variable defines the path to libraries. If you're running an application that relies on a library that's not installed to a standard directory, you can add to the system's library search path using LD_LIBRARY_PATH.

There are several ways to set environment variables, but the most flexible is to place them before you run a command. Look at what setting LD_LIBRARY_PATH does for the ldd command when it's analyzing a "broken" executable:
 

$ LD_LIBRARY_PATH=`pwd`/lib ldd ./
   linux-vdso.so.1 (0x00007ffe515bb000)
   libexample.so => /tmp/Demo/lib/libexample.so (0x0000...
   libc.so.6 => /lib64/libc.so.6 (0x00007eff037ee000)
   /lib64/ld-linux-x86-64.so.2 (0x00007eff03a22000)

It applies just as well to your custom command:
 

$ LD_LIBRARY_PATH=`pwd`/lib myDemo
hello world!

If you move the library file or the executable, however, it breaks again:
 

$ mv lib/libexample.so ~/.local/lib64
$ LD_LIBRARY_PATH=`pwd`/lib myDemo
./myDemo: error while loading shared libraries...

To fix it, you must adjust the LD_LIBRARY_PATH to match the library's new location:
 

$ LD_LIBRARY_PATH=~/.local/lib64 myDemo
hello world!When to use LD_LIBRARY_PATH

In most cases, LD_LIBRARY_PATH isn't a variable you need to set. By design, libraries are installed to /usr/lib64 and so applications naturally search it for their required libraries. You may need to use LD_LIBRARY_PATH in two cases:

• You're compiling software that needs to link against a library that itself has just been compiled and has not yet been installed. Good build systems, such as Autotools and CMake, can help handle this.
• You're bundling software that's designed to run out of a single directory, with no install script or an install script that places libraries in non-standard directories. Several applications have releases that a Linux user can download, copy to /opt, and run with "no install." The LD_PATH_LIBRARY variable gets set through wrapper scripts so the user often isn't even aware it's been set.

Compiling software gives you a lot of flexibility in how you run your system. The LD_LIBRARY_PATH variable, along with the -L and -l GCC options, are components of that flexibility.

Compiling software gives you a lot of flexibility in how you run your system. The LD_LIBRARY_PATH variable, along with the -L and -l GCC options, are components of that flexibility.

Image by:

WOCinTech Chat. Modified by Opensource.com. CC BY-SA 4.0

Programming What to read next Anyone can compile open source code in these three simple steps A programmer's guide to GNU C Compiler This work is licensed under a Creative Commons Attribution-Share Alike 4.0 International License. Register or Login to post a comment.

As part of ISC 2022 happening this week in Hamburg, Germany, the new Top500 supercomputer and Green500 energy efficiency lists have been published...

The post How to Install EPEL Repository in RHEL 9 Linux first appeared on Tecmint: Linux Howtos, Tutorials & Guides .

Installing the EPEL repository is one of the most recommended steps after you install RHEL 9. To make things easy for you, we are not just going to show you installation steps but rather

The post How to Install EPEL Repository in RHEL 9 Linux first appeared on Tecmint: Linux Howtos, Tutorials & Guides.

Surfshark VPN for Linux gets proper GUI  BetaNews

While Intel has long supported GPU-based video decode acceleration on Linux using the Video Acceleration API (VA-API) and more recently via oneVPL under their oneAPI umbrella, with their Intel Media Driver stack they have begun offering support for video decoding using the cross-platform video acceleration extensions to the Vulkan API...

Just in time for Arch Linux's June 2022 monthly ISO refresh, Archinstall 2.5 was released today as the newest version of this text-based Arch Linux installer...

How to Easily Create QR Codes on Linux  MUO - MakeUseOf

How to Easily Create QR Codes on Linux  MUO - MakeUseOf

Arch Linux’s Menu-Based Installer Gets New Disk Preview, FIDO2 Support, and More  9to5Linux

A Microsoft-contributed fix as part of their Hyper-V updates for the Linux 5.19 kernel can shave minutes off their Azure VM boot times when launching a virtual machine with numerous GPUs...

The EFI changes for the Linux 5.19 kernel bring a few interesting changes, including the ability to access secrets injected into the boot image via Confidential Computing "CoCo" hypervisors...

The Chrome platform updates for Linux 5.19 bring various fixes as well as a new ChromeOS ACPI device driver, but for the most part is relatively basic. One notable addition though is the Framework Laptop now having support by cros_ec_lpcs with that modular Linux laptop making use of Google's ChromeOS embedded controller...

AMD could be readying a super-cheap GPU to tackle Nvidia's rumored GTX 1630  TechRadar

AMD could be readying a super-cheap GPU to tackle Nvidia's rumored GTX 1630  TechRadar

A new version of Distrobox was released today, the open-source system that allows quickly and easily launching different distributions from your terminal via Podman or Docker. Distrobox has been a popular option for augmenting the package selection/versions available on your system or as well for firing up faster versions of software...

The XFS file-system updates for the Linux 5.19 merge window are on the heavier side with this pull being described as "a big update with lots of new code" abound for this summer 2022 kernel release...

XFS With Linux 5.19 Brings "Lots Of New Code"  Phoronix

Embedded Software Market by Type (OS X, Windows, GNU / Linux), Application (Automotive, Healthcare, Consumer Electronics , Military & Defense, Industrial, Telecommunication), and Geography – Global Trends & Forecasts to 2019-2029 – Man  ManufactureLink

Linux 5.19 Allows EFI Accessing VM Secrets For Confidential Computing / AMD SEV  Phoronix