Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to build 389-admin on OSX #32

Closed
389-ds-bot opened this issue Sep 12, 2020 · 6 comments
Closed

Unable to build 389-admin on OSX #32

389-ds-bot opened this issue Sep 12, 2020 · 6 comments
Labels
closed: won't fix Migration flag - Issue

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/32


https://bugzilla.redhat.com/show_bug.cgi?id=739133

./Config fails with "grep: /usr//private/etc/apache2/httpd.conf: No such file
or directory"

The reason is that on OSX:

-D HTTPD_ROOT="/usr"

and...

-D SERVER_CONFIG_FILE="/private/etc/apache2/httpd.conf"

The correct location of httpd.conf is *not* HTTPD_ROOT + SERVER_CONFIG_FILE.
It's just SERVER_CONFIG_FILE.
@389-ds-bot 389-ds-bot added the closed: won't fix Migration flag - Issue label Sep 12, 2020
@389-ds-bot 389-ds-bot added this to the 389-admin,console FUTURE milestone Sep 12, 2020
@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-01-10 06:05:46

batch update to FUTURE milestone

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2012-08-14 19:56:22

set default ticket origin to Community

@389-ds-bot
Copy link
Author

Comment from nkinder (@nkinder) at 2012-08-28 04:14:25

Added initial screened field value.

@389-ds-bot
Copy link
Author

Comment from rmeggins (@richm) at 2017-02-11 22:56:08

Metadata Update from @richm:

  • Issue set to the milestone: 389-admin,console FUTURE

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-05 07:33:48

We do not plan to fix this issue.

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2017-04-05 07:33:51

Metadata Update from @Firstyear:

  • Custom field component reset (from Unknown)
  • Custom field reviewstatus adjusted to new (was: Needs Review)
  • Issue close_status updated to: wontfix
  • Issue status updated to: Closed (was: Open)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed: won't fix Migration flag - Issue
Projects
None yet
Development

No branches or pull requests

1 participant