|
From: | Marco Sirabella |
Subject: | configure's --without flags do the opposite |
Date: | Sun, 12 Dec 2021 21:49:38 -0800 |
Hello,
I’m taking another stab at packaging gnu-apl for my personal gentoo overlay, and I’m running into this funny build behaviour:
apl-1.8$ ./configure --without-erlang
...
checking if we want to build an erlang interface (implies libapl.so)... yes
...
apl-1.8$ make
...
Making all in erlang
make[2]: Entering directory '/tmp/tmp.jRec7xMUbt/apl-1.8/erlang'
erlc apl.erl
make[2]: erlc: No such file or directory
I can reproduce this with most of the optional feature flags, --without-
doing the same as --with
.
Digging into the code, it looks like AC_ARG_WITH
’s action is action-if-present
, whether --with
or --without
. You would have to do some checking with $withval
to actually know what was passed.
Alternatively, you could just use $with_erlang
/ $without_erlang
, but that is a more substantial change.
I’m willing to write up a patch, just want to gauge interest/how this all is expected to work.
– Marco Sirabella
signature.asc
Description: PGP signature
[Prev in Thread] | Current Thread | [Next in Thread] |