On Mar 07, 2005, at 19:26, Peter O'Gorman wrote:
D.Walsh wrote:
Peter, are you trying to tell me that the "libtool" supplied and
installed in Mac OSX is not the "GNU libtool"?
Yes, I am, in a way. Apple ships GNU libtool as /usr/bin/glibtool, and
has a completely different program as /usr/bin/lib
D.Walsh wrote:
Peter, are you trying to tell me that the "libtool" supplied and
installed in Mac OSX is not the "GNU libtool"?
Yes, I am, in a way. Apple ships GNU libtool as /usr/bin/glibtool, and has a
completely different program as /usr/bin/libtool. Let me demonstrate:
peter% /usr/bin/libtoo
On Mar 07, 2005, at 17:42, Peter O'Gorman wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D.Walsh wrote:
| Any luck with generating a patch that allows libtool to work
properly in
| the Macintosh environment or has this ball been dropped already?
|
GNU Libtool does work properly in the Mac O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
D.Walsh wrote:
| Any luck with generating a patch that allows libtool to work properly in
| the Macintosh environment or has this ball been dropped already?
|
GNU Libtool does work properly in the Mac OS X environment. The fact that
you installed in /us
On Mon, 7 Mar 2005, D.Walsh wrote:
Any luck with generating a patch that allows libtool to work properly in the
Macintosh environment or has this ball been dropped already?
Please resend your patch.
Bob
==
Bob Friesenhahn
[EMAIL PROTECTED], http://www.simplesyst
Any luck with generating a patch that allows libtool to work properly
in the Macintosh environment or has this ball been dropped already?
-- Dale
Ralf Wildenhues wrote:
Thanks for reporting this. Your patch is not quite correct, as it
causes the $ in the libobj name to be quoted twice. Thus, the output
name of the .lo file will be wrong.
Hm. Yes.
Before delving into a better patch: Beware that such file names do not
play too well with oth
Hi Per,
* Per Bothner wrote on Mon, Mar 07, 2005 at 12:02:20AM CET:
> The srcname and the target name were not being quoted.
> This caused problems with Java, where .class files may
> commonly contain '$'.
Thanks for reporting this. Your patch is not quite correct, as it
causes the $ in the libo
