Bug #41080 Wrong compiler is used in RHEL3/ia64 specific RPMs

• Submitted: 27 Nov 2008 20:00
• Modified: 13 Jan 2009 12:16
• Reporter: Joerg Bruehe
• Status: Closed
• Category: MySQL Server: Packaging
• Severity: S3 (Non-critical)
• Version: 5.0, 5.1
• OS: Linux (ia64, RHEL 3)
• Assigned to: Jonathan Perkin
• CPU Architecture: Any

[27 Nov 2008 20:00] Joerg Bruehe

Description:
Found while doing a test to work on bug#26760 :

"Specific" RPMs for RHEL3/ia64 (host rx2620c) are currently built using gcc,
but should use icc.

Most probably, this is caused by these lines in file "icc9-ia64-profile":

# 2008-06-18 (jperkin) - remove these, they conflict with PlatformData.pm
# and break gcc builds
#xLDFLAGS="-static-intel -static-libgcc"
#CC="icc $xLDFLAGS"
#CXX="icpc $xLDFLAGS"
...

Without the setting of CC, there is no reason for the build to use icc, so it defaults to gcc.
OTOH, that "icc-ia64-profile" is sourced from "path-for-rx2620c" which was last modified on 2007-Dec-17, so that hasn't changed recently.

The last correct RPM builds (using icc) were done on May 23 (5.0.62) and June 17 (5.1.25-rc),
the first wrong (using gcc) on June 19 (5.0.64) and July 3 (5.1.26-rc).

How to repeat:
Check the log files in the archive.

Suggested fix:
Not sure.

I don't see a reason to source "icc-ia64-profile" from "path-for-rx2620c", thios seems wrong.
IMO, we should always call the ICC settings explicitly, like we do when building specific RPMs.