I think we can get rid of CC32 and CC64 now.
They were introduced when AMD64 support was still experimental
in Sun Studio and we needed to use a pre-release version to
build the amd64 bits.
So basically we can now assume that CC points to the C compiler
for both 32-bit and 64-bit and it's in the PATH.
Laca
On Fri, 2007-03-09 at 15:25 +0700, Doug Scott wrote:
> Hi,
> I have just started a fresh build of JDS on snv_59 developer version.
> This version places links for the C compiler in /usr/bin. While this is
> a good thing, if you use the defaults to install CBE, it cases problems
> when doing a JDS build.
>
> What causes the build to fail is the following piece of code in many
> spec files. It puts the directory where it finds the compiler at the
> beginning of the PATH environment variable. Therefore rather than using
> the CBE tools (such as make, gettext etc) installed in /opt/jdsbld/bin,
> the build will use standard Solaris tools from /usr/bin.
>
> export CC=${CC64:-$CC}
> ccdir=`dirname $CC`
> export PATH=$ccdir:$PATH
>
> The following build error (SUNWTiff.spec) is the result of using
> /usr/bin/make rather than /opt/jdsbld/bin/make (GNU make).
>
> + make -j2
> make: Warning: Ignoring DistributedMake -j option
> make: Fatal error: No dmake max jobs argument after -j flag
> Bad exit status from /var/tmp/pkgbuild-jdsbuild/pkgbuild-tmp-2.11823
> (%build)
>
> I am proposing 3 options to fix this
>
> 1) Remove ccdir from *.spec files. Is it still needed???
>
> 2) Do not change the path if ccdir = /usr/bin
> [ "$ccdir" != "/usr/bin" ] && export PATH=$ccdir:$PATH
>
> 3) Move ccdir to be after /opt/jdsbld/bin (This assumes that CBE is
> located at /opt/jdsbld - maybe bad)
> export PATH="${PATH/\/opt\/jdsbld\/bin://opt/jdsbld/bin:$ccdir:}"
>
> Doug
