Currently, by default the bits of a 32-bit build and a 64-bit build on a Solaris SPARC box are put into seperate directories, e.g.

$WS_HOME/build/solaris-sparc
$WS_HOME/build/solaris-sparcv9

To have a properly working 32 or 64 bit j2se install (i.e. one where java -d32 and java -d64 will find the desired data model binary when started from the alternate one), the 64-bit build must be overlayed on top of the 32-bit build. For the end users, this is accomplished by installing the 64-bit components after the 32-bit components (the 32 and 64 bit components are separate downloads).

It would be convenient for developers to have a single build target that built 32 and 64 bit binaries in such a way that the -d<bitness> flag worked. One drawback to such a target is that it does not correspond to a (current) customer download build.