I don't think anything ever used `$o'. This project didn't use `$t'.
And use of `$e' gets in the way of Automake's magic handling of
executable suffixes under Cygwin.
if !CROSS_COMPILING
$(precomp)/crc32-tab.c:
@$(mkdir_p) $(precomp)
- @$(MAKE) crc-mktab$e
+ @$(MAKE) crc-mktab$(EXEEXT)
$(AM_V_GEN)./crc-mktab -o $@.new \
-p0x04c11db7 -b32 -B8 -r -c \
-scrc32_table -icrc32.h -tuint32 && \
if !CROSS_COMPILING
$(precomp)/unihash-global.c:
@$(mkdir_p) $(precomp)
- @$(MAKE) unihash-mkstatic$e
+ @$(MAKE) unihash-mkstatic$(EXEEXT)
$(AM_V_GEN)./unihash-mkstatic -c -sunihash_global -iunihash.h \
-o$@.new && mv $@.new $@
endif
###--------------------------------------------------------------------------
### Miscellaneous useful definitions.
-## Some convenient abbreviations for file suffixes.
-e = $(EXEEXT)
-o = $(OBJEXT)
-t = t$e
-
## Installation directories.
pkglibexecdir = $(libexecdir)/$(PACKAGE)