Shared Lib Support Test Fails on RHEL Platforms #15
Comments
Tevo45
added a commit
to Tevo45/xmlada
that referenced
this issue
Dec 20, 2024
Previously, we used the --host and --target arguments of the configure script to mean the build machine and the machine the package will run on, mirroring GPRBuild's own usage of the flags. By convention, however, autoconf scripts usually take --build to mean the build machine, --host to mean the machine the package will run on and --target to mean the target of the toolchain being configured (if relevant). Our non-standard usage tends to cause problems with some distribution's packaging machinery (such as Void Linux's, or RHEL's), which often follow autoconf's conventions instead. When in Rome, do as the Romans do; hopefully this won't confuse GPRBuild users (too much)! Fixes AdaCore#15
Tevo45
added a commit
to Tevo45/xmlada
that referenced
this issue
Dec 20, 2024
Previously, we used the --host and --target arguments of the configure script to mean the build machine and the machine the package will run on, mirroring GPRBuild's own usage of the terminology. By convention, however, autoconf scripts usually take --build to mean the build machine, --host to mean the machine the package will run on and --target to mean the target of the toolchain being configured (if relevant). Our non-standard usage tends to cause problems with some distribution's packaging machinery (such as Void Linux's, or RHEL's), which often follow autoconf's conventions instead. When in Rome, do as the Romans do; hopefully this won't confuse GPRBuild users (too much)! Fixes AdaCore#15
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Commit cc01d58 introduced in community-2018 release causes regression on RedHat and probably also Fedora systems:
rpmbuild usually applies a %configure macro during build process. This macro sets the build and the host platform and passes them as parameter to the configure script. But not the target platform. This is not an issue, as configure --help clearly states the following strategy:
configure assumes the target platform to be the same as the host platform, if not explicitly specified.
Commit cc01d58 violates this strategy. If --host is passed but not --target $target_alias is NULL, i. e. different from $host_alias, configure tries to check gprbuild's shared library support for an unspecified target platform (NULL), which leads to following failure:
gprbuild: illegal option "--target=" on the command lineCheck will always fail regardless if the host=target platform supports shared GNAT libraries or not.
The text was updated successfully, but these errors were encountered: