Closed
Bug 34759
Opened 26 years ago
Closed 25 years ago
NSPR's Makefiles don't honor configure's CC/CXX assignments
Categories
(NSPR :: NSPR, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: dogcow, Assigned: cls)
Details
do `CC="gcc -L/usr/pkg/lib -R/usr/pkg/lib -I/usr/pkg/include" CXX="g++
-L/usr/pkg/lib -R/usr/pkg/lib -I/usr/pkg/include" ./configure; gmake` at the
TLD.
Watch NSPR utterly fail to honor the CC/CXX assignments. (Manually doing `gmake
CC="gcc -blahblahblah"` works as usual.)
It's another symptom of the non-configure build behavior. The only way to
override the default variables in the classic build is to pass them on the make
command line or (untested) to put them in nsprpub/config/my_overrides.mk. We
could override CC in that file but then we'd always override nspr's default
settings for those variables. At that point, you might as well just use
--enable-nspr-autoconf.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 3•26 years ago
|
||
The report is doing the configure build.
He says:
CC="..." CXX="..." ./configure; gmake
Ok, here's the source of confusion. Is "TLD" mozilla/ or mozilla/nsprpub ?
Comment 5•26 years ago
|
||
Aha. I thought he meant mozilla/nsprpub, hence
the confusion.
dogcow, can you clear up the ambiguity here and then let us know if the problem
still occurs if you use --enable-nspr-autoconf when building mozilla?
Target Milestone: --- → M20
Updated•25 years ago
|
Target Milestone: M20 → ---
I think that introducing additional variables to nspr_my_*.mk to conditionally
override CC/CXX would cause more problems than it could solve. The recommended
solution is to use --enable-nspr-autoconf which already supports this feature.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•