From: "Martin S. Weber" <Ephaeton@gmx.net>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] OCamlon 64 Bit-Sun compiled as 32-Bit
Date: Sat, 16 Sep 2006 22:59:04 +0200 [thread overview]
Message-ID: <20060916205904.GC6039@circe.entropie.net> (raw)
In-Reply-To: <20060916200056.GA6205@first.in-berlin.de>
Hoi & ugh.
On Sat, Sep 16, 2006 at 10:00:56PM +0200, Oliver Bandel wrote:
> On Sat, Sep 16, 2006 at 09:55:45PM +0200, Martin S. Weber wrote:
> > (...)
> > See if you can pass a CPPFLAGS=-m64 to your compiler (gcc option,
> > if you're using sunpro pass the appropriate flag to the compiler
> > to enable/force 64bit compiling)...
> [...]
>
> I doubt setting gcc-Flags make sense, if this is not a flag,
> that the ./configure-script inthe sources-directory accepts.
My fault. I'm used to autoconf scripts, and setting the environment
variable 'CPPFLAGS' (C pre processor flags) will pass additional
flags to the C compiler. This doesn't seem to be an autoconf build
though, sorry.
What I said about code generation and the default setting of your
machine's host compiler remains true :)
> (...)
> At least theconfigure-script did not find out that the machine
> is a 64-Bit's machine. So at least the config-script could be
> changed. (Or there is an 64-Bit-option, which I didn't checked,
> because I thought, it will find it out by itself.
It did not find an 64bit env because your compiler by default
doesn't offer a 64bit env :)
Good luck ...
-Martin
next prev parent reply other threads:[~2006-09-16 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-16 18:55 Oliver Bandel
2006-09-16 19:55 ` [Caml-list] " Martin S. Weber
2006-09-16 20:00 ` Oliver Bandel
2006-09-16 20:59 ` Martin S. Weber [this message]
2006-09-16 22:55 ` John Carr
2006-09-17 0:55 ` Shawn W
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060916205904.GC6039@circe.entropie.net \
--to=ephaeton@gmx.net \
--cc=caml-list@inria.fr \
--cc=oliver@first.in-berlin.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).