caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCamlon 64 Bit-Sun compiled as 32-Bit
Date: Sat, 16 Sep 2006 22:00:56 +0200	[thread overview]
Message-ID: <20060916200056.GA6205@first.in-berlin.de> (raw)
In-Reply-To: <20060916195545.GB6039@circe.entropie.net>

On Sat, Sep 16, 2006 at 09:55:45PM +0200, Martin S. Weber wrote:
> Moin Oliver,
> 
> On Sat, Sep 16, 2006 at 08:55:14PM +0200, Oliver Bandel wrote:
> > Hello,
> > 
> > in the project I'm working, I have todo Perl-Programming.
> > But in a free minute I compiled OCaml on the workstation.
> > The compilation was without problems, it seems.
> > 
> > But the ocaml-distri (3.09.2) compiled as 32-Bit.
> > I asked the admin, and he said, it's a 64-Bit workstation.
> > 
> 
> This doesn't mean the compiler is set to generate 64bit objects
> by default, iirc the solaris 8 boxes I worked on ran 64 bit on 
> 64 bit and nevertheless compiled stuff as 32bit. (yay).
> 
> 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.

I hope there is such an 64-Bit-option in the configure-script,
if not, I think such flags could yield problems.

> 
> I.e. no ocaml bug.
> 

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.


Ciao,
  Oliver



> Maybe have a look at (gcc: gcc -dumpspecs which should among many
> other things also tell you the default build/compile options...
> E.g. on my sparc64, gcc tells me ...
> 
> *cpp_arch:
> %{m32:%(cpp_arch32)} %{m64:%(cpp_arch64)} %{!m32:%{!m64:%(cpp_arch_default)}} 
> 
> (read as: passed m32? select cpp_arch32. passed m64? select cpp_arch64.
> passed neither m32 nor m64 ? select cpp_arch_default.)
> 
> ..and..
> 
> *cpp_arch32:
> 
> 
> *cpp_arch64:
> -D__arch64__
> 
> *cpp_arch_default:
> -D__arch64__
> 
> 
> )
> 
> Regards,
> 
> -Martin 


  reply	other threads:[~2006-09-16 20:00 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 [this message]
2006-09-16 20:59     ` Martin S. Weber
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=20060916200056.GA6205@first.in-berlin.de \
    --to=oliver@first.in-berlin.de \
    --cc=caml-list@inria.fr \
    /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).