<pre style='margin:0'>
Ken (kencu) pushed a commit to branch master
in repository macports-ports.

</pre>
<p><a href="https://github.com/macports/macports-ports/commit/7bded6b45234445ad5cc49a5f56b404ef3d8a38d">https://github.com/macports/macports-ports/commit/7bded6b45234445ad5cc49a5f56b404ef3d8a38d</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 7bded6b4523 legacysupport 1.1 PG: use tranditional libname
</span>7bded6b4523 is described below

<span style='display:block; white-space:pre;color:#808000;'>commit 7bded6b45234445ad5cc49a5f56b404ef3d8a38d
</span>Author: Ken Cunningham <kencu@macports.org>
AuthorDate: Sun Oct 18 11:59:17 2020 -0700

<span style='display:block; white-space:pre;color:#404040;'>    legacysupport 1.1 PG: use tranditional libname
</span><span style='display:block; white-space:pre;color:#404040;'>    
</span><span style='display:block; white-space:pre;color:#404040;'>    it turns out that libtool does not pass along
</span><span style='display:block; white-space:pre;color:#404040;'>    dylibs for linking when the name is a full-specified
</span><span style='display:block; white-space:pre;color:#404040;'>    pathname.
</span><span style='display:block; white-space:pre;color:#404040;'>    
</span><span style='display:block; white-space:pre;color:#404040;'>    However, libtool does pass along static libs for linking
</span><span style='display:block; white-space:pre;color:#404040;'>    when the name is a fully-specified pathname.
</span><span style='display:block; white-space:pre;color:#404040;'>    
</span><span style='display:block; white-space:pre;color:#404040;'>    the changes the dylib name back to the traditional one
</span><span style='display:block; white-space:pre;color:#404040;'>    that works, and has been used for some years in legacysupport 1.0.
</span><span style='display:block; white-space:pre;color:#404040;'>    
</span><span style='display:block; white-space:pre;color:#404040;'>    Hopefully this is the simplest, least-invasive, and most tested
</span><span style='display:block; white-space:pre;color:#404040;'>    method of restoring the proper link behaviour when using
</span><span style='display:block; white-space:pre;color:#404040;'>    legacysupport and libtool.
</span><span style='display:block; white-space:pre;color:#404040;'>    
</span><span style='display:block; white-space:pre;color:#404040;'>    see: https://trac.macports.org/ticket/60798
</span>---
 _resources/port1.0/group/legacysupport-1.1.tcl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

<span style='display:block; white-space:pre;color:#808080;'>diff --git a/_resources/port1.0/group/legacysupport-1.1.tcl b/_resources/port1.0/group/legacysupport-1.1.tcl
</span><span style='display:block; white-space:pre;color:#808080;'>index 0c1a6c54bd8..3284dd7d4e8 100644
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>--- a/_resources/port1.0/group/legacysupport-1.1.tcl
</span><span style='display:block; white-space:pre;background:#e0e0ff;'>+++ b/_resources/port1.0/group/legacysupport-1.1.tcl
</span><span style='display:block; white-space:pre;background:#e0e0e0;'>@@ -50,7 +50,7 @@ proc legacysupport::get_library_name {} {
</span>     if {[option legacysupport.use_static]} {
         return ${prefix}/lib/libMacportsLegacySupport.a
     } else {
<span style='display:block; white-space:pre;background:#ffe0e0;'>-        return ${prefix}/lib/libMacportsLegacySupport.dylib
</span><span style='display:block; white-space:pre;background:#e0ffe0;'>+        return -lMacportsLegacySupport
</span>     }
 }
 
</pre><pre style='margin:0'>

</pre>