Received: (qmail 1411 invoked by uid 2012); 17 May 1999 17:48:06 -0000 Message-Id: <19990517174806.1410.qmail@hyperreal.org> Date: 17 May 1999 17:48:06 -0000 From: Chris Moolenschot Reply-To: chris@hal.co.za To: apbugs@hyperreal.org Subject: nbdm.h not found compiling on Redhat 6.0 X-Send-Pr-Version: 3.2 >Number: 4431 >Category: general >Synopsis: nbdm.h not found compiling on Redhat 6.0 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: closed >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Mon May 17 10:50:00 PDT 1999 >Last-Modified: Tue Jun 29 06:57:21 PDT 1999 >Originator: chris@hal.co.za >Organization: >Release: 1.3.6 >Environment: Redhat 6.0 ecgs-2.91.66 >Description: When I attempted to compile Apache on a RedHat 6.0 system, the compiler complained that it could not find 'ndbm.h' included in src/modules/standard/mod_auth_dbm.c When I looked for the file I found it is a glibc header and it was in /usr/include/db1/ which is not in the include search path. So I changed #include to #include and it compiled. I assume this is because RH uses glibc2.1 which might have had a bit of a layout change, and that no-one has reported this because RH comes with an Apache rpm (which coincidentally does not have DSO support). I have not tested the auth_dbm module after this fix (I have no idea how to). >How-To-Repeat: I assume this will happen when compiling apache with DSO and the auth_dbm module on a Redhat 6.0 system. This should do it: ./configure --enable-module=most --enable-shared=max && make >Fix: Change line 77 in src/modules/standard/mod_auth_dbm.c from #include include to #include and recompile >Audit-Trail: State-Changed-From-To: open-closed State-Changed-By: rse State-Changed-When: Tue Jun 29 06:57:20 PDT 1999 State-Changed-Why: This is fixed for Apache 1.3.6. Thanks for your feedback. >Unformatted: [In order for any reply to be added to the PR database, ] [you need to include in the Cc line ] [and leave the subject line UNCHANGED. This is not done] [automatically because of the potential for mail loops. ] [If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request ] [from a developer. ] [Reply only with text; DO NOT SEND ATTACHMENTS! ]