Thanks, Austin & Herbert.
Switching from clang to gcc-4.8 and reinstalling libraries eliminated most
of the noise for me.
In one set of my own libraries (bringing in new dependencies), I did get
several more haddock warnings from 'ghc-pkg check'. I reinstalled each of
those libs explicitly (cabal
On Thu, 2014-04-10 at 18:49 +0200, Karel Gardas wrote:
> On 04/10/14 06:39 PM, Yuras Shumovich wrote:
> > ...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 j
On Thu, Apr 10, 2014 at 12:39 PM, Yuras Shumovich wrote:
> On Thu, 2014-04-10 at 12:13 -0400, Brandon Allbery wrote:
> > On Thu, Apr 10, 2014 at 12:02 PM, Yuras Shumovich >wrote:
> > > On Thu, 2014-04-10 at 11:54 -0400, Brandon Allbery wrote:
> > > > On Thu, Apr 10, 2014 at 11:44 AM, Yuras Shumov
On 04/10/14 06:39 PM, Yuras Shumovich wrote:
...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.
Hmm, I'm not sure if I'm the patch
On Thu, 2014-04-10 at 12:13 -0400, Brandon Allbery wrote:
> On Thu, Apr 10, 2014 at 12:02 PM, Yuras Shumovich wrote:
>
> > On Thu, 2014-04-10 at 11:54 -0400, Brandon Allbery wrote:
> > > On Thu, Apr 10, 2014 at 11:44 AM, Yuras Shumovich > >wrote:
> > > > Is it intentional change?
> > >
> > > Pret
On Thu, Apr 10, 2014 at 12:02 PM, Yuras Shumovich wrote:
> On Thu, 2014-04-10 at 11:54 -0400, Brandon Allbery wrote:
> > On Thu, Apr 10, 2014 at 11:44 AM, Yuras Shumovich >wrote:
> > > Is it intentional change?
> >
> > Pretty sure it is intentional, because it's necessary for some options.
> ld
>
On Thu, 2014-04-10 at 11:54 -0400, Brandon Allbery wrote:
> On Thu, Apr 10, 2014 at 11:44 AM, Yuras Shumovich wrote:
>
> > ghc-7.6.3 passes additional linker options after all the haskell object
> > files, while ghc-7.8.1 does the opposite.
>
> (...)
>
> > Is it intentional change?
> >
>
> Pret
On Thu, Apr 10, 2014 at 11:44 AM, Yuras Shumovich wrote:
> ghc-7.6.3 passes additional linker options after all the haskell object
> files, while ghc-7.8.1 does the opposite.
(...)
> Is it intentional change?
>
Pretty sure it is intentional, because it's necessary for some options. ld
options a
Hi,
I found that -optl behavior was changed in ghc-7.8.1
ghc-7.6.3 passes additional linker options after all the haskell object
files, while ghc-7.8.1 does the opposite.
$ /opt/ghc-7.6.3/bin/ghc --make main.hs -optl=hello -v
...
'/usr/bin/gcc' '-fno-stack-protector' '-Wl,--hash-size=31'
'-Wl,-
Yes, exactly. Thank you.
On 10 April 2014 22:03, Herbert Valerio Riedel wrote:
> On 2014-04-10 at 06:00:43 +0200, Vivian McPhail wrote:
> > Indeed.
> >
> > It was using the wrong cabal-install version. Even though I had
> installed
> > the newest cabal-install I needed to restart the xterm I
Yes, exactly.
On 10 April 2014 22:03, Herbert Valerio Riedel wrote:
> On 2014-04-10 at 06:00:43 +0200, Vivian McPhail wrote:
> > Indeed.
> >
> > It was using the wrong cabal-install version. Even though I had
> installed
> > the newest cabal-install I needed to restart the xterm I was working
On 2014-04-10 at 06:00:43 +0200, Vivian McPhail wrote:
> Indeed.
>
> It was using the wrong cabal-install version. Even though I had installed
> the newest cabal-install I needed to restart the xterm I was working
> in.
Lemme guess, you're using Bash, and you installed cabal-install into a
new lo
On 2014-04-09 at 19:53:47 +0200, Conal Elliott wrote:
> From a bit of experimentation, it appears that the problematic packages do
> indeed have Haddock failures. For instance,
>
> bash-3.2$ cd random-1.0.1.1/
> bash-3.2$ cabal configure
> Resolving dependencies...
> Configuring ran
On Thu, Apr 10, 2014 at 6:42 AM, Carter Schonwald <
carter.schonw...@gmail.com> wrote:
> i bet you have cabal --version reply with 1.16 :)
>
> 1) cabal update
> 2) cabal install cabal-install
> 3) rm ~/.cabal/config # old pre 1.18 config should go!
>
This was news to me. Is there a list of the i
On Wednesday 09 April 2014, 23:42:26, Carter Schonwald wrote:
> i bet you have cabal --version reply with 1.16
>
> 1) cabal update
> 2) cabal install cabal-install
> 3) rm ~/.cabal/config # old pre 1.18 config should go!
> 4) cabal update # also probably add ~/.cabal/bin to path
There should be
15 matches
Mail list logo