os-hpux/8357: Unable to use apsx to compile DSO module

[Kristin Simpson <ks...@go2vanguard.com>]

>Number:         8357
>Category:       os-hpux
>Synopsis:       Unable to use apsx to compile DSO module
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Tue Sep 18 10:30:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     ksimpson@go2vanguard.com
>Release:        apache 1.3.20
>Organization:
apache
>Environment:
HP-UX HPGroup B.11.00 A 9000/816 
>Description:
Tried compiling module using apxs this is what I get:
bash# ./apxs -c /var/apacheinst/mod_auth_pam.c
syntax error in file ./apxs at line 67, next 2 tokens "use strict"
syntax error in file ./apxs at line 74, next 2 tokens "my $CFG_TARGET "
syntax error in file ./apxs at line 99, next 2 tokens "my $opt_n "
syntax error in file ./apxs at line 119, next 2 tokens "my ("
syntax error in file ./apxs at line 192, next 2 tokens "my $rc"
syntax error in file ./apxs at line 195, next 2 tokens "1 and"
syntax error in file ./apxs at line 196, next 2 tokens "not $opt_q "
syntax error in file ./apxs at line 205, next 2 tokens "my ("
syntax error in file ./apxs at line 208, next 2 tokens "my ("
syntax error in file ./apxs at line 210, next 2 tokens "$var and"
./apxs has too many errors.

I have checked to make sure mod_so.so is installed which it is
bash# ./httpd -l
Compiled-in modules:
  http_core.c
  mod_env.c
  mod_log_config.c
  mod_mime.c
  mod_negotiation.c
  mod_status.c
  mod_include.c
  mod_autoindex.c
  mod_dir.c
  mod_cgi.c
  mod_asis.c
  mod_imap.c
  mod_actions.c
  mod_userdir.c
  mod_alias.c
  mod_access.c
  mod_auth.c
  mod_so.c <-*****
  mod_setenvif.c
suexec: disabled; invalid wrapper /var/apache/bin/suexec 

>How-To-Repeat:
Use the module out of the /src/module/example and try using apxs to compile it.

bash# ./apxs -c /var/apacheinst/mod_auth_pam.c
syntax error in file ./apxs at line 67, next 2 tokens "use strict"
syntax error in file ./apxs at line 74, next 2 tokens "my $CFG_TARGET "
syntax error in file ./apxs at line 99, next 2 tokens "my $opt_n "
syntax error in file ./apxs at line 119, next 2 tokens "my ("
syntax error in file ./apxs at line 192, next 2 tokens "my $rc"
syntax error in file ./apxs at line 195, next 2 tokens "1 and"
syntax error in file ./apxs at line 196, next 2 tokens "not $opt_q "
syntax error in file ./apxs at line 205, next 2 tokens "my ("
syntax error in file ./apxs at line 208, next 2 tokens "my ("
syntax error in file ./apxs at line 210, next 2 tokens "$var and"
./apxs has too many errors.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database 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!     ]