Your Inquiry in www.bau-center.com
DEAR SIR,
WE ARE URGENTLY LOOKING FOR USED LOADER TYP VOLVO KOMATSU 2 TILL 3 M3 FOR KROATIA.
4 OR 5 YEARS OLD.
PLEASE SEND US OFFER.
M.HOEPPNER.
___
Glasgow-haskell-users mailing list
[EMAIL PROTECTED]
| I'm trying to link ghc object files with mingw's
| g++/ld...
We have used the g++-2 compiler that you can get with Cygwin
and it seems to work fine. (mingw-g++ and the normal g++ did
not work for us.)
Another hint: maybe you should give -lstdc++ as a flag to
the final linking fase.
A final
Hi,
I'm trying to compile the latest version of GHC from CVS. I followed
the instructions on GHC's web page and everything worked just fine.
But when I updated the sources with cvs update -dP as instructed,
CVS checked-out pretty much everything the CVS repository carries. (Is
that supposed to
I have never tried to link C++ with GHC stuff; I know that it has caused
people difficulties in the past.
If someone who has got it working cares to write up some notes on what
to do, I'll gladly incorporate them in the GHC users guide. From what
Koen says, maybe it's possible!
Simon
|
In local.glasgow-haskell-users, you wrote:
I'm trying to compile the latest version of GHC from CVS. I followed
the instructions on GHC's web page and everything worked just fine.
But when I updated the sources with cvs update -dP as instructed,
CVS checked-out pretty much everything the CVS
Good morning!
Thanks very much for your help... Compiling everything with cygwin c++-2 /
gcc-2 works fine for me.
| I'm trying to link ghc object files with mingw's
| g++/ld...
We have used the g++-2 compiler that you can get with Cygwin
and it seems to work fine. (mingw-g++ and the
Volker Stolz writes:
Where did you find those instructions?
At http://haskell.cs.yale.edu/ghc/docs/latest/html/building/sec-cvs.html:
| 2.4. Updating Your Source Tree
|
| It can be tempting to cvs update just part of a source tree to bring in
| some changes that someone else has made, or
Alastair: Thanks a lot for the detailed reply! I'll take a look at the
build again; maybe I can get this problem fixed after all.
The attached diff (about to be committed) seems to fix the problem.
--
Alastair? gc-3.00
? distrib/html/old_index.html
? lib/Foreign/GreenCard.p_hi
?
I'm trying to compile the latest version of GHC from CVS. I followed
the instructions on GHC's web page and everything worked just fine.
But when I updated the sources with cvs update -dP as instructed,
CVS checked-out pretty much everything the CVS repository carries.
Sorry about that, the
Alastair Reid writes:
The attached diff (about to be committed) seems to fix the problem.
It does indeed -- thank you very much for your help!
One problem remains, though: When I build GHC from the top-level
directory, the build process does get the order right. It tries to
build
Simon Marlow writes:
CVS doesn't really support the structure of our source tree very
well.
Actually, it does. ;-)
The problem is that »ghc«, »green-card«, »hood« et al. are
subdirectories of »fptools«, that's why »cvs update -d« retrieves them
automatically. I guess a more appropriate
In local.glasgow-haskell-users, you wrote:
| 2.4. Updating Your Source Tree
| It can be tempting to cvs update just part of a source tree to bring in
| some changes that someone else has made, or before committing your own
| changes. This is NOT RECOMMENDED! [...]
|
| So, to avoid a lot of
Volker Stolz writes:
[STABLE branch]
Does the »STABLE« branch contain the meta-haskell extensions already?
Because this was the reason I wanted to run the CVS version in the
first place. :-)
Oh, and I have news: The build does not work yet, unfortunately. It
fails here:
|
The problem is that ghc, green-card, hood et al. are
subdirectories of fptools, that's why cvs update -d retrieves them
automatically. I guess a more appropriate repository layout would be
_flat_, like this:
/cvs --+
|
+-- CVSROOT
|
+--
Simon Marlow writes:
We could just rearrange the repository in place, and everything would
still work, right?
It's not quite that easy, unfortunately. If you want to retain the
files's version history (and I guess you would), then you have to move
the directories around in the CVS
Simon Marlow [EMAIL PROTECTED] writes:
/cvs --+
|
+-- CVSROOT
|
+-- fptools
|
+-- ghc
|
+-- libraries
|
+-- hslibs
|
Simon Marlow writes:
We could just rearrange the repository in place, and
everything would
still work, right?
It's not quite that easy, unfortunately. If you want to retain the
files's version history (and I guess you would), then you have to move
the directories around in the
The hsc2hs way of handling header files does not fit well with what is
described by the FFI spec, making it difficult for non-GHC implementations
to use .hsc files. Typical .hsc files may contain several #include
lines, which turn into OPTIONS -#include pragmas. The portable way is to
specify
18 matches
Mail list logo
