<pre style='margin:0'>
Ryan Schmidt (ryandesign) pushed a commit to branch master
in repository macports-ports.
</pre>
<p><a href="https://github.com/macports/macports-ports/commit/4a8a85dbab92da5a3621c5d89970ec681ff8f232">https://github.com/macports/macports-ports/commit/4a8a85dbab92da5a3621c5d89970ec681ff8f232</a></p>
<pre style="white-space: pre; background: #F8F8F8">The following commit(s) were added to refs/heads/master by this push:
<span style='display:block; white-space:pre;color:#404040;'> new 4a8a85d cryptlib: Fix comment and remove commented-out code
</span>4a8a85d is described below
<span style='display:block; white-space:pre;color:#808000;'>commit 4a8a85dbab92da5a3621c5d89970ec681ff8f232
</span>Author: Ryan Schmidt <ryandesign@macports.org>
AuthorDate: Wed Mar 28 11:57:42 2018 -0500
<span style='display:block; white-space:pre;color:#404040;'> cryptlib: Fix comment and remove commented-out code
</span>---
devel/cryptlib/Portfile | 6 +-----
1 file changed, 1 insertion(+), 5 deletions(-)
<span style='display:block; white-space:pre;color:#808080;'>diff --git a/devel/cryptlib/Portfile b/devel/cryptlib/Portfile
</span><span style='display:block; white-space:pre;color:#808080;'>index 4955b28..76be9f2 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/devel/cryptlib/Portfile
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/devel/cryptlib/Portfile
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -5,7 +5,7 @@ PortGroup conflicts_build 1.0
</span>
# Quoth the makefile: "[Multiple-architecture building] is rather trouble-prone
# because the low-level crypto code has to configure itself for CPU endianness
<span style='display:block; white-space:pre;background:#ffe0e0;'>-# and word size 5975092or the algorithms that require low-level bit fiddling, and
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+# and word size for the algorithms that require low-level bit fiddling, and
</span> # uses different code strategies depending on the CPU architecture and bit
# width. This single-pass build for multiple architectures often causes
# problems, and you're more or less on your own if you decide to try it."
<span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -64,10 +64,6 @@ build.args CC="${configure.cc}" \
</span> configure.cppflags-replace -I${prefix}/include -isystem${prefix}/include
foreach arch ${universal_archs} {
<span style='display:block; white-space:pre;background:#ffe0e0;'>-# set archflag "-arch ${arch}"
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-# lappend merger_build_env(${arch}) \
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-# CFLAGS=[list {*}${configure.cflags} {*}${configure.cppflags} {*}${archflag}] \
</span><span style='display:block; white-space:pre;background:#ffe0e0;'>-# LDFLAGS=[list {*}${configure.ldflags} {*}${archflag}]
</span> lappend merger_build_env(${arch}) \
CFLAGS="${configure.cflags} ${configure.cppflags} -arch ${arch}" \
LDFLAGS="${configure.ldflags} -arch ${arch}"
</pre><pre style='margin:0'>
</pre>