Re: [gentoo-user] "xyz.la seems to be moved" message

["Vladimir G. Ivanovic" <vgivanovic@comcast.net>]

On Tue, 2006-10-24 at 11:24 -0500, Michael Sullivan wrote:
> On Tue, 2006-10-24 at 17:31 +0200, Fabrice Delliaux wrote:
> > Hi,
> > 
> > Explanation && patch here :
> > 
> > http://www.mail-archive.com/bug-libtool@gnu.org/msg00838.html
> 
> I saved the patch at the above link to /root/libtool.patch, but I can't
> figure out how to use it.  

Here's what I did:

     1. cd /usr/portage/sys-devel/libtool/files/
     2. mkdir 1.5.22
     3. cd 1.5.22
     4. Create "libtool-1.5.22-ltmain.sh-seems-to-be-moved.patch"
with contents: 

--- libtool-1.5.22/ltmain.in.~1~     2006-10-24 12:54:00.000000000 -0700
+++ libtool-1.5.22/ltmain.in    2006-10-24 12:55:16.000000000 -0700
@@ -2920,7 +2920,11 @@
                    exit $EXIT_FAILURE
                  fi
                  if test "$absdir" != "$libdir"; then
-                   $echo "$modename: warning: \`$deplib' seems to be
moved" 1>&2
+                     absdir2=`cd "$absdir" && pwd || echo "$absdir"`
+                     libdir2=`cd "$libdir" && pwd || echo "$libdir"`
+                     if test "$absdir2" != "$libdir2"; then
+                         $echo "$modename: warning: \`$deplib' seems to
be moved from \`$libdir' to \`$absdir'" 1>&2
+                     fi
                  fi
                  path="$absdir"
                fi

  5. cd ..
  6. Apply the following patch:

--- libtool-1.5.22.ebuild.~1~   2006-10-17 03:06:30.000000000 -0700
+++ libtool-1.5.22.ebuild       2006-10-24 11:57:18.000000000 -0700
@@ -83,6 +83,10 @@
        # <azarah@gentoo.org> - (11 Feb 2004)
        epatch
"${FILESDIR}"/1.5.20/${PN}-1.5.20-ltmain_sh-max_cmd_len.patch
 
+       # Get rid of false positive "seems to be moved" messages.
+       # http://www.mail-archive.com/bug-libtool@gnu.org/msg00838.html
+       epatch
"${FILESDIR}"/1.5.22/libtool-1.5.22-ltmain.sh-seems-to-be-moved.patch
+
        # Libtool's autoguessing at tag's sucks ... it get's confused 
        # if the tag's CC says '<CHOST>-gcc' and the env CC says 'gcc'
        # or vice versa ... newer automakes specify the tag so no

  7. ebuild libtool-1.5.22.ebuild digest
  8. emerge -av --with-bdeps y =libtool-1.5.22

--- Vladimir

-- 
Vladimir G. Ivanovic <vgivanovic@comcast.net>

-- 
gentoo-user@gentoo.org mailing list