libtool
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[zzSPAM] Javascript Junkmail-Notify (Javascript(pain meds))


From: zzHQMAIL1
Subject: [zzSPAM] Javascript Junkmail-Notify (Javascript(pain meds))
Date: Thu, 29 Apr 2004 11:02:33 -0700

************* eManager Notification **************

Javascript Junkmail Notify

Source mailbox: "address@hidden"
Destination mailbox(es): "address@hidden"
Policy: Javascript(pain meds)
Action: Delete

******************* End of message *******************
--- Begin Message --- Subject: Libtool Digest, Vol 17, Issue 20
Send Libtool mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        http://mail.gnu.org/mailman/listinfo/libtool
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Libtool digest..."


Today's Topics:

   1. Re: Problem with /.libs/.libs/ during link (Peter O'Gorman)
   2. Re: Do autotools support free Microsoft compiler?
      (Braden McDaniel)
   3. make your man bigger for for the New Year (Susanne Romero)
   4. Re: Problem with /.libs/.libs/ during link (Dan S. Camper)
   5. Re: Problem with /.libs/.libs/ during link (Peter O'Gorman)
   6. Re: Problem with /.libs/.libs/ during link (Peter O'Gorman)
   7. Re: Problem with /.libs/.libs/ during link (Dan S. Camper)
   8. (no subject) (Iurie Jigalov)
   9. Strong Pain meds (Tamra Kent)
  10. prefix restrictions (Steven F. Killen)
  11. prefix restrictions (Steven F. Killen)


----------------------------------------------------------------------

Message: 1
Date: Thu, 29 Apr 2004 08:48:59 +0900
From: Peter O'Gorman <address@hidden>
Subject: Re: Problem with /.libs/.libs/ during link
To: "Dan S. Camper" <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii; format=flowed

Dan S. Camper wrote:

> 
> Oh yes:  The libtool I'm using is:
> 
> #: ./libtool --version
> ltmain.sh (GNU libtool) 1.5 (1.1220 2003/04/05 19:32:58)
> 
> Thoughts?

Libtool-1.5.6 may fix this problem, please try it.

Peter
-- 
Peter O'Gorman - http://www.pogma.com




------------------------------

Message: 2
Date: Wed, 28 Apr 2004 20:01:39 -0400
From: Braden McDaniel <address@hidden>
Subject: Re: Do autotools support free Microsoft compiler?
To: address@hidden
Cc: address@hidden, address@hidden, address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii; format=flowed

Paul Eggert wrote:

> Braden McDaniel <address@hidden> writes:
> 
> 
>>autoconf, basically. autoconf's check for whether it can use -g is
>>busted, but the effect of this is just a benign warning from the
>>compiler. (I have a patch for this that I submitted to
>>autoconf-patches many months ago; but it was ignored.)
> 
> 
> Sorry, I dropped the ball on that.  I didn't like your patch, but
> didn't have time to compose a better one at the time.  I just took the
> time, installed the following patch instead.  Please try CVS Autoconf
> on your compiler installation to see whether this approach works for
> you.

Thanks for following up on this.

Unfortunately I haven't been able to test this yet. CVS autoconf now 
appears to want "help2man", which I have not yet succeeded in 
building/installing on Cygwin. (The attempt sent me on quite a wild 
goose chase, though: help2man wants perl Locale::gettext wants fresher 
gettext (than Cygwin packages) wants a C# compiler (!...fortunately this 
dependency could be disabled).)

Braden





------------------------------

Message: 3
Date: Thu, 29 Apr 2004 05:47:56 +0000
From: "Susanne Romero" <address@hidden>
Subject: make your man bigger for for the New Year
To: address@hidden, address@hidden, address@hidden,
        address@hidden, address@hidden, address@hidden
Message-ID:
        <address@hidden>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL: 
http://mail.gnu.org/pipermail/libtool/attachments/20040429/f1528860/attachment.html

------------------------------

Message: 4
Date: Thu, 29 Apr 2004 07:47:43 -0500
From: "Dan S. Camper" <address@hidden>
Subject: Re: Problem with /.libs/.libs/ during link
To: "Peter O'Gorman" <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="US-ASCII"

In our last episode, on 4/28/04 6:48 PM, Peter O'Gorman (address@hidden)
said something like:

> Dan S. Camper wrote:
> 
>> 
>> Oh yes:  The libtool I'm using is:
>> 
>> #: ./libtool --version
>> ltmain.sh (GNU libtool) 1.5 (1.1220 2003/04/05 19:32:58)
>> 
>> Thoughts?
> 
> Libtool-1.5.6 may fix this problem, please try it.
> 
> Peter

I just updated one of my systems to libtool 1.5.6, ran libtoolize to ensure
that the support files in my conftools/ subdirectory were updated, then
executed autoheader, autoconf, 'make distclean' and ./configure to bring
everything back to square one.  Unfortunately, the problem still exists (and
is identical).

This problem of /.libs/.libs/ showing up on the link line seems to date back
to 2000, at least according to Google.  In many cases it was dismissed as
someone adding -L./.libs or something to the link command, or otherwise
manually futzing with the libtool commands.  I'm not doing that here.

I tried looking through the libtool script and, frankly, I needed to lay
down afterwards.  That made my head hurt.

DSC

_________________________________________________________________________
Dan S. Camper                                         Borrowed Time, Inc.
Software Thaumaturge                                   http://www.bti.net






------------------------------

Message: 5
Date: Thu, 29 Apr 2004 23:02:51 +0900
From: Peter O'Gorman <address@hidden>
Subject: Re: Problem with /.libs/.libs/ during link
To: "Dan S. Camper" <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"

Dan S. Camper wrote:

> I just updated one of my systems to libtool 1.5.6, ran libtoolize to ensure
> that the support files in my conftools/ subdirectory were updated, then
> executed autoheader, autoconf, 'make distclean' and ./configure to bring
> everything back to square one.  Unfortunately, the problem still exists (and
> is identical).
> 
> This problem of /.libs/.libs/ showing up on the link line seems to date back
> to 2000, at least according to Google.  In many cases it was dismissed as
> someone adding -L./.libs or something to the link command, or otherwise
> manually futzing with the libtool commands.  I'm not doing that here.
> 
> I tried looking through the libtool script and, frankly, I needed to lay
> down afterwards.  That made my head hurt.

Dammit, looks like I only fixed it in HEAD, not branch-1-5. :(

Looking for the patch now.... this looks like the relevant bit. Can you 
please apply it and confirm a fix, thanks.

Peter
-- 
Peter O'Gorman - http://www.pogma.com
-------------- next part --------------
Index: ltmain.in
===================================================================
RCS file: /cvsroot/libtool/libtool/ltmain.in,v
retrieving revision 1.334.2.32
diff -u -3 -p -u -r1.334.2.32 ltmain.in
--- ltmain.in   1 Apr 2004 04:34:22 -0000       1.334.2.32
+++ ltmain.in   29 Apr 2004 14:00:16 -0000
@@ -2151,10 +2151,17 @@ EOF
            absdir="$libdir"
          fi
        else
-         dir="$ladir/$objdir"
-         absdir="$abs_ladir/$objdir"
-         # Remove this search path later
-         notinst_path="$notinst_path $abs_ladir"
+         if test ! -f "$ladir/$objdir/$linklib" && test -f 
"$abs_ladir/$linklib"; then
+           dir="$ladir"
+           absdir="$abs_ladir"
+           # Remove this search path later
+           notinst_path="$notinst_path $abs_ladir"
+         else
+           dir="$ladir/$objdir"
+           absdir="$abs_ladir/$objdir"
+           # Remove this search path later
+           notinst_path="$notinst_path $abs_ladir"
+         fi
        fi # $installed = yes
        name=`$echo "X$laname" | $Xsed -e 's/\.la$//' -e 's/^lib//'`
 

------------------------------

Message: 6
Date: Thu, 29 Apr 2004 23:43:13 +0900
From: Peter O'Gorman <address@hidden>
Subject: Re: Problem with /.libs/.libs/ during link
To: "Dan S. Camper" <address@hidden>
Cc: address@hidden, Libtool Patches <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"

Dan S. Camper wrote:

> 
> Thank you VERY much for the prompt and -- better yet -- working fix!
> 

Thank you.

Note, I just applied the attached patch to branch-1-5.

Peter
-- 
Peter O'Gorman - http://www.pogma.com
-------------- next part --------------
Index: ChangeLog
2004-04-29  Peter O'Gorman  <address@hidden>

        * ltmain.in: Fix problem with .libs/.libs/libfoo.so appearing on
        the link line, reported and fix confirmed by Dan S. Camper.

from  Gary V. Vaughan  <address@hidden>
Index: ltmain.in
===================================================================
RCS file: /cvsroot/libtool/libtool/ltmain.in,v
retrieving revision 1.334.2.32
diff -u -3 -p -u -r1.334.2.32 ltmain.in
--- ltmain.in 1 Apr 2004 04:34:22 -0000 1.334.2.32
+++ ltmain.in 29 Apr 2004 14:39:36 -0000
@@ -2151,10 +2151,17 @@ EOF
            absdir="$libdir"
          fi
        else
-         dir="$ladir/$objdir"
-         absdir="$abs_ladir/$objdir"
-         # Remove this search path later
-         notinst_path="$notinst_path $abs_ladir"
+         if test ! -f "$ladir/$objdir/$linklib" && test -f 
"$abs_ladir/$linklib"; then
+           dir="$ladir"
+           absdir="$abs_ladir"
+           # Remove this search path later
+           notinst_path="$notinst_path $abs_ladir"
+         else
+           dir="$ladir/$objdir"
+           absdir="$abs_ladir/$objdir"
+           # Remove this search path later
+           notinst_path="$notinst_path $abs_ladir"
+         fi
        fi # $installed = yes
        name=`$echo "X$laname" | $Xsed -e 's/\.la$//' -e 's/^lib//'`
 

------------------------------

Message: 7
Date: Thu, 29 Apr 2004 09:26:57 -0500
From: "Dan S. Camper" <address@hidden>
Subject: Re: Problem with /.libs/.libs/ during link
To: "Peter O'Gorman" <address@hidden>
Cc: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="US-ASCII"

In our last episode, on 4/29/04 9:02 AM, Peter O'Gorman (address@hidden)
said something like:

> Dammit, looks like I only fixed it in HEAD, not branch-1-5. :(
> 
> Looking for the patch now.... this looks like the relevant bit. Can you
> please apply it and confirm a fix, thanks.
> 
> Peter
> -- 
> Peter O'Gorman - http://www.pogma.com

<patch snipped>

Bingo!  The patch did the trick.

Thank you VERY much for the prompt and -- better yet -- working fix!

DSC

_________________________________________________________________________
Dan S. Camper                                         Borrowed Time, Inc.
Software Thaumaturge                                   http://www.bti.net






------------------------------

Message: 8
Date: Thu, 29 Apr 2004 11:42:14 -0400
From: "Iurie Jigalov" <address@hidden>
Subject: (no subject)
To: <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset="iso-8859-1"

Hi, guys, 

sorry for probably stupid question but I can nor  find problem myself.
I have windows DLL file compiled using  msvc++  I need to convert into
Linux library (ELF) that could be used by Oracle on Linux as external library.
As I understood I need to use dlltool - by how to compile it on Linux or 
I can use something different.  Any advise will be greatly appreciated.

Thanks

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
http://mail.gnu.org/pipermail/libtool/attachments/20040429/2d3eb348/attachment.htm

------------------------------

Message: 9
Date: Thu, 29 Apr 2004 18:01:55 +0000
From: "Tamra Kent" <address@hidden>
Subject: Strong Pain meds
To: address@hidden
Message-ID: <address@hidden>
Content-Type: text/plain; charset="us-ascii"

An HTML attachment was scrubbed...
URL: 
http://mail.gnu.org/pipermail/libtool/attachments/20040429/dbdd3a1a/attachment.html

------------------------------

Message: 10
Date: Thu, 29 Apr 2004 12:33:38 -0400 (EDT)
From: "Steven F. Killen" <address@hidden>
Subject: prefix restrictions
To: address@hidden
Message-ID:
        <address@hidden>
Content-Type: TEXT/PLAIN; charset=US-ASCII

Greetings,

I'm attempting to install Gaim 0.77, which is built with
autoconf/automake.  It builds fine, but I'm having trouble with gmake
install and libtool in particular.

The version distributed with gaim is 1.4.3, but I have 1.5.2 installed
locally on the system as well.  The behavior is exhibited when either is
used.

I've run ./configure and accepted the default prefix, /usr/local, because
that is where the program will be running out of.  However, gmake install
prefix=/tmp/gaim fails.  The specific error is:

libtool: install: error: cannot install `gaim-remote.la' to a directory
not ending in /usr/local/lib/gaim

Two caveats:

1) the prefix needs to be /usr/local to the program's eye,
because that is where it will run out of.  It will actually be installed
to another directory (on afs) and then symlinked in to /usr/local for
sitewide distribution purposes.

2) It can't install to /usr/local, because that's a read-only volume.

Is there a way to tell libtool to ignore the prefix for installation
purposes, or must I copy each file by hand to the directory I wish to
move the files to?  Is there something I'm missing about how libtool
operates?

--
Steve Killen <address@hidden>




------------------------------

Message: 11
Date: Thu, 29 Apr 2004 12:10:09 -0400 (EDT)
From: "Steven F. Killen" <address@hidden>
Subject: prefix restrictions
To: address@hidden
Message-ID:
        <address@hidden>
Content-Type: TEXT/PLAIN; charset=US-ASCII



--
Steve Killen <address@hidden>




------------------------------

_______________________________________________
Libtool mailing list
address@hidden
http://mail.gnu.org/mailman/listinfo/libtool


End of Libtool Digest, Vol 17, Issue 20
***************************************

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]