-optl behavior in ghc-7.8.1
allbery.b at gmail.com
Thu Apr 10 16:52:54 UTC 2014
On Thu, Apr 10, 2014 at 12:39 PM, Yuras Shumovich <shumovichy at gmail.com>wrote:
> On Thu, 2014-04-10 at 12:13 -0400, Brandon Allbery wrote:
> > On Thu, Apr 10, 2014 at 12:02 PM, Yuras Shumovich <shumovichy at gmail.com
> > > On Thu, 2014-04-10 at 11:54 -0400, Brandon Allbery wrote:
> > > > On Thu, Apr 10, 2014 at 11:44 AM, Yuras Shumovich <
> shumovichy at gmail.com
> > > >wrote:
> > > > > Is it intentional change?
> > > >
> > > > Pretty sure it is intentional, because it's necessary for some
> > > ld
> > > > options are not in general position independent, and can't be.
> > >
> > > Yes, I understand. But how the new behavior is better then the old one?
> > If it was not clear from what I said that some linker options must come
> > before objects/libraries to have any effect then I am not sure what will
> > clarify it for you.
> ...and other linker options must come after, like in my case. So what?
Is your use case that much more important than everyone else's that other
people's bugs must be rejected for your convenience? This has been an issue
for other people and the change was needed.
> Are you kidding me? cabal unconditionally adds "-l" to extra-libraries.
I may be misremembering some other option; I do recall people using direct
references to static archives in cabal files, and not via ld-options where
they don't belong.
brandon s allbery kf8nh sine nomine associates
allbery.b at gmail.com ballbery at sinenomine.net
unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Glasgow-haskell-users