Closed
Bug 75734
Opened 24 years ago
Closed 24 years ago
configure fails if "directory" does not exist
Categories
(Directory :: LDAP XPCOM SDK, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.3
People
(Reporter: robbe, Assigned: cls)
References
Details
Attachments
(2 files)
881 bytes,
patch
|
Details | Diff | Splinter Review | |
883 bytes,
patch
|
Details | Diff | Splinter Review |
(May I say that calling a directory "directory" is kinda clumsy, even if it
makes some sense with LDAP <g>.)
Anyways, if one wants to builds in a directory seperate from the source (e.g.
"mkdir _build_; ../configure"), "directory" is not yet present. An "mkdir
directory/c-sdk" that is attempted at the end of the configure script therfore
has to fail.
if test ! -d "directory"; then
mkdir "directory"
fi
should be inserted before that.
If not already the case, one or two Unix tinderboxen should be modified to build
in a seperate build-dir, so these errors are catched quickly.
Updated•24 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Um, most of the tinderboxes (ports anyway) build in a separate obj-tree as do I
and I've never hit this error. Looking at configure.in, directory/xpcom would
have been created as a result of the toplevel configure run so it would already
exist when running directory/c-sdk/ldap's configure. What source tree are you
using?
This turned out to be a fallout from trying to build psm2 (following
instructions in bug 75018). Forcing my tree back to trunk level killed all
problems. user error, marking INVALID.
Sorry for the bother
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → INVALID
Status: VERIFIED → REOPENED
Component: Build Config → LDAP XPCOM SDK
Product: Browser → Directory
Resolution: INVALID → ---
Found out that building PSM2 in a separate object dir can cause this. I.e.
mkdir build_psm2
cd build_psm2
../configure --enable-modules=psm2
will give this error. Reopening and moving to Directory.
Reassigning to dmose as per message <9dhove$mrm1@secnews.netscape.com>.
Assignee: cls → dmose
Status: REOPENED → NEW
Comment 6•24 years ago
|
||
cls', is robbe's proposed fix the right one? It would work, but is part of the
problem really the fact that the ldap stuff isn't part of what client.mk
considers a "module"? Any opinions about the best thing to do here?
Status: NEW → ASSIGNED
Updated•24 years ago
|
Target Milestone: --- → mozilla0.9.3
Comment 9•24 years ago
|
||
cls: is BUILD_MODULES intended to take precedence over an explicitly specified
--enable-ldap?
Assignee | ||
Comment 10•24 years ago
|
||
Well, --enable-ldap is currently a no-op, right? The only way BUILD_MODULES
gets set to anything other than "all" is via --enable-modules. If we're
specifying a standalone module to build and we want to build ldap as well, then
we should specify it in the standalone modules list.
Comment 12•24 years ago
|
||
a= asa@mozilla.org for checkin to the trunk.
(on behalf of drivers)
Assignee | ||
Comment 13•24 years ago
|
||
Patch has been checked in.
Status: NEW → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•