From: Ken Coar Date: Sun, 27 Sep 1998 17:36:12 +0000 (+0000) Subject: Add the AIX compiler bug to the FAQ. X-Git-Tag: 1.3.3~7 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=2e11057c8ef16b8c9730a1b9eefd2b378180fb73;p=apache Add the AIX compiler bug to the FAQ. PR: 2312, 2534, 2664, 2853, 3042 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@82169 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/misc/FAQ.html b/docs/manual/misc/FAQ.html index 485759e7ed..b742e1050e 100644 --- a/docs/manual/misc/FAQ.html +++ b/docs/manual/misc/FAQ.html @@ -14,7 +14,7 @@

Apache Server Frequently Asked Questions

- $Revision: 1.129 $ ($Date: 1998/09/17 14:14:52 $) + $Revision: 1.130 $ ($Date: 1998/09/27 17:36:12 $)

The latest version of this FAQ is always available from the main @@ -296,6 +296,8 @@

  • How do I submit a patch to the Apache Group?
    • +
  • Why am I getting "Expected </Directory> + but saw </Directory>" when I try to start Apache?
    • @@ -2277,30 +2279,35 @@ let you apply certain attributes against collections of files or resources in very flexible ways - for example, all .gif and .jpg files under any "images" directory could be written as /.*\/images\/.*[jpg|gif]/. - -

    The best overview around is probably the one which comes with +

    +

    + The best overview around is probably the one which comes with Perl. We implement a simple subset of Perl's regexp support, but it's still a good way to learn what they mean. You can start by - going to the CPAN - page on regular expressions, and branching out from there. - + going to the + CPAN page on regular expressions, and branching out from there. +

  • I'm using gcc and I get some compilation errors, what is wrong? -

    GCC parses your system header files and produces a modified subset which +

    + GCC parses your system header files and produces a modified subset which it uses for compiling. This behaviour ties GCC tightly to the version of your operating system. So, for example, if you were running IRIX 5.3 when you built GCC and then upgrade to IRIX 6.2 later, you will have to rebuild GCC. Similarly for Solaris 2.4, 2.5, or 2.5.1 when you upgrade to 2.6. Sometimes you can type "gcc -v" and it will tell you the version of the operating system it was built against. +

    If you fail to do this, then it is very likely that Apache will fail to build. One of the most common errors is with readv, writev, or uio.h. This is not a bug with Apache. You will need to re-install GCC. +

  • @@ -2313,33 +2320,55 @@ it covers the directory you are trying to use the .htaccess file in. This is normally accomplished by ensuring it is inside the proper Directory container. +

  • How do I submit a patch to the Apache Group?

    - The Apache Group encourages patches from outside developers. There are 2 main "types" - of patches: small bugfixes and general improvements. Bugfixes should be sent to the + The Apache Group encourages patches from outside developers. There are 2 + main "types" + of patches: small bugfixes and general improvements. Bugfixes should be + submitting using the Apache bug report page. - Improvements, modifications and additions should follow these instructions. + Improvements, modifications, and additions should follow the instructions + below. +

    In general, the first course of action is to be a member of the - new-httpd@apache.org mailing list. This indicates to the Group that - you are closely following the latest Apache developments. Your patch file should be - generated using either 'diff -c' or 'diff -u' against the - latest CVS tree. To submit your patch, send Email to new-httpd@apache.org - with a Subject: line that starts with [PATCH] and + new-httpd@apache.org mailing list. This indicates to the Group + that + you are closely following the latest Apache developments. Your patch file + should be + generated using either 'diff -c' or + 'diff -u' against the + latest CVS tree. To submit your patch, send email to + new-httpd@apache.org + with a Subject: line that starts with [PATCH] and includes a general description of the patch. In the body of the message, the - patch should be clearly described and then included at the end of the message. - If the patch-file is long, you can note a URL to the file instead of the file - itself. Use of MIME enclosures/attachments should be avoided. + patch should be clearly described and then included at the end of the + message. + If the patch-file is long, you can note a URL to the file instead of the + file itself. Use of MIME enclosures/attachments should be avoided. +

    - Be prepared to respond to any questions about your patches and possibly defend + Be prepared to respond to any questions about your patches and possibly + defend your code. If your patch results in a lot of discussion, you may be asked to submit an updated patch that incorporate all changes and suggestions. +

    +
    +
    • +
  • Why am I getting "Expected + </Directory> but saw </Directory>" when + I try to start Apache? +

    + This is a known problem with certain versions of the AIX C compiler. + IBM are working on a solution, and the issue is being tracked by + problem report #2312. +

    • -