It's only relocatable given some assumptions which are violated by
various distributions (AIX was already mentioned; and the bin and lib
directories may not be next to each other with some distributions'
preferred configurations). Basically the configure mechanism gives us
some flexibility not
Per https://gitlab.haskell.org/ghc/ghc/issues/17191 I do hope to break
up our configure script soon.[1] Then the bindist will need not ship the
"entire" configure script, but just what is necessary to fill in the
settings file(s) which have that information Ben mentions.
I think that will
"Mathieu Boespflug" writes:
> Hi all,
>
> GHC currently has 3 tier-1 platforms: Linux, macOS and Windows. I'll
> focus the dicussion below on these three platforms. The binary
> distributions for Linux and macOS are designed to be unpacked, then
> the user types ./configure && make install. This
Hi Mathieu,
you can! See http://hackage.mobilehaskell.org/; it's been one of the
design goals I had when I was hacking on hadrian. The whole configure
&& make install shenanigans were just too much.
Initially I wanted to drop that outright, but was convinced that
configure and make install is
Hi all,
GHC currently has 3 tier-1 platforms: Linux, macOS and Windows. I'll focus the
dicussion below on these three platforms. The binary distributions for Linux
and macOS are designed to be unpacked, then the user types ./configure && make
install. This is not the case for Windows.
On all
