You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(I have reported the same issue to bug-gsl using the GNU mailing list. But no response: bug-gsl link)
Hi.
I'm working on a project where I compile with different optimization options for different target architectures in different compile versions.
Cross-compilation failed when compiling GSL package. (compiler hang)
First, the compiled environment is inside the Docker container, and the Docker image is based on ubuntu:16.04. The host running that Docker container is x86_64 Ubuntu 20.04.5 LTS.
The following is the result of executing 'uname -a' in an environment where compiling GSL fails.
$ uname -aLinux 30a3b73aab3b 5.4.0-125-generic #141-Ubuntu SMP Wed Aug 10 13:42:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Inside the ubuntu:16.04 Docker container, I tried to build GSL with the following options.
When I tried GSL for the above compiler options, it failed to compile in the following case.
compiler version: Clang 8 and Clang 9
target architecture: arm_32
optimization level: Ofast
i.e. it failed to cross-compile GSL with Ofast option with arm_32 target architecture with Clang 8 and Clang 9 in x86_64 environment. (In all other cases the GSL build succeeded.)
I also tried to build by downgrading the GSL version since the build failed on GSL 2.7.1. But GSL 2.7, GSL 2.6, GSL 2.5, GSL 2.4 all failed to build. (I haven't tried lower versions. I'd like to compile the highest version, GSL 2.7.1, if possible.)
The reason why the build failed was because of the 'compiler hang', and in particular, I analyzed which command the hang occurred when trying.
As a result of checking with the htop command, hang occurred while executing the two commands below, and it was confirmed that the size of the virtual memory occupied by the process executing these two commands increased to 42G.
Can you please confirm if it is possible to build (cross-compile) GSL with Ofast option with arm_32 target architecture with Clang 8 and Clang 9 in x86_64 environment?
I am new to bug report and issue open. Required information may be missing.
If you request additional information, we will respond faithfully.
Thank you.
The text was updated successfully, but these errors were encountered:
(I have reported the same issue to bug-gsl using the GNU mailing list. But no response: bug-gsl link)
Hi.
I'm working on a project where I compile with different optimization options for different target architectures in different compile versions.
Cross-compilation failed when compiling GSL package. (compiler hang)
First, the compiled environment is inside the Docker container, and the Docker image is based on
ubuntu:16.04
. The host running that Docker container is x86_64 Ubuntu 20.04.5 LTS.The following is the result of executing 'uname -a' in an environment where compiling GSL fails.
Inside the
ubuntu:16.04
Docker container, I tried to build GSL with the following options.When I tried GSL for the above compiler options, it failed to compile in the following case.
i.e. it failed to cross-compile GSL with Ofast option with arm_32 target architecture with Clang 8 and Clang 9 in x86_64 environment. (In all other cases the GSL build succeeded.)
I also tried to build by downgrading the GSL version since the build failed on GSL 2.7.1. But GSL 2.7, GSL 2.6, GSL 2.5, GSL 2.4 all failed to build. (I haven't tried lower versions. I'd like to compile the highest version, GSL 2.7.1, if possible.)
The reason why the build failed was because of the 'compiler hang', and in particular, I analyzed which command the hang occurred when trying.
As a result of checking with the htop command, hang occurred while executing the two commands below, and it was confirmed that the size of the virtual memory occupied by the process executing these two commands increased to 42G.
Can you please confirm if it is possible to build (cross-compile) GSL with Ofast option with arm_32 target architecture with Clang 8 and Clang 9 in x86_64 environment?
I am new to bug report and issue open. Required information may be missing.
If you request additional information, we will respond faithfully.
Thank you.
The text was updated successfully, but these errors were encountered: