| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| install_actflow [2024/10/14 10:37] – [Linux/Unix-like environments] rajit | install_actflow [2025/11/21 10:55] (current) – [MacOS] rajit |
|---|
| |
| Primary development of the tools in the actflow repository is conducted on Linux and MacOS, and so it has been extensively tested on such systems. It has also been tested in certain [[install#Microsoft Windows|Windows]] environments (see below). | Primary development of the tools in the actflow repository is conducted on Linux and MacOS, and so it has been extensively tested on such systems. It has also been tested in certain [[install#Microsoft Windows|Windows]] environments (see below). |
| | |
| | If you are a Homebrew user, check out the [[https://github.com/asyncvlsi/homebrew-tap|homebrew tap]] for the tools. |
| | |
| | |
| | ===== Getting the source ===== |
| | |
| |
| The repository is available from [[https://github.com/asyncvlsi/actflow|Github]]. Once you clone this repository, make sure you run | The repository is available from [[https://github.com/asyncvlsi/actflow|Github]]. Once you clone this repository, make sure you run |
| https://github.com/asyncvlsi/actflow/blob/main/.circleci/config.yml | https://github.com/asyncvlsi/actflow/blob/main/.circleci/config.yml |
| |
| for ''Debian'', ''Ubuntu'' look at the ubuntu section. Here's the script used by the continuous integration build on Ubuntu to build and install the tools in ''/usr/local/cad'', and run the test cases: | ==== Debian or Ubuntu Linux ==== |
| | |
| | For ''Debian'', ''Ubuntu'' look at the ubuntu section. Here's the script used by the continuous integration build on Ubuntu to build and install the tools in ''/usr/local/cad'', and run the test cases: |
| <code> | <code> |
| $ apt-get -q update -y | $ apt-get -q update -y |
| |
| Replace ''/usr/local/cad'' on the lines where it is used with your actual installation directory. | Replace ''/usr/local/cad'' on the lines where it is used with your actual installation directory. |
| | |
| | ==== Alpine Linux ==== |
| |
| For Alpine Linux look at the alpine section in the yml file. | For Alpine Linux look at the alpine section in the yml file. |
| |
| **MacOS:** Recent versions of MacOS have a C++ compiler issue, namely that the default compiler distributed by Apple does not support the "-fopenmp" flag. To fix this issue, we normally install either ''llvm'' or ''g++'' using homebrew. This normally results in the compiler being installed in a path that looks something like ''/opt/homebrew/Cellar/llvm/<version>/bin/clang++'' or ''/opt/homebrew/Cellar/gcc/<version>/bin/g++-<version>''. Set the environment variable ''CXX'' to the absolute path name of this C++ compiler before running "./build". | ==== MacOS ==== |
| | |
| | Recent versions of MacOS have a C++ compiler issue, namely that the default compiler distributed by Apple does not support the "-fopenmp" flag. To fix this issue, we normally install either ''llvm'' or ''g++'' using homebrew. This normally results in the compiler being installed in a path that looks something like ''/opt/homebrew/Cellar/llvm/<version>/bin/clang++'' or ''/opt/homebrew/Cellar/gcc/<version>/bin/g++-<version>''. Set the environment variable ''CXX'' to the absolute path name of this C++ compiler before running "./build". |
| | |
| | More recent versions of LLVM have problems with linking. If you see messages like this: |
| | <code> |
| | Undefined symbols for architecture arm64: |
| | "std::__1::__hash_memory(void const*, unsigned long)", referenced from: |
| | ... |
| | </code> |
| | then chances are you have a known issue in recent LLVM versions on MacOS ([[https://github.com/llvm/llvm-project/issues/155606|github issue]]). The workaround that fixes this at least for the actflow build (see the discussion for details, this may not necessarily be a proper fix) is to edit the ''.cfg'' file installed with LLVM to include |
| | the location of the LLVM C++ standard library. The [[https://github.com/llvm/llvm-project/issues/155606|github issue]] has details and various workarounds, and the root cause appears to be that while the LLVM compiler uses a specific algorithm to find include paths, it uses a different one to find libraries; so the system C++ standard library is being used instead of the LLVM-provided C++ standard library. Explicitly including the LLVM-provided library fixes this issue in the build. |
| | |
| | For example, on a recent MacOS/homebrew setup, this required editing ''.cfg'' files in ''/opt/homebrew/etc/clang/'', replacing the line ''-i sysroot /Library/Developer/CommandLineTools/SDKs/MacOSX26.sdk'' with |
| | ''/opt/homebrew/opt/llvm/lib/c++/libc++.1.0.dylib -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX26.sdk'' (see the github issue for details). |
| |
| === OpenMP message === | ==== OpenMP message ==== |
| |
| You may see the following message: | You may see the following message: |
| A modern install of g++ or clang++ can compile this program when given the ''-fopenmp'' option. | A modern install of g++ or clang++ can compile this program when given the ''-fopenmp'' option. |
| |
| === Filesystem message === | ==== Filesystem message ==== |
| |
| You may see the following message: | You may see the following message: |