User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041013 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a5) Gecko/20041013 according to one of our s390 developers the s390x platform does define the s390, too. Therefore I suggest the attached patch to avoid problems. Reproducible: Always Steps to Reproduce: .
Attachment #162058 - Flags: review?(wchang0222)
Attachment #162058 - Flags: review?(wchang0222) → review+
wtc: thanks for review. Could you please check this in? It seems NSPR write-access is rare ;-)
Wolfgang, you should ask for the right to create bug as new, especially for when you enter bugs for the s390 arch. If wtc doesn't answer, try to ping some other of the NSPR peers. But I too think it will be a bit uneasy to get a patch inside NSPR :-)
Status: UNCONFIRMED → NEW
Ever confirmed: true
Created attachment 162522 [details] [diff] [review] Patch as checked in This is what I actually checked in. I simply test for __s390x__ before __s390__. Just a matter of personal preference.
Attachment #162058 - Attachment is obsolete: true
I checked in the patch on the NSPR trunk (NSPR 4.6) and NSPRPUB_PRE_4_2_CLIENT_BRANCH (post Mozilla 1.8 Alpha 4).
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → 4.6
thanks, that looks nicer ;-)
Comment on attachment 162522 [details] [diff] [review] Patch as checked in Want this on the branches for the distributors that care about s390(x).
Comment on attachment 162522 [details] [diff] [review] Patch as checked in a=shaver for our branchen.
14 years ago
Keywords: fixed-aviary1.0.4, fixed1.7.8
You need to log in before you can comment on or make changes to this bug.