You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When moving from 0.15 to 0.18 all my builds broke on rhel7/8/9.
The issue shows up as traffic_server: error while loading shared libraries: libhwloc.so.15: ELF load command address/offset not properly aligned
Steps To Reproduce
compile code with a compiler less than gcc 12 ( which is common on rhel system) and run patchelf to change the run path. running the program will result in the aligned error from above.
The workaround is to recompile the code gcc 12 ( available on rhel with devtool )
If using the older compile I found I had to move back to 0.15
Expected behavior
It should not break the binary based on the compiler
Additional context
This is more of a note as many issues here may have the same problem. just using a newer compiler fixed the problem with patchelf.
The text was updated successfully, but these errors were encountered:
Seems like this is possibly a duplicate of #528? The thing about alignment issues is that there are a lot of things that can affect whether or not one hits the bug.
Describe the bug
When moving from 0.15 to 0.18 all my builds broke on rhel7/8/9.
The issue shows up as
traffic_server: error while loading shared libraries: libhwloc.so.15: ELF load command address/offset not properly aligned
Steps To Reproduce
compile code with a compiler less than gcc 12 ( which is common on rhel system) and run patchelf to change the run path. running the program will result in the aligned error from above.
The workaround is to recompile the code gcc 12 ( available on rhel with devtool )
If using the older compile I found I had to move back to 0.15
Expected behavior
It should not break the binary based on the compiler
Additional context
This is more of a note as many issues here may have the same problem. just using a newer compiler fixed the problem with patchelf.
The text was updated successfully, but these errors were encountered: