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 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 assume Ben bootstraps wit 8.2.1. > > I'll set up a Ubuntu 16.10 machine tomorrow and try to reproduce this. > > Joachim, is perf.haskell.org running Ubuntu as well? > > Cheers, > Moritz > > > On Oct 11, 2017, at 1:43 AM, Thomas Jakway <tjak...@nyu.edu> wrote: > > > > 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 using it in > > configure with --with-ffi-includes and --with-ffi-libraries but got the > > same error. > > > > > > On 10/09/2017 02:40 AM, Moritz Angermann wrote: > > > 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 in build time > > > issues. > > > > > > The key to libffi is the libffi-tarballs git submodule, which contains > > > the packaged libffi-tarballs. Make sure all your submodules are also > > > updated. > > > > > > I usually use `git -x -f -d` (read the documentation first) to ensure a > > > clean working tree. Especially as you say you can’t reproduce it on other > > > machines, maybe there is a file in your tree that the cleaning did not > > > catch? > > > > > > Sent from my iPhone > > > > > > > On 9 Oct 2017, at 4:31 AM, Thomas Jakway <tjak...@nyu.edu> wrote: > > > > > > > > I'm on Ubuntu 16.10. > > > > > > > > I ran git bisect: > > > > > > > > ---------------------- > > > > > > > > e515c7f37be97e1c2ccc497ddd0a730e63ddfa82 is the first bad commit > > > > commit e515c7f37be97e1c2ccc497ddd0a730e63ddfa82 > > > > Author: Moritz Angermann <moritz.angerm...@gmail.com> > > > > Date: Sat Sep 30 09:31:12 2017 -0400 > > > > > > > > Allow libffi snapshots > > > > > > > > This is rather annoying. I'd prefer to have a stable release to > > > > use. However libffi-3.2.1 has been released November 12, 2014, and > > > > libffi-4 is TBD. See also https://github.com/libffi/libffi/issues/296 > > > > > > > > The core reason for this change is that llvm changed the supported > > > > assembly to unified syntax, which libffi-3.2.1 does not use, and hence > > > > fails to compile for arm with llvm. For refence, see the following > > > > issue: https://github.com/libffi/libffi/issues/191. > > > > > > > > This diff contains a script to generate a tarball for the > > > > `libffi-tarballs` repository from the libffi GitHub repository; as well > > > > as the necessary changes to the build system. > > > > > > > > Updates libffi-tarballs submodule. > > > > > > > > Reviewers: austin, bgamari, hvr > > > > > > > > Subscribers: hvr, erikd, rwbarton, thomie > > > > > > > > Differential Revision: https://phabricator.haskell.org/D3574 > > > > > > > > ---------------------- > > > > > > > > I can't reproduce it on my other linux computers though. > > > > > > > > > > > > > On 10/04/2017 02:17 PM, Ben Gamari wrote: > > > > > Thomas Jakway <tjak...@nyu.edu> 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 checkout, this error is happening on a branch > > > > > > I'm > > > > > > working on, but one that doesn't touch the FFI) > > > > > > > > > > > > > > > > I'm afraid I can't reproduce this. What platform/operating system is > > > > > this on? > > > > > > > > > > Cheers, > > > > > > > > > > - Ben > > > > > > > > _______________________________________________ > > > > ghc-devs mailing list > > > > ghc-devs@haskell.org > > > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > > > _______________________________________________ > > ghc-devs mailing list > > ghc-devs@haskell.org > > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > -- Joachim Breitner m...@joachim-breitner.de http://www.joachim-breitner.de/
signature.asc
Description: This is a digitally signed message part
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
