[arch-haskell] What to do about --enable-shared?

[Leif Warner]

The packages in extra and community are built with enabled-shared.  I find
this useful because I then have the option of linking dynamically against
them in things I compile myself.  I was hoping that option would get enabled
in the PKGBUILDs generated by cabal2arch.

-Leif

On Wed, Oct 27, 2010 at 12:59 PM, Magnus Therning <magnus at therning.org>wrote:

> On 27/10/10 19:11, Peter Simons wrote:
> > Hi guys,
> >
> > I've made some tests with --enable-shared, and the good news is that it
> > works great. The bad news is that Cabal doesn't honor the flag when
> building
> > executables. Apparently, this is a known issue:
> >
> >     http://hackage.haskell.org/trac/hackage/ticket/600
> >
> > A work-around that has been suggested is to specify --ghc-opt=-dynamic
> for
> > builds that contain executables, but this solution feels kind of
> hack'ish.
> > On the other hand, shared linkage cuts down binary size a lot, which is
> > good.
> >
> > How do you feel about this issue? Any preferences?
>
> My gut says it's pointless to add --enable-shared if we don't also make
> sure
> executables are made to use shared libs.
>
> Would it be possible to somehow configure ghc in Arch to do all of this,
> both
> for libs and the hack for exes, automatically?
>
> /M
>
> --
> Magnus Therning                        (OpenPGP: 0xAB4DFBA4)
> magnus＠therning．org           Jabber: magnus＠therning．org
> http://therning.org/magnus         identi.ca|twitter: magthe
>
>
> _______________________________________________
> arch-haskell mailing list
> arch-haskell at haskell.org
> http://www.haskell.org/mailman/listinfo/arch-haskell
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/arch-haskell/attachments/20131012/c6575c7f/attachment.html>