Change in osmo-gsm-tester[master]: util: adds the feature to force the rpath when patching files.

alealcon gerrit-no-reply at
Thu Jun 3 16:31:39 UTC 2021

alealcon has posted comments on this change. ( )

Change subject: util: adds the feature to force the rpath when patching files.

Patch Set 1:

Hi Pau, 

As a summary I'm going to do:

- Abandon this commit (remove the patchelf_force function and do not implement the extra option for the normal patchelf function)
- Abandon 
- I will create the as we talked, in a new commit, updating if needed the if needed.

Answering these 2 questions:

- Why does * sets the rpath?

For the code I'm seeing from amarisoft epc and ue, it seems that the binaries are not patched in the job, so it is done in ms-amarisoft. The path that its patched seems different too, as it patches "remote_inst" (at least for the epc)

- Why we have a different libc version. 

When we build a new toolchain we try to get the latest stable version of each library, to get the latest features/stability/performance.
Sadly, the OS running in that platforms it's too old, and because it is a leasing we cannot update the system libraries/utilities. That's why we have to patch the binary with "--force-rpath". If we could have updated those libraries, it would have been way easiest :D.

Thanks for all your suggestions, information and patience, Pau.


To view, visit
To unsubscribe, or for help writing mail filters, visit

Gerrit-Project: osmo-gsm-tester
Gerrit-Branch: master
Gerrit-Change-Id: I2d4a105d4843c0d31d6b5d8f8d4195247b290aec
Gerrit-Change-Number: 24272
Gerrit-PatchSet: 1
Gerrit-Owner: alealcon <alejandro.leal at>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin at>
Gerrit-Comment-Date: Thu, 03 Jun 2021 16:31:39 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list