Re: GHC HEAD now needs extra tools to build libffi?

I don't know if it helps, but upgrading my ArchLinux installation yesterday broke my builds because of linker issues with stack. I now have to specify "ghc-build: nopie" in stack.yaml file. (cf https://github.com/commercialhaskell/stack/issues/2712) Could your error be related to PIE too?

Re: GHC HEAD now needs extra tools to build libffi?

Hi, Am Montag, den 23.10.2017, 20:49 +0800 schrieb Moritz Angermann: > I still can’t make sense of this. Is your gold a different version now as > well? It is “GNU gold (GNU Binutils 2.29.1) 1.14” now, and it seems it was upgraded: [2017-10-22 16:58] [ALPM] upgraded binutils (2.27-1 ->

Re: GHC HEAD now needs extra tools to build libffi?

I still can’t make sense of this. Is your gold a different version now as well? Sent from my iPhone > On 23 Oct 2017, at 8:45 PM, Joachim Breitner wrote: > > Hi, > > JFTR, upgrading the Arch installation, including ghc to 8.2.1, fixes > the issue for

Re: GHC HEAD now needs extra tools to build libffi?

Hi, JFTR, upgrading the Arch installation, including ghc to 8.2.1, fixes the issue for perf.haskell.org. Greetings, Joachim Am Donnerstag, den 19.10.2017, 16:28 +0800 schrieb Moritz Angermann: > Hi, > > As it turns out this might be linker madness. I do not yet understand why > this did work

Re: GHC HEAD now needs extra tools to build libffi?

Hi, As it turns out this might be linker madness. I do not yet understand why this did work with the "old" libffi though. The command that fails is a rather long gcc invocation asking it to link a bunch of libraries together. $ gcc -fno-stack-protector -DTABLES_NEXT_TO_CODE '-fuse-ld=gold'

Re: GHC HEAD now needs extra tools to build libffi?

Hi, I was able to reproduce this with: Ubuntu 16.10 (YakketyYak), stack's ghc (8.0.2) (via stack setup). I'll try to figure out what's going wrong here. Cheers, Moritz > On Oct 18, 2017, at 11:38 PM, Joachim Breitner > wrote: > > Hi, > > it’s an Arch linux

Re: GHC HEAD now needs extra tools to build libffi?

Hi, it’s an Arch linux (generously sponsored by Richard’s university). I have not idea how to give more precise information about the distro release version or such :-) Greetings, Joachim Am Mittwoch, den 18.10.2017, 22:02 +0800 schrieb Moritz Angermann: > Hi, > > so this somehow looks like

Re: GHC HEAD now needs extra tools to build libffi?

Hi, so this somehow looks like for a not yet absolutely clear reason to me, when building ghci, we fail to link in libffi, for some configurations. Joachim, as far as I could see, you are using ghc 8.0.1 to boostrap the compiler. Thomas are you by any chance bootstrapping with 8.0.1 as well? I

Re: GHC HEAD now needs extra tools to build libffi?

I’ll try to dig into this in three days when I’m back in SG. Joachim, thanks for providing the full build log. Sent from my iPhone > On 15 Oct 2017, at 5:41 AM, Ben Gamari wrote: > > Joachim Breitner writes: > >> Hi, >> >> >> Am Dienstag,

Re: GHC HEAD now needs extra tools to build libffi?

Joachim Breitner writes: > Hi, > > > Am Dienstag, den 03.10.2017, 13:55 -0400 schrieb Thomas Jakway: >> Anyone else getting linker errors? >> >> /home/thomas/git/ghc-new/libraries/ghci/dist-install/build/libHSghci-8.3-ghc8.3. >> 20171003.so: error: undefined reference

Re: GHC HEAD now needs extra tools to build libffi?

Hi, Am Dienstag, den 03.10.2017, 13:55 -0400 schrieb Thomas Jakway: > Anyone else getting linker errors? > > /home/thomas/git/ghc-new/libraries/ghci/dist-install/build/libHSghci-8.3-ghc8.3. > 20171003.so: error: undefined reference to 'ffi_type_uint64' > chmod +x

Re: GHC HEAD now needs extra tools to build libffi?

Thanks for getting back to me. (I think you mean `git clean -x -f -d`): I usually omit -x but I'll give it a go and report back. Before I got the issue on a clean checkout I thought it was something I did to the build files. I also tried building the latest release of libffi (v3.2.1) and

