|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Mail-Followup-To: rt@krbdev.mit.edu mail-copies-to: never From: "Ken Raeburn via RT" <rt-comment@krbdev.MIT.EDU> In-Reply-To: <rt-6565@krbdev.mit.edu> Message-ID: <rt-6565-31711.14.217773154978@krbdev.mit.edu> To: "'AdminCc of krbdev.mit.edu Ticket #6565'":;"'AdminCc of krbdev.mit.edu Ticket #6565'":;@MIT.EDU Date: Tue, 15 Sep 2009 02:36:15 +0000 (UTC) Reply-To: rt-comment@krbdev.MIT.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: krb5-bugs-bounces@mit.edu On Sep 14, 2009, at 21:45, Arlene Berry via RT wrote: > For krb5-1.7 all IA64 platforms are identified as little endian but > HP-UX is big endian. I wondered if there should be some startup-time sanity check of that, just to be safe. The current GCC sources indicate that it'll define __BIG_ENDIAN__ on big-endian IA64 targets. It may be good to add __BIG_ENDIAN__ and __LITTLE_ENDIAN__ to the list of macros we test for; certainly several GCC configurations seem to define one or the other for several processors that can go either way. I'll take a look.... Ken _______________________________________________ krb5-bugs mailing list krb5-bugs@mit.edu https://mailman.mit.edu/mailman/listinfo/krb5-bugs
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |