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