On 1/3/25 16:45, Zhang, Peng (Paul) (CN) via lists.openembedded.org wrote:
From: Zhang Peng<peng.zhang1...@windriver.com>
When building the `lapack` package, the following QA error occurs:
"File /usr/lib64/libblas.so.3.12.0 in package lapack contains reference to TMPDIR
[buildpaths]"
The issue arises because the `xerbla.o` object file embeds the absolute host
path of `xerbla.f`.
This occurs during compilation, where the build command in `build.make`
(generated by CMake) specifies:
`gfortran -c <absolute path>/xerbla.f -o`.
As a result, the absolute path is included in `xerbla.o`. Unfortunately,
`gfortran` does not support
flags like `-fdebug-prefix-map` or `-ffile-prefix-map` to remove such paths.
To resolve this, the fix involves replacing the absolute path of `xerbla.f` in
the generated
`build.make` file with a relative path before the compilation step. This
ensures that the
resulting `xerbla.o` does not contain any references to TMPDIR, passing the
`do_package_qa` check.
Signed-off-by: Zhang Peng<peng.zhang1...@windriver.com>
---
.../recipes-devtools/lapack/lapack_3.12.0.bb | 23 +++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/meta-oe/recipes-devtools/lapack/lapack_3.12.0.bb
b/meta-oe/recipes-devtools/lapack/lapack_3.12.0.bb
index fef9d3a80e..ef5726eeaa 100644
--- a/meta-oe/recipes-devtools/lapack/lapack_3.12.0.bb
+++ b/meta-oe/recipes-devtools/lapack/lapack_3.12.0.bb
@@ -33,6 +33,29 @@ OECMAKE_GENERATOR = "Unix Makefiles"
inherit cmake pkgconfig ptest
EXCLUDE_FROM_WORLD = "1"
+# The `xerbla.o` file contains an absolute path in `xerbla.f.o`, but the options
+# `-fdebug-prefix-map` and `-ffile-prefix-map` cannot be used because gfortran
does not support them.
+# To address this issue, we manually replace the absolute path with a relative
path
+# in the generated `build.make` file.
+#
+# An issue has been
reported:https://github.com/Reference-LAPACK/lapack/issues/1087,
+# requesting a fix in the source code.
+#
+# This workaround resolves the TMPDIR [buildpaths] issue by converting the
absolute path
+# of `xerbla.f` to a relative path. The steps are as follows:
+#
+# 1. Locate all `build.make` files after the `do_configure` step is completed.
+# 2. Compute the relative path for `xerbla.f` based on the current build
directory.
+# 3. Replace the absolute path with the calculated relative path in the
`build.make` files
+
While the current implementation resolves the immediate issue
effectively, I recognize that the approach may not be the most optimal
or elegant. I believe there might be a better way to address this issue
If anyone has any suggestions, alternative ideas, or feedback on how to
improve this solution, I would greatly appreciate your input.
Thank you for taking the time to review and share your thoughts!
//Peng
+do_configure:append(){
+ for file in `find ${B} -name build.make`; do
+ sed -i -e "s#\(.*-c \).*\(/xerbla\.f \)#\1$(grep '\-c .*xerbla\.f'
$file | awk -F'cd ' '{print $2}'| \
+ awk '{src=$1; sub(/.*-c /, ""); sub(/xerbla\.f.*/, "");
obj=$0; print src, obj}' | \
+ while read src obj; do echo "$(realpath --relative-to="$src"
"$obj")"; done)\2#g" $file
+ done
+}
+
do_install_ptest () {
rsync -a ${B}/TESTING ${D}${PTEST_PATH} \
--exclude CMakeFiles \
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#114624):
https://lists.openembedded.org/g/openembedded-devel/message/114624
Mute This Topic: https://lists.openembedded.org/mt/110403421/21656
Group Owner: openembedded-devel+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-devel/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
