Re: Multiple pointers to /usr/lib/epics

[Ralph Lange via Tech-talk <tech-talk at aps.anl.gov>]

On Tue, 22 Nov 2022 at 22:33, Daykin, Evan via Tech-talk <tech-talk at aps.anl.gov> wrote: 

After upgrading to EPICS 7, we now get the following warning(s) when building packages with multiple dependencies:

>/usr/lib/epics/configure/RULES_BUILD:601: Warning: Base configure/RULES_BUILD file included more than once. Does configure/RELEASE have multiple pointers to /usr/lib/epics?

Our convention is as Mark describes here: https://epics.anl.gov/tech-talk/2021/msg00813.php . Our add-ons are essentially all installed into a flat /usr/lib/epics directory, and our experience is the same as Mark described – as long as any miscellaneous package that is _not_ in /usr/lib/epics is defined before anything that _is_ in /usr/lib/epics, everything works fine. Now that we are getting these warnings, can they be ignored, or is this convention broken/otherwise disfavored in EPICS 7?

Such "flat" installations are fine and supported.

The check for double inclusion is relatively new. It emits a warning, as it doesn't know if the double inclusion is due to a bug or happens because you have multiple modules in a flat installation.

In the latter case, you can safely ignore the warning.

To avoid it, you can try to not define a module in the RELEASE file at all (will work for most modules). If the module or your application use things like 'ífdef $SNCSEQ' in Make rules, not defining it would break and you can try defining it as a string that is not a location, e.g., 'SNCSEQ=installed'.

Cheers,
~Ralph