Joshua,
Thanks again for your tips.
After a complete installation of perl, mod_perl, and Apache (details below), I am
ALMOST there
... :
after starting apache/1.3.9 (mod_perl/1.21), I can see a BLACK page with many links in
some
kind of not quite orderly table layout (rather than plain script as of yesterday). It
seems
that asp is there, yet not quite, since the looks on many other pages are wrong and
there is no
asp functionality.
As for configuration, I have the following in the httpd.conf file:
<Directory />
Options FollowSymLinks
AllowOverride All
</Directory>
<Location /ASP/>
SetHandler perl-script
PerlHandler Apache::ASP
# PerlSerVar Global /tmp
</Location>
for now, the httpd directory is located at: /usr/local/apache/htdocs/ with Joshua's
site/eg/
files at eg directory under htdocs.
I have to comment out PerlSetVar, otherwise, httpd won't start and error msg says
"invalid
command PerlSetVar, perhaps mispelled or module not supported".
So, questions are:
Is my mod_perl and asp really working? how can I tell?
why can't I use PerlSetVar?
what's implication of the skipped test when I install mod_perl? Are they needed?
Thanks,
Don
----------here's what I did: ----------------------
After reading somewhere about possible broken perl from RedHat package, I reinstalled
a fresh
Perl_5.00503 (also have to include six other modules, including libwww, mime-base64,
etc.).
in CPAN.pm, a few tests (request, perlrunrx, cookie, and module) were skipped and one
failed
(sandwich) after I did "install Bundle::Apache".
I then went ahead and installed mod_perl with (perl Makefile.PL USE_APACI=1
EVERYTHING=1, make,
make install, make test). It again reported a few failed tests as above.
I went on to install Apache, and ASP.pm. and this time, it seemed to worked, although
mod_perl
could still be faulty, since I don't quite know how to test it yet.
Oh, one more thing: silly but I definetely overlooked, and if not for someone else
email post,
I would never know: I have to find where the newly compiled httpd program is upon
compilation
and installtion, and remember to use the new one rather than the old one as defined by
default
path.
Joshua Chamas wrote:
> don Wang wrote:
> >
> > Joshua, (and all)
> >
> > Thanks very much for your reply. Following your suggestions, I have tried
> > again this morning, to no avail.
> >
> > I am sure I missed something obvious here. although serveral people have
> > mentioned compiling mod_perl STATICALLY with Apache, I have not found clear
> > instructions on EXACTLY how to do it. Following the 10-step instruction at
> > http://perl.apache.org/guide/install.html, still several problem came up.
> >
>
> If you avoid doing ...
>
> The DSO mechanism is provided by Apache's mod_so.c which needs to be compiled
> into the httpd program. This is automatically done when DSO is enabled for
>module
> mod_xxx via configure --enable-module=xxx or by explicitly adding mod_so via
>configure
> --enable-module=so.
>
> you will get a static build. You need to make install mod_perl, before
> you make test mod_perl. After make test works, then copy your new httpd
> to your final home /usr/local/apache/...
>
> Once you have the new server copied over it should have the mod_perl
> tag in the header too.
>
> -- Joshua
> _________________________________________________________________
> Joshua Chamas Chamas Enterprises Inc.
> NodeWorks >> free web link monitoring Huntington Beach, CA USA
> http://www.nodeworks.com 1-714-625-4051
--
***************************************************************
[EMAIL PROTECTED]
Unified Access Communications, Inc.
200 Lincoln Street, Suite 201
Boston, MA 02111
phone: (617) 695-0137, ext. 13
fax: (617) 695-0984
***************************************************************
begin: vcard
fn: Don Wang
n: Wang;Don
org: Unified Access Communications
adr: 200 Lincoln Street;;;Boston;MA;02111;USA
email;internet: [EMAIL PROTECTED]
tel;work: 617-695-0137 x 13
tel;fax: 617-695-0984
note: http://www.uac.com
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard
