Re: Relocatable dist

Hi, right now I’d like to compare the compiler at my feature branch with and without the last commit on that branch. I have a working copy at the end of my feature branch. If the worktree was relocatable, I could now simply `cp -r` the whole worktree, pop the top commit, run `make -C ghc 2` and

Re: Relocatable dist

Hi, just to elaborate a bit. We *can* build cross compiler, and cross compile ghc with the current make based build system. I'm not certain how well packaging binary distributions of cross compiled ghc's work. I've only run into several when trying to build binary distributions for cross

Re: Relocatable dist

That doesn’t mean it can’t be used for cross-compilation once it is in the tree. > Am 25.10.2017 um 11:06 schrieb Brandon Allbery : > > Discussion I've been seeing is Hadrian will not be ready for production use > for 8.4. Pulling it in tree is scheduled for 8.4 mostly to

Re: Relocatable dist

Discussion I've been seeing is Hadrian will not be ready for production use for 8.4. Pulling it in tree is scheduled for 8.4 mostly to make it easier to keep up to date with other changes and to make it easier to work on and test the various missing pieces: as I understand it, Hadrian can't yet

Re: Relocatable dist

> Am 24.10.2017 um 20:02 schrieb Moritz Angermann : > > Hi *, > > so I've given this a stab[1]. While getting the wrapper requirement, > and the .conf files sorted was rather easy. (We already have > getExecutablePath, > and the relocatable logic for windows. As

Re: Relocatable dist

On Tue, Oct 24, 2017 at 5:02 AM, Moritz Angermann < moritz.angerm...@gmail.com> wrote: > However, I am now again at the point where I start hacking on the build > system, while Hadrian is imminent. And this is quite depressing > Realistically, while Hadrian going into the tree may be imminent,

Re: Relocatable dist

Hi *, so I've given this a stab[1]. While getting the wrapper requirement, and the .conf files sorted was rather easy. (We already have getExecutablePath, and the relocatable logic for windows. As well as $topdir and ${pkgroot} support for paths in .conf files.) Now as Manuel laid out the

Re: Relocatable dist

Hi Manuel, thanks for the link! Ahh yes lovely RPATH (this reminds me, I should look to verify if I can make GHC link recursively.) The conf files came up on #ghc yesterday as well. Maybe we need some $home, $sysroot or similar marker to make them relocatable. I'll probably take a crack at

Re: Relocatable dist

Hi Moritz, Haskell for Mac is fully relocatable (as every Mac users expects this of a Mac app). Unfortunately, it is not just the libdir in the wrapper scripts that’s in the way of a relocatable GHC. Additional problems are (1) the (at least, as of 8.0) still not macOS-friendly RPATHs in

Re: Relocatable dist

Hi, Am Montag, den 23.10.2017, 14:04 +0800 schrieb Moritz Angermann: > I've come wonder, how hard it could be to > make GHC relocatable. (e.g. just unpack the distribution, > and use the compiler from the `bin` folder within). Yes yes yes please! (Sorry for not contributing anything but

Relocatable dist

Hi, while trying to make the binary-distribution logic work for cross compilers. I've come wonder, how hard it could be to make GHC relocatable. (e.g. just unpack the distribution, and use the compiler from the `bin` folder within). Right now this does not work due to the need for the path to