Keith Wansbrough wrote:
> AFAICS, a straightforward solution is for the configure script to
> determine the absolute paths of both ghc and ghc-pkg, and for the rest
> of the build system to use those absolute paths, rather than relying
> on the executable search path to find them. This still breaks if
> "ghc-pkg" does not correspond to "ghc" even with the same path; but
> this is a much less likely scenario (and the --hc=foo, --hcpkg=foo,
> switches are still there to address it).
>
Hi Keith,
Thanks for the detailed bug report -- I'll try to fix this in the
configure script (and maybe I'll even ask you to try it out before
releasing wxHaskell 0.9 :-)
> Thanks for a great piece of software; I'm enjoying using it!
Ha, that is good to hear after all the countless hours of
wxWidgets debugging ;-)
-- Daan.
> Hi... recently I attempted to install wxHaskell on a system with
> multiple versions of GHC installed. I did
>
> ./configure --prefix=/usr/local/foo --with-opengl
> make
> su
> make install
>
> The "make" phase used the default "ghc" in my path.
>
> The "make install" phase used the default "ghc-pkg" in my path.
>
> However, my paths as ordinary user and as root are _different_, and so
> these were different: /usr/local/bin/ghc ->
> /usr/local/bin/ghc-6.3.20041124 versus /usr/bin/ghc-pkg ->
> /usr/bin/ghc-pkg-6.2.2.
>
> This had the obvious consequence of registering a wxHaskell built for
> one ghc, ghc-6.3.20041124, with the wrong ghc, ghc-6.2.2.
>
> AFAICS, a straightforward solution is for the configure script to
> determine the absolute paths of both ghc and ghc-pkg, and for the rest
> of the build system to use those absolute paths, rather than relying
> on the executable search path to find them. This still breaks if
> "ghc-pkg" does not correspond to "ghc" even with the same path; but
> this is a much less likely scenario (and the --hc=foo, --hcpkg=foo,
> switches are still there to address it).
>
> Thanks for a great piece of software; I'm enjoying using it!
>
> --KW 8-)
>
|
