Closed Bug 99072 Opened 23 years ago Closed 23 years ago

Always set 'CPU_ARCH=x86'

Categories

(NSS :: Build, defect, P1)

3.3.1
All
NetBSD
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: taya, Assigned: wtc)

Details

Attachments

(1 file, 1 obsolete file)

In 'security/coreconf/NetBSD.mk', CPU_ARCH is always set to x86.
Attached patch suggested fix (obsolete) — Splinter Review
Status: UNCONFIRMED → NEW
Ever confirmed: true
Status: NEW → ASSIGNED
Priority: -- → P1
Target Milestone: --- → 3.3.2
Version: unspecified → 3.3.1
Could you tell me what 'uname -m' and 'uname -p' on some common architectures for NetBSD?
From uname(8) -p print the machine processor architecture name. -m print the machine hardware name. e.g. On NetBSD/i386% uname -p i386 % uname -m i386 On NetBSD/cobalt(little endian mips) % uname -p mipsel % uname -m cobalt On NetBSD/mac68k % uname -p m68k % uname -m mac68k
Thank you for the info on the -p and -m options of uname. I will propose a simpler patch, based on the fact that 'uname -p' and 'uname -m' both return "i386" on NetBSD/i386. I think we don't need to add -D$(CPU_ARCH), although I will keep -Di386 for backward compatibility.
Attachment #48864 - Attachment is obsolete: true
Comment on attachment 56076 [details] [diff] [review] Proposed patch. Please review and test it. I have no netbsd box but it looks good. r=cls
Attachment #56076 - Flags: review+
Fix checked in on the tip and NSS_3_3_BRANCH of NSS. I also moved the NSS_CLIENT_TAG. Taya, please verify that the fix works for you. I think this is mostly a cosmetic change because NSS is not really using CPU_ARCH but it is wrong to define -Di386 for all architectures :-)
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
I could build mozilla with this patch & worked fine. veified.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: