Bug 480787
| Summary: | autoconf parameter --with-... --without-... | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] 389 | Reporter: | Mario Fetka <mario.fetka> | ||||
| Component: | Database - General | Assignee: | Noriko Hosoi <nhosoi> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Viktor Ashirov <vashirov> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 1.1.3 | CC: | edewata, rmeggins | ||||
| Target Milestone: | --- | Keywords: | VerifiedUpstream | ||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-12-07 16:55:26 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 543590 | ||||||
| Attachments: |
|
||||||
|
Description
Mario Fetka
2009-01-20 15:25:09 UTC
one additional requested extensin for the --with-.... is the that if you specifiy only -with-sasl it should work like --with-sasl=yes Can you provide a link to a gentoo document that explains the requirements of --with and --without? For pam, specifically, you can use --enable-pam-passthru or --disable-pam-passthru For sasl, specifically, the server requires the use of sasl - that is, --without-sasl will fail - instead of --with-sasl=yes, use no --with-sasl option at all - then it will attempt to find sasl in the system locations. yes and it is already used (http://tinyurl.com/yb8j5jv) there you can see in the src_configure section that gentoo has this nice functions called use_enabled use_with more details at: http://devmanual.gentoo.org/ebuild-writing/functions/src_compile/configuring/index.html and these functions will create for ex: $(use_with icu) will result in the configure switch --with-icu and this will not work with the actual design of the autoconf macros where it expects --with-icu=yes this request is to make it pssoble to have fort ex --with-icu. and now with the comming openldap support the gentoo user can decide if thx want tobuild with mozldap or with openldap So, to summarize: For all of the --with-XXX configure switches supported by directory server 1) if just --with-XXX is specified, it should imply --with-XXX=yes 2) --without-XXX should work, and should work exactly the same way as --with-XXX=no yes this is right this would really help Mario, the configure script has two types of options: feature and package (see configure --help). The features are configured using --enable/disable, but the packages are configured using --with/without. According to comment #5 we will make changes to the --with-XXX only (i.e. packages), but in your original bug description you also mention about disabling pam which is a feature, not a package. So to disable pam you will still need to use --disable-pam-passthru, not --without-pam-passthru. Will this work for you? Thanks. (In reply to comment #7) > Will this > work for you? Thanks. yes this will work it is absolutly ok ( i don't know how i came up with pam for the example ? ) greate thx Created attachment 401381 [details]
0001-Bug-480787-Autoconf-parameter-with-and-without.patch
The configure script has been modified such that the --with-XXX and --without-XXX switches will work as --with-XXX=yes and --with-XXX=no, respectively. If the package is required and none of the switches are specified, it will default to "yes".
The code that detects LDAPSDK and OpenLDAP conflicts has been updated. The help messages have been cleaned up.
To ssh://git.fedorahosted.org/git/389/ds.git
04a0bd9..682529e master -> master
commit 682529e7f8391744615b40a14852efd317936109
Author: edewata
Date: Fri Mar 19 19:25:48 2010 -0500
Fix Description: The configure script has been modified
such that the --with-XXX and --without-XXX switches will
work as --with-XXX=yes and --with-XXX=no, respectively.
If the package is required and none of the switches are
specified, it will default to "yes".
The code that detects LDAPSDK and OpenLDAP conflicts has
been updated. The help messages have been cleaned up.
Reviewed by: rmeggins (and pushed by)
|