Hi, On Mon, Jun 22, 2020 at 11:28:16AM -0700, James Bottomley wrote: > That will be my fault. I assumed automake always ran with gnu make,
No :-) (and let's not start a gnu make vs bsd make vs. cmake vs. ant
discussion now :-) ).
Specifically, we run automake on linux systems before doing release
tarballs, so the target host doesn't even *need* automake installed -
but if you want, automake runs just fine on BSD, producing "standard
makefiles" that work fine with BSD make.
> so the .cnf rule is in gnu make syntax at the bottom of (Makefile.am):
>
> $(builddir)/%.cnf: $(srcdir)/%.cnf.in
> sed "s|ABSBUILDDIR|$(abs_builddir)|" < $< > $@
>
>
> If I just spell everything out and don't use the percent wildcard, it
> should work even on legacy make.
Ah, there it is :) - I think "non-GNU" make doesn't handle these in
combination with paths.
"man make" on FreeBSD says:
The $@ and $< variables are more or less universally portable, as is the
$(MAKE) variable. Basic use of suffix rules (for files only in the
current directory, not trying to chain transformations together, etc.) is
also reasonably portable.
so
$(builddir)/openvpn.cnf: $(srcdir)/openvpn.cnf.in
sed "s|ABSBUILDDIR|$(abs_builddir)|" < $< > $@
should work.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
signature.asc
Description: PGP signature
_______________________________________________ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
