Alfred M. Szmidt wrote:
Why not print a message if that bug is found instead of depending on
the architecture which surley will backfire, since you could be
running GNU/Linux or anything on such a machine.
It would be somewhat difficult to detect the bug, as it is by its very nature
random. In fact, it is never seen with gcc 4.2.4, despite the fact Sun
acknowledge it is a bug on Solaris - the upper 32-bit of a 64-bit register are
not set to 0 as they should be. So I'd rather warn the user. In any case, if
they build it on sun4v, it could be put on another sun4v machine, where the bug
does exist. (Sun will soon have a patch for it).
So is there a way I can check the architecture? Also, I would like to know if
the machine is sun4m, as that can not be upgraded to Solaris 10. Since Solaris
10 is the only supported version of Solaris, and earlier (sun4m) hardware can
not be upgraded, I would like to be able to test the architecture.
Any, that aside, how could I use the output of any arbitrary command, to return
something I can test on?
dave
_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf
