gnu-compilers: build texinfo inline#2646
Merged
Merged
Conversation
📦 Package Count Analysis ResultsEnvironment: UBI 10 Container 🏭 Factory RepositoriesStatus: ✅ Factory repositories analysis completed successfully
Analysis performed by OpenHPC Package Count CI |
🚀 CCache Statistics
📊 Detailed StatisticsopenEuler (aarch64)openEuler (x86_64)RHEL (aarch64/gnu15)RHEL (x86_64/gnu15)RHEL (x86_64/intel)🤖 Generated from workflow run |
Test Results 29 files - 75 29 suites - 75 50s ⏱️ - 5m 22s Results for commit 462f8c7. ± Comparison against base commit b6af457. This pull request removes 242 tests.♻️ This comment has been updated with latest results. |
Member
|
What about building texinfo before building the compiler like here: https://github.com/openhpc/ohpc/blob/4.x/components/mpi-families/mvapich2/SPECS/mvapich2.spec#L35 Would that be doable? |
viniciusferrao
force-pushed
the
gnu-compilers-openeuler
branch
from
286664b to
fcb1959
Compare
Contributor
Author
|
Is it a build cache issue that causes aarch64 build to fail? I could not make sense of it. |
Member
No idea what is going trying a rebuild works: #2647 |
Member
|
Maybe try the texinfo change for openeuler on all arches. |
openEuler has no dependable texinfo -- none at all on its ppc64le port, and only in the everything repo elsewhere. Bundle texinfo and build it inline before GCC on openEuler (all arches), like mvapich2/sowing, so makeinfo is available and gcc.info, gfortran.info, etc. are generated. Distro texinfo is still used on non-openEuler distros. Verified on native ppc64le (full GCC build, all 9 info manuals) and on openEuler x86_64 (inline texinfo builds, makeinfo functional), both with texinfo absent from the system. Signed-off-by: Vinícius Ferrão <ferrao@versatushpc.com.br> Sponsored-by: VersatusHPC
viniciusferrao
force-pushed
the
gnu-compilers-openeuler
branch
from
fcb1959 to
462f8c7
Compare
Member
|
Now it fails because the upstream tar archive locations are not reachable. I will trigger a rebuild soon. |
viniciusferrao
changed the title
Member
|
Now it works. This is a bit strange, but let's merge it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi @adrianreber, this one is a little bit different. And I think this is the last one in the track of
ppc64le.openEuler's does not ship texinfo in
ppc64leSo the idea was to gate the BuildRequires to openEulerppc64leonly; it stays on EL, SUSE, and openEuler x86_64/aarch64, etc.I didn't removed it because we would lose the docs for every system. The info manuals (gcc.info, gfortran.info, etc) are skipped there.
There is a decision here: should OpenHPC drops the info manuals, or ships texinfo for OpenEuler
ppc64le.