--On Sunday, November 02, 2003 22:26:40 +0100 Peter Eisentraut <[EMAIL PROTECTED]> wrote:

Larry Rosenman writes:

Since peter objects to my methods, what is an ACCEPTABLE way to detect
the 7.1.3UP3 compiler?

One POSSIBLE way to do this properly is to write a test that

1) Uses $CC, $CFLAGS, and related variables rather than hardcoding 'cc

2) Names any test files conftest.*, so configure cleans up automatically.

3) Doesn't execute any compiled programs.  See the __FAST_MATH__ test for
   an example.

However, I still think that we should not bother testing for this.
Considering that the condition first occurred a couple of months ago and
is already fixed, this isn't a big issue.  Think about what would happen
if we had to develop and maintain fixes for every buggy GCC compiler every
The problem is MOST people will **NOT** be able to get the fixed compiler
as it's on the Upgrade Pack path (PAY FOR), and **NOT** the Maintenance
Pack path (Free).

I'll try and write the patch as you suggest.

Peter Eisentraut   [EMAIL PROTECTED]

-- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED] US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to