[Yocto Build] riscv64-oe-linux-gfortran issue

[LeoWeng]

While cross-compiling the OpenBLAS module, my compiler used riscv64-oe-linux-gfortran. After verification, it was found that the correct library reference path could not be found, leading to the inability to locate the corresponding libgfortran.spec.

The corresponding search paths can be found by executing the following snippet:
riscv64-oe-linux-gfortran -print-search-dirs

Here are my search paths:
Program paths:

`
/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/libexec/riscv64-oe-linux/gcc/riscv64-oe-linux/13.2.0/

/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/libexec/riscv64-oe-linux/gcc/

/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/bin/riscv64-oe-linux/bin/riscv64-oe-linux/13.2.0/

/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/bin/riscv64-oe-linux/bin/
`

Library paths:

`
/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/lib/riscv64-oe-linux/gcc/riscv64-oe-linux/13.2.0/

/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/lib/riscv64-oe-linux/gcc/

/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/lib/riscv64-oe-linux/lib/riscv64-oe-linux/13.2.0/

/build/tmp-glibc/work/riscv64-oe-linux/openblas/0.3.27/recipe-sysroot-native/usr/lib/riscv64-oe-linux/lib/

/not/exist/lib64/lp64d/riscv64-oe-linux/13.2.0/

/not/exist/lib64/lp64d/

/not/exist/usr/lib64/lp64d/riscv64-oe-linux/13.2.0/

/not/exist/usr/lib64/lp64d/

/not/exist/lib/riscv64-oe-linux/13.2.0/

/not/exist/lib/

/not/exist/usr/lib/riscv64-oe-linux/13.2.0/

/not/exist/usr/lib/
`

I am trying to understand how to correctly modify this path.
Could you please provide a method for adjusting it?
Perhaps I should make adjustments in the openembedded-core/meta/recipes-devtools/gcc within the project.
I would like to know if there is an applicable way to do this.

[LeoWeng]

The issue has been resolved. Solution:
Locate the corresponding GCC source code and manually change the parameter --with-sysroot=/not/exist to --with-sysroot=${STAGING_DIR_TARGET}.

If you intend to adjust this directly from the bb file, it has not been successful so far.