Created attachment 1248454[details]
patch
Description of problem:
The DOE has identified that software is the key to unlocking the potential of the next generation of supercomputing systems. To be able to facilitate this new generation of software, tools are needed. As a response LLNL is scaling up its tools team. These new hires and collaborators need better dynamic linker documentation since it is a primary interface for many kinds of tooling.
Here is a proposed patch which adds a chapter to the glibc manual. It has been submitted upstream but it hasn't been applied.
What is the problem with taking the attached patch first into upstream glibc and then backporting it rhel? It is a doc only patch and so the risk is very low.
If you need changes to the patch please speak up and identify what needs to be changed.
We are going to track this upstream here:
"Bug 25595 - Impove the quality of dynamic linker documentation"
https://sourceware.org/bugzilla/show_bug.cgi?id=25595
This bug is now CLOSED/UPSTREAM and we'll triage this upstream and get it integrated there.
These issues will then naturally become a part of the next version of RHEL. We may review CLOSED/UPSTREAM bugs for backport.
Created attachment 1248454 [details] patch Description of problem: The DOE has identified that software is the key to unlocking the potential of the next generation of supercomputing systems. To be able to facilitate this new generation of software, tools are needed. As a response LLNL is scaling up its tools team. These new hires and collaborators need better dynamic linker documentation since it is a primary interface for many kinds of tooling. Here is a proposed patch which adds a chapter to the glibc manual. It has been submitted upstream but it hasn't been applied.