Ticket #1160 (closed defect: fixed)

Opened 8 years ago

Last modified 8 years ago

gtk2hs builds but does not install under Windows

Reported by: guest Owned by: pgavin
Priority: normal Milestone: 0.10.2
Component: general (Gtk+, Glib) Version:
Keywords: Cc:


To cut a long story short... a few lines that say "$(DESTDIR)/$(pkglibdir)" in Makefile.in and Makefile.am should say "$(DESTDIR)$(pkglibdir)" (ie without the forward slash).

I'm surprised that this doesn't cause problems on other platforms - maybe it does? - but certainly building under MSys on Windows this prevents the installation from working (because directories like /C:/gtk2hs don't exist). And when I correct this error myself then it does work.

This with the 0.10.0 source package.

Change History

Changed 8 years ago by int-e

Just for the record, this should work on POSIX systems:


Changed 8 years ago by pgavin

  • status changed from new to closed
  • resolution set to invalid

Multiple slashes are valid on any POSIX system. DESTDIR should be empty under normal use, btw.

Marking as invalid.

Changed 8 years ago by guest

  • status changed from closed to reopened
  • resolution invalid deleted
  • summary changed from gtk2hs builds but does not install under Windows (and other platforms?) to gtk2hs builds but does not install under Windows

Invalid? Forgive my frustration, but I'd hardly have opened the ticket if I hadn't experienced a problem here. "Should work" is all very well, but "doesn't work" surely ought to carry more weight.

Would you please reconsider this ticket? Per my original report, I think that the fix ought to be very straightforward.

(BTW, a workaround suggested on the mailing list was to try "--prefix=/c/haskell" instead of "--prefix=c:/haskell". This also doesn't work, as with the extra slash that becomes //c/haskell, which gets interpreted as a non-existent network share).

Changed 8 years ago by pgavin

  • owner changed from somebody to pgavin
  • status changed from reopened to new
  • milestone set to 0.10.2

I probably shouldn't have marked it invalid, but rather as wontfix-- we don't really support running make install under Windows, but supply a Windows installer instead. But since this is a small change, I'll go ahead and do it. (I'll admit your bug fell victim to the effort I took to clean things up a few weeks ago, I apologize.)

I'm surprised that the install works with that change alone. Have you tried loading the package in ghci, for example? If everything works as it should, please let me know and I'll think about supporting make install under windows.

Changed 8 years ago by pgavin

  • status changed from new to closed
  • resolution set to fixed

Changed 8 years ago by guest

It was otherwise pretty close to working. As I recall I had to make some tweaks to the .package.conf files and reregister the packages with GHC; I'm afraid that I forget exactly what changes but I think that something about the extra-libraries was wrong in some fairly obvious way. Otherwise this was all good (and I have it working both under GHCI and in compiled code).

I would certainly prefer to use a Windows installer than go through the pain of compiling and fixing stuff myself. That would be much much easier. But there's a significant lag between GHC releases and Gtk2Hs releases. Unless I'm missing something, this leaves those of us who like to keep our software up-to-date (and also Haskell newcomers, who will surely take the most recent GHC) with little choice but to compile this stuff ourselves. If the Gtk2Hs team were able to release updated Windows installers reasonably close to GHC releases, that would be marvellous.

Anyway, thanks for making this change.

Note: See TracTickets for help on using tickets.