Skip to content

don't use non-existing --enable-sve configure option when building FFTW on Arm system that supports SVE#3696

Merged
branfosj merged 1 commit intoeasybuilders:developfrom
boegel:20250410160753_new_pr_fftw
Apr 10, 2025
Merged

don't use non-existing --enable-sve configure option when building FFTW on Arm system that supports SVE#3696
branfosj merged 1 commit intoeasybuilders:developfrom
boegel:20250410160753_new_pr_fftw

Conversation

@boegel
Copy link
Copy Markdown
Member

@boegel boegel commented Apr 10, 2025 •
edited
Loading

(created using eb --new-pr)

fix for:

configure: WARNING: unrecognized options: --enable-sve

== 2025-04-10 13:56:19,438 run.py:601 INFO Shell command completed successfully (see output above): ./configure --prefix=/software/FFTW/3.3.10-GCC-14.2.0  --build=aarch64-unknown-linux-gnu  --host=aarch64-unknown-linux-gnu --enable-single --with-pic --enable-openmp --enable-shared --enable-threads --enable-fma --enable-sve --enable-armv8-cntvct-el0
== 2025-04-10 13:56:19,507 build_log.py:226 ERROR EasyBuild encountered an error (at easybuild/base/exceptions.py:126 in __init__): Found unrecognized configure options: --enable-sve (at easybuild/easyblocks/generic/configuremake.py:355 in configure_step)

@boegel boegel added bug fix aarch64 Related to Arm 64-bit (aarch64) labels Apr 10, 2025
@boegel boegel added this to the release after 5.0.0 milestone Apr 10, 2025
@boegel boegel changed the title don't use non-existing --enable-sve configure option when building FFTW on Arm system that supports SVE don't use non-existing --enable-sve configure option when building FFTW on Arm system that supports SVE Apr 10, 2025
@boegel
Copy link
Copy Markdown
Member Author

boegel commented Apr 10, 2025

@boegelbot please test @ jsc-zen3
EB_ARGS="--installpath /tmp/$USER FFTW-3.3.10-GCC-13.3.0.eb FFTW.MPI-3.3.10-gompi-2024a.eb"
CORE_CNT=16

@boegel boegel mentioned this pull request Apr 10, 2025
Merged
1 task
@boegelbot
Copy link
Copy Markdown

boegelbot commented Apr 10, 2025

@boegel: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de

PR test command 'if [[ develop != 'develop' ]]; then EB_BRANCH=develop ./easybuild_develop.sh 2> /dev/null 1>&2; EB_PREFIX=/home/boegelbot/easybuild/develop source init_env_easybuild_develop.sh; fi; EB_PR=3696 EB_ARGS="--installpath /tmp/$USER FFTW-3.3.10-GCC-13.3.0.eb FFTW.MPI-3.3.10-gompi-2024a.eb" EB_REPO=easybuild-easyblocks EB_BRANCH=develop /opt/software/slurm/bin/sbatch --job-name test_PR_3696 --ntasks="16" ~/boegelbot/eb_from_pr_upload_jsc-zen3.sh' executed!

  • exit code: 0
  • output:
Submitted batch job 6157

Test results coming soon (I hope)...

Details

- notification for comment with ID 2793546068 processed

Message to humans: this is just bookkeeping information for me,
it is of no use to you (unless you think I have a bug, which I don't).

@boegelbot
Copy link
Copy Markdown

boegelbot commented Apr 10, 2025

Test report by @boegelbot

Overview of tested easyconfigs (in order)

  • SUCCESS FFTW-3.3.10-GCC-13.3.0.eb
  • SUCCESS FFTW.MPI-3.3.10-gompi-2024a.eb

Build succeeded for 2 out of 2 (2 easyconfigs in total)
jsczen3c1.int.jsc-zen3.fz-juelich.de - Linux Rocky Linux 9.5, x86_64, AMD EPYC-Milan Processor (zen3), Python 3.9.21
See https://gist.github.com/boegelbot/1c674a706fc4d8aad746ae1645c7d33b for a full test report.

@branfosj branfosj merged commit 6cb0bfc into easybuilders:develop Apr 10, 2025
17 checks passed
@boegel boegel deleted the 20250410160753_new_pr_fftw branch April 10, 2025 16:46
@boegel boegel mentioned this pull request May 23, 2025
Merged
@migueldiascosta
Copy link
Copy Markdown
Member

migueldiascosta commented Jul 12, 2025

just a note that --enable-sve will exist in FFTW 3.3.11, it has already been merged (https://github.com/rdolbeau/fftw3/wiki)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@branfosj branfosj branfosj approved these changes

Assignees

No one assigned

Labels

aarch64 Related to Arm 64-bit (aarch64) bug fix

Projects

None yet

Milestone

5.1.0

Development

Successfully merging this pull request may close these issues.

4 participants

@boegel @boegelbot @migueldiascosta @branfosj