AX_BOOST_BASE and nix
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 32/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- build-system
Research direction
Start by reproducing the reported ./configure failure in the Nix source tree under MSYS2, focusing on the AX_BOOST_BASE call at configure line 5590 and the installed Boost package. Read the linked Nix build-from-source instructions and the MSYS2 setup commands; done means identifying whether the failure is caused by the environment or the build configuration and recording a reproducible resolution.
Written by the indexing model from the issue text.
Description
Hi,
A few days ago I discovered msys2 and I am very pleased with the state of things overall.
My ultimate goal is to build nix from source inside msys2 on Windows 10.
Having nix on Windows would be a cornucopia, because it is very powerful build system.
I don't see potential in WSL, because it is just VirtualBox. It is not working if Windows inside VBox on Linux!
nix has lots of dependencies.
Some of them are already provided by msys2 through pacman.
My setup:
$ pacman -Syu
$ pacman -Su
$ pacman -S --needed base-devel mingw-w64-x86_64-toolchain
$ pacman -S pkg-config
$ pacman -S mingw-w64-x86_64-jq
$ pacman -S mingw-w64-x86_64-boost
$ git clone https://github.com/NixOS/nix
$ cd nix
$ ./configure
...
checking for lsof... lsof
checking for jq... /mingw64/bin/jq
./configure: line 5590: syntax error near unexpected token1.66,' ./configure: line 5590:AX_BOOST_BASE(1.66, CXXFLAGS="$BOOST_CPPFLAGS $CXXFLAGS", AC_MSG_ERROR([Nix requires boost.]))'
I started reading autoconf and automake articles, but as for now the error message looks pretty cryptic to me and makes me think, that this is a parser error in m4.
Any hint would be helpful.
- Dominant language
- CSS
- Stars
- 3.3k
- Forks
- 446
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 1
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from msys2/msys2.github.io
-
Mirror RegistrationOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
msys2/msys2.github.io#445 · 8 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
msys2/msys2.github.io#439 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
msys2/msys2.github.io#426 · 8 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
msys2/msys2.github.io#419 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
msys2/msys2.github.io#411 ·
All issues in msys2/msys2.github.io
Similar issues
-
bot-found bug priority: P3
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
madenvel/KalinkaPlayer#179 ·
-
cuAmpcorParameter.cpp (CPU pycuampcor) does not compile with libc++: EXIT_FAILURE is undeclaredOpen
Difficulty 1/5 Under an hour Newbie friendliness 92/100
isce-framework/isce3#387 ·
-
agent-research-recommend agent-review-finding enhancement ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jordansmall/spindrift#3965 · 1 comment ·
Maintainers usually reply within 2 days
-
upstream update
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
conan-io/conan-center-index#31055 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day