Re: 64-bit windows version?

2007-06-25 Thread Simon Marlow
Peter Tanski wrote: On Jun 22, 2007, at 11:42 AM, Simon Marlow wrote: Peter Tanski wrote: A bit invasive (it involves modifying the make rules so they take an object-suffix variable). Instead of the current suffix.mk: $(odir_)%.$(way_)o : %.hc it should be: $(odir_)%.$(way_)$(obj_sfx) :

Re: 64-bit windows version?

2007-06-25 Thread Peter Tanski
On Jun 25, 2007, at 5:19 AM, Simon Marlow wrote: Yes it is easy but now all Makefiles must be changed to use $ (osuf), such as this line in rts/Makefile: 378: %.$(way_)o : %.cmm $(H_FILES), for what will be a (hopefully) temporary Windows build. I bet there are only a few makefiles that

Re: 64-bit windows version?

2007-06-25 Thread skaller
On Mon, 2007-06-25 at 11:43 -0400, Peter Tanski wrote: It would be much better to have a single build system. I would gladly replace the whole thing for three reasons: (1) it is a source of many build bugs and it makes them much more difficult to track down; and, (2) it seems to be a

Re: 64-bit windows version?

2007-06-25 Thread Gour
On Tue, 26 Jun 2007 02:06:25 +1000 skaller [EMAIL PROTECTED] wrote: My basic idea is that it should be generic and package based, that is, it does NOT include special purpose tools as might be required to build, say, Haskell programs: these are represented by 'plugin' components. Have you

need help with 6.4.2 boot build for hpux 11.0

2007-06-25 Thread Joe Buehler
I am attempting to get 6.4.2 booted under hpux 11.0 following the instructions for building from hc files generated on another machine. The target compiler builds but will not build a trivial test program. The error message indicates that it cannot import the Prelude module. Looking at the

Re: 64-bit windows version?

2007-06-25 Thread Peter Tanski
On Jun 25, 2007, at 12:06 PM, skaller wrote: On Mon, 2007-06-25 at 11:43 -0400, Peter Tanski wrote: It would be much better to have a single build system. I would gladly replace the whole thing ... I am thinking of starting a new project (possibly as sourceforge) to implement a new build

Re: 64-bit windows version?

2007-06-25 Thread kyra
Certainly doable but it does present a conundrum: for the old GHC (without builtin cl-support) the order for compilation seems to be: compile/link command compile/link flags output source/object files other flags while for cl running link.exe or link.exe, it is better to put all the files at

Re: 64-bit windows version?

2007-06-25 Thread Peter Tanski
On Jun 25, 2007, at 12:55 PM, kyra wrote: Certainly doable but it does present a conundrum: for the old GHC (without builtin cl-support) the order for compilation seems to be: compile/link command compile/link flags output source/ object files other flags while for cl running link.exe or

Re: 64-bit windows version?

2007-06-25 Thread skaller
On Mon, 2007-06-25 at 13:35 -0400, Peter Tanski wrote: Maybe some gcc mimicing cl wrapper tailored specifically for GHC building system could help? One more layer of indirection, but could leave ghc driver relatively intact. That's a good idea! Do you know if or how the mingw-gcc is

Re[2]: 64-bit windows version?

2007-06-25 Thread Bulat Ziganshin
Hello Peter, Monday, June 25, 2007, 9:35:31 PM, you wrote: Maybe some gcc mimicing cl wrapper tailored specifically for GHC building system could help? One more layer of indirection, but could leave ghc driver relatively intact. That's a good idea! there is possibility that such driver

Re: 64-bit windows version?

2007-06-25 Thread Peter Tanski
On Jun 25, 2007, at 3:34 PM, skaller wrote: On Mon, 2007-06-25 at 13:35 -0400, Peter Tanski wrote: Maybe some gcc mimicing cl wrapper tailored specifically for GHC building system could help? One more layer of indirection, but could leave ghc driver relatively intact. That's a good idea!