Here's what I could find:
[dfeuer@lemur libffi]$ find . -name "*\.a"
./build/inst/lib64/libffi.a
./build/x86_64-unknown-linux-gnu/.libs/libffi.a
./build/x86_64-unknown-linux-gnu/.libs/libffi_convenience.a
On Sat, Sep 20, 2014 at 6:15 AM, Moritz Angermann
wrote:
> Could you check if you had any
Filed a bug under GHC Trac, #9620
On Sat, Sep 20, 2014 at 7:24 AM, Herbert Valerio Riedel
wrote:
> Hello!
>
> Is there a ticket for that already on GHC Trac? If not, please create
> one, and try to document everything we already know about this issue
>
> On 2014-09-20 at 14:25:56 +0200, member M
Symlinking lib64 to lib didn't seem to work, I think the directory is
getting cleared before build. But if I copy the contents of lib64 to lib
after the build fails and then type make again, ghc compiles!
Thanks for the workaround, hopefully a real fix will be found soon enough :)
On Sat, Sep 20,
While this is not a proper fix. Assuming there is no no lib folder, and the
proper lib is in lib64, does: symlinking lib64 to lib and continuing with make
solve the issue?
On Sep 20, 2014, at 12:32 PM, member MP2E wrote:
> Yep, I reported this same build error for NixOS on x86_64, unfortunatel
Yep, I reported this same build error for NixOS on x86_64, unfortunately I
haven't found any way to solve it. Reverting the commit that upgrades to
libffi-3.1 still showed this issue. I'd love to see this fixed, as I am
unable to do any development on GHC until it's fixed :(
On Sat, Sep 20, 2014 a
Could you check if you had any other libffi.a or (any other .a) file for that
matter in the
libffi folder? I have the suspicion that the new libffi builds the archives
for some platforms into different target folders, as someone on irc mentioned
that for nix, there was a lib64 folder or so, and
