Qt support agent claims that linuxdeploy patchelf is "corrupting" object files, problem seen on Qt66->Qt65 LTS downgrade

[mdear]

After going back and forth and finding that I had to hack linuxdeploy to refrain from doing patchelf in some cases after I downgraded from Qt-6.6 to long term support Qt-6.5.x I finally created this issue and pointed to it from the Qt case.

The Qt agent thinks that we "got lucky" in Qt6.6 but maintains that the patchelf is "corrupting" the object files. It's the classic support fingerpointing. I want no part of it, I'll continue to patch my linux deploy but if I do end up making a PR I will not include those hacks.

For posterity, or if you wish to continue the discussion with the Qt support engineer, the painful details are below. I've done all I'm willing/able to do as I have to move on with project deliverables.

linuxdeploy-patchelf-potentially-breaks-qt5_3.txt

[TheAssassin]

Some patchelf versions can break binaries. The question is how. I don't have access to official binaries and am not really interested in working with these eitehr. Patches improving the situation are very much welcome.