Closed
Bug 194083
Opened 22 years ago
Closed 1 year ago
Patch for the file mozilla/security/coreconf/QNX.mk
Categories
(NSS :: Build, defect, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: amardare, Unassigned)
References
()
Details
Attachments
(1 file)
1.17 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Not applicable
I attached a patch for the file
mozilla/security/coreconf/QNX.mk
It contains photon ( qnx ) specific changes and should not affect the other
platforms.
It allows you to succesfully build the security related files on a QNX 6.2.1
system.
Reproducible: Always
Steps to Reproduce:
N/A
Actual Results:
N/A
Expected Results:
N/A
It contains photon ( qnx ) specific changes and should not affect the other
platforms.
It allows you to succesfully build the security related files on a QNX 6.2.1
system.
Updated•22 years ago
|
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Comment 2•22 years ago
|
||
Comment on attachment 114898 [details] [diff] [review]
Patch for the file mozilla/security/coreconf/QNX.mk
1. Do you still want to support building with gcc?
2. Does QNX run on ppc architecture? If it does, we should
keep the ifeq ($(OS_TEST),ppc) test.
>1. Do you still want to support building with gcc?
No, qcc should always be used.
>2. Does QNX run on ppc architecture? If it does, we should
>keep the ifeq ($(OS_TEST),ppc) test.
We tried with the mips instead. You can keep the ppc line also, it doesn't hurt.
Thank you.
Updated•22 years ago
|
Priority: -- → P1
Target Milestone: --- → 3.8
Comment 4•22 years ago
|
||
Question: can you use the -Vgcc_ntox86 flag on non-x86 CPUs
(such as ppc)?
Comment 5•22 years ago
|
||
Question: the definitions of CCC and CXX are different:
CCC=qcc -Vgcc_ntox86
CXX=qcc -lang-c++ -Vgcc_ntox86
Which one is correct? (By the way, NSS does not use the
CXX variable.)
Comment 6•22 years ago
|
||
Remove target milestone of 3.8, since these bugs didn't get into that release.
Target Milestone: 3.8 → ---
Comment 7•20 years ago
|
||
This bug was last touched more than 2.5 years ago, and has no target. Marking P2.
Priority: P1 → P2
Updated•19 years ago
|
QA Contact: wtchang → build
http://www.qnx.com/developers/docs/qnx_6.1_docs/neutrino/utilities/q/qcc.html
no x86 shouldn't be used for non x86
-V [version,]target
The version number (optional) and the target name. If you specify version, qcc looks in ${QCC_CONF_PATH}/version for configuration files.
The targets include:
* gcc_ntox86
* gcc_ntomipsle
* gcc_ntomipsbe
* gcc_ntoppcbe
For a list of supported targets, specify -V?.
and the two defs are fine, -lang-c++ only applies to c++ files, now given that nss doesn't currently have c++ files that means it can use the non -land-c++ line, however given that bug 171084 (filed before this bug) talks about compiling w/ a c++ compiler, having the right env vars available would be a good idea, because otherwise this poor port would die when you switched.
Updated•3 years ago
|
Severity: normal → S3
Comment 9•3 years ago
|
||
The bug assignee is inactive on Bugzilla, and this bug has priority 'P2'.
:beurdouche, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: wtc → nobody
Status: ASSIGNED → NEW
Flags: needinfo?(bbeurdouche)
Comment 10•2 years ago
|
||
We have modified the bot to only consider P1 as high priority, so I'm cancelling the needinfo here.
Flags: needinfo?(bbeurdouche)
Updated•1 year ago
|
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•