and others.
+
2011-02-12 Peter O'Gorman
Install ltmain.sh without execute bit set.
diff --git a/NEWS b/NEWS
index dbad2ae..90d14b7 100644
--- a/NEWS
+++ b/NEWS
@@ -10,6 +10,9 @@ New in 2.4.2 2011-??-??: git version 2.4.1a, Libtool team:
- Initial support for Go, using the gccgo comp
On 03/04/2011 12:47 PM, Ralf Wildenhues wrote:
[ dropping bug-libtool ]
Hi Peter,
* Peter O'Gorman wrote on Fri, Mar 04, 2011 at 07:07:30PM CET:
Ok?
A few copyright year bumps are missing.
Oh, yeah, will fix.
Some minor nits inline below.
+AT_SETUP(darwin can lt_dlopen .dylib and .so
[ dropping bug-libtool ]
Hi Peter,
* Peter O'Gorman wrote on Fri, Mar 04, 2011 at 07:07:30PM CET:
> Ok?
A few copyright year bumps are missing.
Some minor nits inline below.
Thank you,
Ralf
> Subject: [PATCH] On Mac OS X try .dylib as well as .so with lt_dlopenext
>
> * libltdl/m4/ltdl.m4: De
pasted lt_dlopenext testcase and slightly modified it), passes after.
.dylib is tried after .so so there is no potentially surprising change
in behaviour for existing applications.
Oh, I forgot a NEWS entry, will add:
"On Mac OS X .dylib is now tried as well as .so with lt_dlopenext" there
Hello,
* Michael Ellis wrote on Fri, Mar 04, 2011 at 04:48:44AM CET:
> If I install 2.4, do I need to rebuild everything that
> uses it or will the newer library be picked up at run time?
The last incompatible change in libltdl was in Libtool 2.2.6.
If you are upgrading from a version older than
On 4 Mar 2011, at 04:00, Bob Friesenhahn wrote:
>> So guile-2.0.0 using libltdl.7.dylib of libtool-2.4, can on Mac OS X 10.6.6
>> only open a dynamic library if the name of what it actually opens ends in
>> .so (say by making a soft link using 'ln -s'); if it ends in .dylib, it
>> cannot open i
On 4 Mar 2011, at 03:59, Peter O'Gorman wrote:
>>> Mac OS X does not care about file name extensions; .dylib is just a
>>> convention for native dynamic libraries.
>
> The static linker when it sees a -l flag will look for files beginning with
> "lib" and ending in ".dylib", ".so" (though this
Hi Peter,
On Fri 04 Mar 2011 03:59, Peter O'Gorman writes:
>>> So the wanted behavior is to first try opening a library without
>>> adding an extension, and then try out different endings. On Mac OS
>>> X, it would be best trying out .dylib first - I haven't seen any
>>> other ending in use.
>
>
On Thu, Mar 3, 2011 at 10:00 PM, Bob Friesenhahn
wrote:
> Are you sure that libltdl from libtool-2.4 is being used? The dtruss trace
> (from Michael Ellis) at
> http://lists.gnu.org/archive/html/bug-guile/2011-03/msg00020.html shows
> insecure accesses more like I would expect from a libtool ver
On Thu, Mar 3, 2011 at 9:59 PM, Peter O'Gorman wrote:
>
> However, I can see the point that libltdl should try .dylib as well as .so
> for lt_dlopenext on Mac OS X. I will come up with a patch for that.
>
> Peter
Thanks, Peter. I'll be happy to test it.
Cheers,
Mike
On Thu, 3 Mar 2011, Hans Åberg wrote:
So guile-2.0.0 using libltdl.7.dylib of libtool-2.4, can on Mac OS X
10.6.6 only open a dynamic library if the name of what it actually
opens ends in .so (say by making a soft link using 'ln -s'); if it
ends in .dylib, it cannot open it, even if the full na
On 03/03/2011 01:56 PM, Michael Ellis wrote:
On Thu, Mar 3, 2011 at 2:32 PM, Hans Åberg wrote:
[I'm not on the bug-libtool list, so please cc me.]
Despite being reported a year ago, Guile can still not open dynamic libraries
ending with .dylib on Mac OS X. Looking throw the past discussion, i
On Thu, Mar 3, 2011 at 2:32 PM, Hans Åberg wrote:
> [I'm not on the bug-libtool list, so please cc me.]
>
> Despite being reported a year ago, Guile can still not open dynamic libraries
> ending with .dylib on Mac OS X. Looking throw the past discussion, it looks
> as though developers of the on
[I'm not on the bug-libtool list, so please cc me.]
Despite being reported a year ago, Guile can still not open dynamic libraries
ending with .dylib on Mac OS X. Looking throw the past discussion, it looks as
though developers of the one package hold the opinion that those of the other
package
[I'm not on the bug-libtool list, so please cc me.]
Despite being reported a year ago, Guile can still not open dynamic libraries
ending with .dylib on Mac OS X. Looking throw the past discussion, it looks as
though developers of the one package hold the opinion that those of the other
package
On 4 Feb 2010, at 16:34, Peter O'Gorman wrote:
$ lilypond empty.ly
dyld: loaded: /Applications/LilyPond.app/Contents/Resources/bin/../
lib//libintl.8.dylib
dyld: loaded: /Applications/LilyPond.app/Contents/Resources/bin/../
lib//libguile.17.dylib
dyld: loaded: /Applications/LilyPond.app/Con
On 4 Feb 2010, at 16:34, Peter O'Gorman wrote:
Not really: 10.4 and earlier are obsolete, and 10.5 is becoming. On
10.5, just ordinary load is fine.
10.4 and earlier are not obsolete, sorry.
The only computers that can't run 10.4 are G3 and they are really to
slow. At least the one I inst
On Thu, Feb 04, 2010 at 04:21:27PM +0100, Hans Aberg wrote:
>> When libtool support for Mac OS X was added, there was no way to load
>> .dylib files, not much software had any knowledge of Mac OS X, and
>> quite
>> a lot of things had hardcoded ".so" when loading files at runtime, so
>> to
>> ac
On Thu, Feb 04, 2010 at 01:40:07PM +0100, Hans Aberg wrote:
> On 2 Feb 2010, at 17:52, Bob Friesenhahn wrote:
>
>> Under OS-X (Leopard and later), the 'dtruss' program can be used to
>> see what is really going on.
>
> While at it, I found another problem involving libltdl.7.dylib,
> guile-1.8.
On 4 Feb 2010, at 14:49, Peter O'Gorman wrote:
What does otool -L
/Applications/LilyPond.app/Contents/Resources/bin/guile say? Which
libltdl.7.dylib does it list?
See below. They differ: libltdl.7.dylib current versions 10.0.0 and
10.1.0.
If you run lilypond with DYLD_PRINT_LIBRARIES=1 se
On 2 Feb 2010, at 17:52, Bob Friesenhahn wrote:
Under OS-X (Leopard and later), the 'dtruss' program can be used to
see what is really going on.
While at it, I found another problem involving libltdl.7.dylib,
guile-1.8.7 and lilypond 2.13.7:
When upgrading guile using libtool-2.2.6b, lily
Hi,
Ken Raeburn writes:
> [Is Hans on one of these lists now? His original message to bug-guile
> said not and asked to be cc'ed.]
We might have lost him then. ;-)
> On Feb 2, 2010, at 13:01, Ludovic Courtès wrote:
>> The Guile manually specifically tells that FNAME should not contain
>> an
[Is Hans on one of these lists now? His original message to bug-guile said not
and asked to be cc'ed.]
On Feb 2, 2010, at 13:01, Ludovic Courtès wrote:
> The Guile manually specifically tells that FNAME should not contain an
> extension.
That could be unfortunate, since it means that unlike oth
On Tue, 2 Feb 2010, Hans Aberg wrote:
On 2 Feb 2010, at 15:20, Ken Raeburn wrote:
On Mac OS X (trying it on 10.5.8 PPC G4), guile-1.8.7 cannot open
dynamic library files with name extensions .dylib, but only if they
are renamed using .so instead. On the Bug-Guile list they say it
just calls li
Hi,
Hans Aberg writes:
> On 2 Feb 2010, at 17:52, Bob Friesenhahn wrote:
>
>> Unless I am missing something, the question to be answered is if
>> Guile requests opening modules using a name like "module.so"
>> (assuming a particular naming scheme), "module.la" (using libltdl
>> as originally i
On 2 Feb 2010, at 17:52, Bob Friesenhahn wrote:
Unless I am missing something, the question to be answered is if
Guile requests opening modules using a name like
"module.so" (assuming a particular naming scheme),
"module.la" (using libltdl as originally intended), or bare
"module" (using
On 2 Feb 2010, at 15:20, Ken Raeburn wrote:
On Mac OS X (trying it on 10.5.8 PPC G4), guile-1.8.7 cannot open
dynamic library files with name extensions .dylib, but only if they
are renamed using .so instead. On the Bug-Guile list they say it
just calls libltdl, in the libtool package. I have in
Hello Hans,
* Hans Aberg wrote on Mon, Feb 01, 2010 at 03:26:53PM CET:
> On Mac OS X (trying it on 10.5.8 PPC G4), guile-1.8.7 cannot open
> dynamic library files with name extensions .dylib, but only if they
> are renamed using .so instead. On the Bug-Guile list they say it
> just calls libltdl,
On Feb 2, 2010, at 04:08, Hans Aberg wrote:
On 2 Feb 2010, at 07:42, Ralf Wildenhues wrote:
>
>>> On Mac OS X (trying it on 10.5.8 PPC G4), guile-1.8.7 cannot open
>>> dynamic library files with name extensions .dylib, but only if they
>>> are renamed using .so instead. On the Bug-Guile list they
On 2 Feb 2010, at 07:42, Ralf Wildenhues wrote:
On Mac OS X (trying it on 10.5.8 PPC G4), guile-1.8.7 cannot open
dynamic library files with name extensions .dylib, but only if they
are renamed using .so instead. On the Bug-Guile list they say it
just calls libltdl, in the libtool package. I hav
[I'm not on this list, so please cc me.]
On Mac OS X (trying it on 10.5.8 PPC G4), guile-1.8.7 cannot open
dynamic library files with name extensions .dylib, but only if they
are renamed using .so instead. On the Bug-Guile list they say it just
calls libltdl, in the libtool package. I have
On 30 Jan 2010, at 20:30, Andy Wingo wrote:
It seems guile-1.8.7 does not admit dynamic library file name
extensions
.dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4)
I think your example shold work, but it's something that's totally
handled by libltdl. Are you using the latest libltd
On 30 Jan 2010, at 19:39, Ken Raeburn wrote:
The Mac OS X situation is a bit more complicated than on "normal"
ELF-based UNIX systems; shared libraries and dynamically loadable
objects are not the same thing. It's easy to assume they're
equivalent when working mostly on ELF or Windows syst
On 30 Jan 2010, at 19:37, Ludovic Courtès wrote:
The abstraction over file name extensions is handled by Libtool’s
libltdl, used in ‘libguile/dynl.c’. Which version of Libtool/ltdl are
you using?
I took down the latest stable before trying to compile guile:
libtool --version
ltmain.sh (GN
Hello Hans,
On Sat 30 Jan 2010 15:41, Hans Aberg writes:
> It seems guile-1.8.7 does not admit dynamic library file name extensions
> .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4)
I think your example shold work, but it's something that's totally
handled by libltdl. Are you using the
On Jan 30, 2010, at 09:41, Hans Aberg wrote:
[I'm not on this list, so please cc me.]
It seems guile-1.8.7 does not admit dynamic library file name
extensions .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4),
despite the manual saying guile should adapt to local standards. The
exam
Hello,
Hans Aberg writes:
> It seems guile-1.8.7 does not admit dynamic library file name
> extensions .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4),
> despite the manual saying guile should adapt to local standards. The
> example in the manual sec. 4.2.1 works fine with
> gcc -dyna
[I'm not on this list, so please cc me.]
It seems guile-1.8.7 does not admit dynamic library file name
extensions .dylib, but only .so, on Mac OS X (tried 10.5.8. PPC G4),
despite the manual saying guile should adapt to local standards. The
example in the manual sec. 4.2.1 works fine with
38 matches
Mail list logo
