Simon Riggs wrote On 12/02/06 06:50,:

Robert, Can you throw any light on this? Or do you have any further
comments on the docs?
Here is what the dtrace man page says about the -32 and -64 flags:

        The D compiler produces programs using the  native  data
        model  of  the  operating system kernel. You can use the
        isainfo -b command to determine  the  current  operating
        system  data  model.  If  the  -32  option is specified,
        dtrace forces the D compiler  to  compile  a  D  program
        using the 32-bit data model. If the -64 option is speci-
        fied, dtrace forces the D compiler to compile a  D  pro-
        gram using the 64-bit data model. These options are typ-
        ically not required as dtrace selects  the  native  data
        model  as  the default. The data model affects the sizes
        of integer types and other language properties.  D  pro-
        grams  compiled for either data model can be executed on
        both 32-bit and 64-bit kernels. The -32 and -64  options
        also determine the ELF file format (ELF32 or ELF64) pro-
        duced by the -G option.

In my testing on the 64 bit Solaris kernel building a 64-bit Postgres binary, if DTRACEFLAGS="-64" is not passed to the configure script, compilation will fail when dtrace is invoked. Based on my observation, dtrace will default to 32-bit, but for 64-bit you have to be explicit with DTRACEFLAGS="-64"

Simon, thanks for you help with the doc patch!


---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Reply via email to