> On Oct 29, 2014, at 10:38 AM, Daniel J. Luke <dl...@geeklair.net> wrote:
> I've added a small configure patch to MacPorts to work around this for now - 
> I imagine if the next subversion release uses the current (or newer) libtool, 
> then the patch won't be necessary anymore:
> 
> --- configure.orig    2014-10-29 10:20:21.000000000 -0400
> +++ configure 2014-10-29 10:22:43.000000000 -0400
> @@ -10348,7 +10348,7 @@
>       case ${MACOSX_DEPLOYMENT_TARGET-10.0},$host in
>       10.0,*86*-darwin8*|10.0,*-darwin[91]*)
>         _lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
> -     10.[012]*)
> +     10.[[012]][[,.]]*)
>         _lt_dar_allow_undefined='${wl}-flat_namespace ${wl}-undefined 
> ${wl}suppress' ;;
>       10.*)
>         _lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
and it turns out I used the m4 template patch as the basis for this, so it has 
double square brackets when it shouldn't here's a better one that hopefully 
won't break 10.0-10.2 (not that anyone should be running them):

--- configure.orig      2014-10-29 10:20:21.000000000 -0400
+++ configure   2014-10-29 10:22:43.000000000 -0400
@@ -10348,7 +10348,7 @@
       case ${MACOSX_DEPLOYMENT_TARGET-10.0},$host in
        10.0,*86*-darwin8*|10.0,*-darwin[91]*)
          _lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;
-       10.[012]*)
+       10.[012][,.]*)
          _lt_dar_allow_undefined='${wl}-flat_namespace ${wl}-undefined 
${wl}suppress' ;;
        10.*)
          _lt_dar_allow_undefined='${wl}-undefined ${wl}dynamic_lookup' ;;

--
Daniel J. Luke                                                                  
 
+========================================================+                      
  
| *---------------- dl...@geeklair.net ----------------* |                      
    
| *-------------- http://www.geeklair.net -------------* |                      
    
+========================================================+                      
  
|   Opinions expressed are mine and do not necessarily   |                      
    
|          reflect the opinions of my employer.          |                      
    
+========================================================+




Reply via email to