Comment # 3 on bug 1204587 from David Mair

During building crash extension modules, the *.c source files in the
extensions/ directory are used as a dictionary (entries being the source
filenames before the dot, <fname>) of libraries to be created using make rules
with the simplified effect:

all: link_defs <fname>.so

link_defs:
    @rm -f defs.h
    @ln ../defs.h 

<fname>.so: <fname>.c defs.h

It's assumed the failing make rules are run in the extensions/ sub-directory of
the crash package source because they correctly use dminfo as an example
<fname> based on the presence of dminfo.c and the rule to make dminfo.so fails.

In that case, (the crash source root, ..) the parent directory of where the
above is made has a file named defs.h in it (in spite of the above rules and
the failure error).

Tumbleweed ln binary still supports it's use with a single target (to be
hard-linked in the current directory).

defs.h is part of the crash package source and in the parent directory of the
one the above make rules are assumed to be run in.

Build failure reports a <fname>.so make rule can't be executed, <fname>.so is
dependent on defs.h which doesn't exist (in spite of the above rules).

On Monday I'll diagnose the operation and effect of link_defs: in the
extensions/ Makefile.