Problem with little endian / big endian on Sparc/Linux

VERIFIED FIXED

Status

P3
minor
VERIFIED FIXED
21 years ago
20 years ago

People

(Reporter: thorsten, Assigned: ramiro)

Tracking

1998-03-31
x86
Linux

Details

(Reporter)

Description

21 years ago
Created by Thorsten Heit (thorsten@wurzelausix.cs.uni-sb.de) on Wednesday, April 8, 1998 7:09:13 AM PDT
Additional Details :
I do not know what problem could arise, but before
trying it I installed the following patch to remove
some compiler warning about redefining symbols:

(only seen on Sparc/Linux which is a big endian machine,
not on x86/Linux)

--- ns/include/mcom_db.h.orig   Wed Apr  8 16:01:41 1998
+++ ns/include/mcom_db.h        Wed Apr  8 16:02:09 1998
@@ -420,8 +420,10 @@
 /*
  *    Why you would want to override the system defines?
  */
+#if !defined(__sparc__)
 #if BYTE_ORDER != LITTLE_ENDIAN
 #define BYTE_ORDER LITTLE_ENDIAN
+#endif
 #endif
 #endif
--- ns/dbm/include/mcom_db.h.orig       Tue Mar 31 04:05:30
1998
+++ ns/dbm/include/mcom_db.h    Wed Apr  8 16:06:07 1998
@@ -398,8 +398,10 @@
 __END_DECLS

 #ifdef linux
+#if !defined(__sparc__)
 #if BYTE_ORDER != LITTLE_ENDIAN
 #define BYTE_ORDER LITTLE_ENDIAN
+#endif
 #endif
 #endif

Updated

20 years ago
Component: XFE

Updated

20 years ago
Assignee: nobody → {}

Updated

20 years ago
Assignee: {} → ramiro
(Assignee)

Updated

20 years ago
Status: NEW → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → FIXED

Comment 1

20 years ago
I beleive wtc@netscape.com recently checked in code to fix the endian problem on
sparc linux.

adding wtc@netscape.com to cc.
marking fixed.

Comment 2

20 years ago
Yes, I deleted all the offending code in the
two copies of mcom_db.h.

Updated

20 years ago
QA Contact: 3849

Comment 3

20 years ago
Set beppe@netscape.com as qa monitoring contact, thorsten@wurzelausix.cs.uni-
sb.de please verify on your end.

Updated

20 years ago
Status: RESOLVED → VERIFIED

Comment 4

20 years ago
presuming thorsten@wurzelausix.cs.uni-sb.de is happy with the fix, marking
verified.
You need to log in before you can comment on or make changes to this bug.