-optl behavior in ghc-7.8.1

[Yuras Shumovich]

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>wrote:
> 
> > 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 options.
> > 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?
Are there any ticket where people complain about the old behavior? I'm
not advocating any specific behavior, I'm just asking why it was
changed.

> 
> > >     ld-options:  ./path/to/libsomething.a
> > >
> > > You're abusing ld-options. Use extra-libraries for this; if it doesn't
> > work
> > > then you have found another bug and should file it as such.
> >
> > extra-libraries doesn't work because it links with libsomething.so
> > instead of libsomething.a
> >
> 
> Don't specify it using -l..., specify the .a file just as you were with
> ld-options.

Are you kidding me? cabal unconditionally adds "-l" to extra-libraries.