Re: Checking for GCC 4

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> > And I'm not sure which is more fragile, user input or coded checks.

> Best would be functional and safe automatic checks ;)

Ideally, I agree with you.  But in reality, the ideal pretty much never
happens.

> The worst are semi-thought out automatic checks silently failing and
> producing bogus results. A GCC version check definitely from of this
> class, due to the reasons I gave in my initial reply.

A bug is a bug.

I don't see a significant difference between something that (apparently)
works that is based on a version number check, an OS version check, or a
feature test.

H


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux