However, on this pass COMMON_DIR is also not yet defined, so we are saying that build depends on /devEpics.dbd, which of course there is no rule to create.
A few comments:
I'm not sure this is an asyn issue per se; this is definitely about the interaction between asyn's (custom) build rules and EPICS base.
The build instructions for asyn explicitly say that you should run make and not make build, so technically I am not following the instructions. However, for EPICS base make and make build do the same thing; moreover, make build is not an unreasonable command to try to run, and it is surprising that it fails while make or even make install succeed.
If you do the following:
make build
in asyn after configuring it to point at EPICS basethen you will have a failed build failing with
The reason appears to be the following code from asyn/Makefile (https://github.com/epics-modules/asyn/blob/master/asyn/Makefile#L340):
From what I can see, the issue is that on the first pass through in EPICS base (https://github.com/epics-base/epics-base/blob/7.0/configure/RULES)
T_A
is not defined which means we do not defineDBDCAT_COMMAND
(fromRULES.Db
), which adds the dependencyHowever, on this pass
COMMON_DIR
is also not yet defined, so we are saying thatbuild
depends on/devEpics.dbd
, which of course there is no rule to create.A few comments:
asyn
explicitly say that you should runmake
and notmake build
, so technically I am not following the instructions. However, for EPICS basemake
andmake build
do the same thing; moreover,make build
is not an unreasonable command to try to run, and it is surprising that it fails whilemake
or evenmake install
succeed.