Re: GHC HEAD now needs extra tools to build libffi?

Yes, this commit indeed introduced the need for makeinfo, however after some debugging and improved packaging of the external libffi library, this dependency was removed again, and should not be required with the latest head anymore. Then again this should not result in link issues but rather

Re: GHC HEAD now needs extra tools to build libffi?

I'm on Ubuntu 16.10. I ran git bisect: -- e515c7f37be97e1c2ccc497ddd0a730e63ddfa82 is the first bad commit commit e515c7f37be97e1c2ccc497ddd0a730e63ddfa82 Author: Moritz Angermann Date: Sat Sep 30 09:31:12 2017 -0400 Allow libffi snapshots

Re: GHC HEAD now needs extra tools to build libffi?

Thomas Jakway writes: > Anyone else getting linker errors? > > > This is after running > > make clean && make distclean && find . -name "*.o" -type f -delete && > find . -name "*.hi" -type f -delete > > then > > ./boot && ./configure && make -j5 > > (ghc-new is not a new

Re: GHC HEAD now needs extra tools to build libffi?

Thomas Jakway writes: > Hm, so it's definitely not anything I changed. I just cloned and built > it and got the same problem (7109fa8157f3258912c947f28dab7617b5e5d281). > Alright, I'm trying to replicate. Cheers, - Ben signature.asc Description: PGP signature

Re: GHC HEAD now needs extra tools to build libffi?

Build flavor is devel2, of course. On 10/03/2017 04:42 PM, Ben Gamari wrote: Can you confirm which commit you are on? On October 3, 2017 4:36:48 PM EDT, Thomas Jakway wrote: Not sure. I ran `git submodule update --init --recursive` and git status says everything's

Re: GHC HEAD now needs extra tools to build libffi?

Hm, so it's definitely not anything I changed. I just cloned and built it and got the same problem (7109fa8157f3258912c947f28dab7617b5e5d281). On 10/03/2017 04:42 PM, Ben Gamari wrote: Can you confirm which commit you are on? On October 3, 2017 4:36:48 PM EDT, Thomas Jakway

Re: GHC HEAD now needs extra tools to build libffi?

Can you confirm which commit you are on? On October 3, 2017 4:36:48 PM EDT, Thomas Jakway wrote: >Not sure. I ran `git submodule update --init --recursive` and git >status says everything's up to date. I'm on Ubuntu 16.10. > > >On 10/03/2017 02:17 PM, John Leo wrote: >> I

Re: GHC HEAD now needs extra tools to build libffi?

Not sure. I ran `git submodule update --init --recursive` and git status says everything's up to date. I'm on Ubuntu 16.10. On 10/03/2017 02:17 PM, John Leo wrote: I pulled head this morning and built with no problems on a Mac. I wonder if you need to pull submodules as well (which I did)

Re: GHC HEAD now needs extra tools to build libffi?

I pulled head this morning and built with no problems on a Mac. I wonder if you need to pull submodules as well (which I did) or if you're missing some newly required dependency. John On Tue, Oct 3, 2017 at 10:55 AM, Thomas Jakway wrote: > Anyone else getting linker errors? >

Re: GHC HEAD now needs extra tools to build libffi?

Anyone else getting linker errors? /home/thomas/git/ghc-new/libraries/ghci/dist-install/build/libHSghci-8.3-ghc8.3. 20171003.so: error: undefined reference to 'ffi_type_uint64' chmod +x inplace/bin/runghc /home/thomas/git/ghc-new/libraries/ghci/dist-install/build/libHSghci-8.3-ghc8.3.

Re: GHC HEAD now needs extra tools to build libffi?

Moritz Angermann writes: > I hope this will be fixed with: > https://phabricator.haskell.org/D4053 and > https://phabricator.haskell.org/D4054 > This should be fixed as of 9968aa3631bdee7b3215dcaf7b513d8ffe6fff4c. Cheers, - Ben signature.asc Description: PGP signature

Re: GHC HEAD now needs extra tools to build libffi?

I hope this will be fixed with: https://phabricator.haskell.org/D4053 and https://phabricator.haskell.org/D4054 Sent from my iPhone > On 2 Oct 2017, at 6:33 AM, Ryan Scott wrote: > > Trying to build a fresh copy of GHC HEAD (at commit [1]) today failed > for me with