mdolab / mdolab/adflow

Installation failed on Centos 7-based cluster

Open
#363 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Fortran
Stars
332
Forks
124
PR merge metrics
No merged PRs in 30d

Description

I attempted to install ADflow on a homogeneous HPC supercomputer (all nodes share the same architecture) using Intel Composer 2017. Initially, I encountered the following error: 'for' loop initial declarations are only allowed in C99 mode. I resolved this by adding -std=c99 to the C flags in the Makefile. However, upon rerunning the build, I encountered a new error: (mpicc -fPIC -O -std=c99 -I../c_defines -I../metis-4.0 -I/path/to/petsc/build/include -c ../adjoint/ADFirstAidKit/adStack.c -o adStack.o

    --- Compiled metisInterface.c successfully ---

../adjoint/ADFirstAidKit/adStack.c:65:1: error: unknown type name ‘u_int64_t’
static u_int64_t pushPopTraffic = 0 ;).

I haven't been able to resolve this issue. Could you please provide assistance or any tips to address this? (PS. I installed the CGNS and PETSc from the source using the same compiler)

Moreover, I attempted another way to install it by creating a conda environment having the latest versions of all recommended packages on this website (https://mdolab-mach-aero.readthedocs-hosted.com/en/latest/installInstructions/install3rdPartyPackages.html) using anaconda 2024 but failed and gave the following error:
(../adjoint/outputReverseFast/utils_fast_b.f90
/path/to/adflow/src/build/fort_depend.py:86: SyntaxWarning: invalid escape sequence '\s')

Code versions for the first attempt
  • Operating System: Centos 7 Kernal 2.10
  • Python: Python 3.6.8
  • OpenMPI: impi 2017
  • CGNS: 4.4
  • PETSc: 3.21.4
  • Compiler: Intel Composer 2017
Code versions for the second attempt
  • Operating System: Centos 7 Kernal 2.10
  • Python: Python 3.12.2
  • OpenMPI: 4.1.4
  • CGNS: 4.4
  • PETSc: 3.21.4
  • Compiler:

I really appreciate any help you can provide.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the installation with the listed CentOS 7, Intel Composer, MPI, PETSc, and CGNS versions. Inspect the Makefile around the C flags, adjoint/ADFirstAidKit/adStack.c, and src/build/fort_depend.py, then compare the two reported environments. Done means identifying a supported configuration or documenting the specific build changes needed for these environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
anaconda, c, centos, fortran, python
Domain
build-system, hpc, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.