On Thu, 2009-05-14 at 09:15 +0100, Simon Marlow wrote:
> On 13/05/2009 19:54, Duncan Coutts wrote:
> > Shared libs enthusiasts,
> >
> > We can use ghc to link a bunch of .o files into a shared lib:
> >
> > $ ghc -dynamic -shared Blah.o -o libHSblah.so
> >
> > The question on ELF platforms is how we
On 13/05/2009 19:54, Duncan Coutts wrote:
Shared libs enthusiasts,
We can use ghc to link a bunch of .o files into a shared lib:
$ ghc -dynamic -shared Blah.o -o libHSblah.so
The question on ELF platforms is how we should set the "soname". This
name is name baked into the .so lib and used to i
On Wed, 2009-05-13 at 20:35 +0100, Neil Mitchell wrote:
> Hi
>
> > With gcc, on ELF platforms you would use:
> >
> > $ gcc -shared Blah.o -o libblah.so -Wl,-soname,libblah.so
> >
> > We could require (or at least suggest) -package-name be given when
> > linking a shared lib. However that would inv
Hi
> With gcc, on ELF platforms you would use:
>
> $ gcc -shared Blah.o -o libblah.so -Wl,-soname,libblah.so
>
> We could require (or at least suggest) -package-name be given when
> linking a shared lib. However that would involve baking in the "HS"
> library prefix name convention into ghc.
>
> O
Shared libs enthusiasts,
We can use ghc to link a bunch of .o files into a shared lib:
$ ghc -dynamic -shared Blah.o -o libHSblah.so
The question on ELF platforms is how we should set the "soname". This
name is name baked into the .so lib and used to identify the library by
the dynamic linker (t
