ekhtml: Always autoreconf; fixes build failure with SDK

When the port was originally added, autoreconf was only used when the
universal variant was selected. Perhaps this was done because it was
assumed that an SDK would only be used when building universal. An SDK
can be used for any build, not just universal builds, so we should
always autoreconf.

Also modernize checksums.

textproc/ekhtml/Portfile

@@ -4,6 +4,10 @@ PortSystem      1.0
 
 name            ekhtml
 version         0.3.2
+checksums       rmd160  8e5d664821d181e12f0fc6d24d1a288f432cc2b5 \
+                sha256  1ed1f0166cd56552253cd67abcfa51728ff6b88f39bab742dbf894b2974dc8d6 \
+                size    234917
+
 license         BSD
 categories      textproc devel
 platforms       darwin
@@ -16,17 +20,11 @@ long_description \
 homepage        http://ekhtml.sourceforge.net/
 master_sites    sourceforge:project/ekhtml/ekhtml/${version}
 
-checksums       md5     cc9d2e4adaccacfacefddbd75ccccfdf \
-                sha1    d4e6c25964f7e110073f646950dc307e84d61f1b \
-                rmd160  8e5d664821d181e12f0fc6d24d1a288f432cc2b5
-
 patchfiles      patch-automake-1.13.diff
 
-if {[variant_isset universal]} {
-    use_autoreconf yes
-} else {
-    configure.ccache no
-}
+# Fix build error "clang: error: unknown argument: '-syslibroot'" when
+# a macOS SDK is used.
+use_autoreconf  yes
 
 use_parallel_build no