You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by allan <la...@inet.uni2.dk> on 2001/05/25 10:12:01 UTC

macintosh osX - mod_perl install problems

hello

this might be mac-specific ...
can anyone help with this - ive looked around on the net but cant seem
to find an answer anywhere

i have compiled apache 1_3.20 and perl 5.6.1 problemless. 
i have also installed the nesecary modules before mod_perl and now want
to build mod_perl itself.
im aware of the head/HEAD problem that comes with LWP on mac osX and
have therefore copied a binary head that ken williams sent me into
/usr/bin and moved the lwp head into /usr/local/bin.

below follows an exerpt from the shell

thanks
allan



[localhost:/Applications/mod_perl-1.25] aju% sudo perl makefile.pl
everything=1 apache_prefix=/usr/local/apache
Configure mod_perl with ../apache_1.3.20/src ? [y] y
Shall I build httpd in ../apache_1.3.20/src for you? [y] y
Appending mod_perl to src/Configuration
Unknown option: 1
Usage: head [-options] <url>...
    -m <method>   use method for the request (default is 'HEAD')
etc. etc. ...

Using config file: /Applications/mod_perl-1.25/src/Configuration
Creating Makefile
 + configured for Darwin platform
 + setting C compiler to cc
 + setting C pre-processor to cc -E -traditional-cpp
 + checking for system header files
 + adding selected modules

Usage: head [-options] <url>...
    -m <method>   use method for the request (default is 'HEAD')
etc. etc. ...

 + checking sizeof various data types
 + doing sanity check on compiler and options
Creating Makefile in support
Creating Makefile in regex
Creating Makefile in os/unix
Creating Makefile in ap
Creating Makefile in main
Creating Makefile in lib/expat-lite
Creating Makefile in modules/standard
EXTRA_CFLAGS: -DDARWIN -DUSE_HSREGEX -DUSE_EXPAT
-I$(SRCDIR)/lib/expat-lite -DNO_DL_NEEDED
PerlDispatchHandler.........disabled (enable with PERL_DISPATCH=1)
PerlChildInitHandler........enabled
PerlChildExitHandler........enabled
PerlPostReadRequestHandler..disabled (enable with PERL_POST_READ_REQUEST=1)
PerlTransHandler............disabled (enable with PERL_TRANS=1)
PerlHeaderParserHandler.....disabled (enable with PERL_HEADER_PARSER=1)
PerlAccessHandler...........disabled (enable with PERL_ACCESS=1)
PerlAuthenHandler...........disabled (enable with PERL_AUTHEN=1)
PerlAuthzHandler............disabled (enable with PERL_AUTHZ=1)
PerlTypeHandler.............disabled (enable with PERL_TYPE=1)
PerlFixupHandler............disabled (enable with PERL_FIXUP=1)
PerlHandler.................enabled
PerlLogHandler..............disabled (enable with PERL_LOG=1)
PerlInitHandler.............disabled (enable with PERL_INIT=1)
PerlCleanupHandler..........disabled (enable with PERL_CLEANUP=1)
PerlRestartHandler..........disabled (enable with PERL_RESTART=1)
PerlStackedHandlers.........disabled (enable with PERL_STACKED_HANDLERS=1)
PerlMethodHandlers..........disabled (enable with PERL_METHOD_HANDLERS=1)
PerlDirectiveHandlers.......disabled (enable with PERL_DIRECTIVE_HANDLERS=1)
PerlTableApi................disabled (enable with PERL_TABLE_API=1)
PerlLogApi..................disabled (enable with PERL_LOG_API=1)
PerlUriApi..................disabled (enable with PERL_URI_API=1)
PerlUtilApi.................disabled (enable with PERL_UTIL_API=1)
PerlFileApi.................disabled (enable with PERL_FILE_API=1)
PerlConnectionApi...........enabled
PerlServerApi...............enabled
PerlSections................disabled (enable with PERL_SECTIONS=1)

PerlSSI.....................disabled (enable with PERL_SSI=1)

Will run tests as User: 'nobody' Group: 'wheel'
Checking CGI.pm VERSION..........ok
Checking for LWP::UserAgent......ok
Checking for HTML::HeadParser....ok
Checking if your kit is complete...
Looks good
'APACHE_PREFIX' is not a known MakeMaker parameter name.
'EVERYTHING' is not a known MakeMaker parameter name.
Writing Makefile for Apache
Writing Makefile for Apache::Connection
Writing Makefile for Apache::Constants
Writing Makefile for Apache::File
Writing Makefile for Apache::Leak
Writing Makefile for Apache::Log
Writing Makefile for Apache::ModuleConfig
Writing Makefile for Apache::PerlRunXS
Writing Makefile for Apache::Server
Writing Makefile for Apache::Symbol
Writing Makefile for Apache::Table
Writing Makefile for Apache::URI
Writing Makefile for Apache::Util
Writing Makefile for mod_perl
[localhost:/Applications/mod_perl-1.25] aju% sudo make
(cd ../apache_1.3.20/src && PERL5LIB=/Applications/mod_perl-1.25/lib env
LD_RUN_PATH=/System/Library/Perl/darwin/CORE make CC="cc";)
===> regex
cc -I.  -I../os/unix -I../include   -DDARWIN -DUSE_HSREGEX -DUSE_EXPAT
-I../lib/expat-lite -DNO_DL_NEEDED -g -pipe -pipe -fno-common
-DHAS_TELLDIR_PROTOTYPE -fno-strict-aliasing -I/usr/local/include
-DMOD_PERL -DPOSIX_MISTAKE   -c -o regcomp.o regcomp.c
etc. etc. ...

/usr/bin/ld: Undefined symbols:
_actions_module
_include_module
_log_config_module
make[1]: *** [target_static] Error 1
make: *** [apache_httpd] Error 2

[localhost:/Applications/mod_perl-1.25] aju%

Re: macintosh osX - mod_perl install problems -> head - HEAD - setenv

Posted by allan <la...@inet.uni2.dk>.
thanks again

i did something similar with that lwp-head before i read your reply, but
somewhat more stupid:

rm HEAD

(!)

in fact i have now tested mod_perl with only "ok"s and "skipped on this
platform"s and installed as well with no complaints whatsoever.
so i guess im almost there (im posting other queries just after this)

allan

Ken Williams wrote:
> 
> lambretta@inet.uni2.dk (allan) wrote:
> >one thing: i have discovered that another problem i have had since
> >upgrading to perl 5.6.1 might be interfering with the one in this topic
> >(im not sure though -  it is concerning setenv)
> >
> >look at this new fresh terminal window:
> >
> >[localhost:~] aju% which head
> >/usr/local/bin/head
> >[localhost:~] aju% which HEAD
> >/usr/bin/HEAD
> >[localhost:~] aju% setenv LC_ALL C
> >[localhost:~] aju% setenv LANG "en_US"
> >[localhost:~] aju% which head
> >/usr/bin/head
> >[localhost:~] aju% which HEAD
> >/usr/local/bin/HEAD
> 
> Criminy!  I don't understand this one bit.  But if you do:
> 
>   cd /usr/local/bin
>   mv HEAD LWP-HEAD
> 
> then you should have it out of the way for good.  At least until you try
> to upgrade LWP. =)

Re: macintosh osX - mod_perl install problems -> head - HEAD - setenv

Posted by Ken Williams <ke...@forum.swarthmore.edu>.
lambretta@inet.uni2.dk (allan) wrote:
>one thing: i have discovered that another problem i have had since
>upgrading to perl 5.6.1 might be interfering with the one in this topic
>(im not sure though -  it is concerning setenv)
>
>look at this new fresh terminal window:
>
>[localhost:~] aju% which head
>/usr/local/bin/head
>[localhost:~] aju% which HEAD
>/usr/bin/HEAD
>[localhost:~] aju% setenv LC_ALL C
>[localhost:~] aju% setenv LANG "en_US"
>[localhost:~] aju% which head
>/usr/bin/head
>[localhost:~] aju% which HEAD
>/usr/local/bin/HEAD

Criminy!  I don't understand this one bit.  But if you do:

  cd /usr/local/bin
  mv HEAD LWP-HEAD

then you should have it out of the way for good.  At least until you try
to upgrade LWP. =)

>maybe i should just start all over, reformat and everything ...?
>

No, that's probably a bit too drastic if you've got anything of
consequence on the disk.


  -------------------                            -------------------
  Ken Williams                             Last Bastion of Euclidity
  ken@forum.swarthmore.edu                            The Math Forum

Re: macintosh osX - mod_perl install problems -> head - HEAD - setenv

Posted by allan <la...@inet.uni2.dk>.
Ken Williams wrote:
> 
> lambretta@inet.uni2.dk (allan) wrote:
> >im aware of the head/HEAD problem that comes with LWP on mac osX and
> >have therefore copied a binary head that ken williams sent me into
> >/usr/bin and moved the lwp head into /usr/local/bin.
> 
> Looks like that problem still isn't fixed, as shown by the following
> error message:
> 
> >Usage: head [-options] <url>...
> >    -m <method>   use method for the request (default is 'HEAD')
> 
> You may have a different PATH than I do, or different capitalization on
> the binary files.  The upshot is that when you run the 'head' command,
> it *must* run the /usr/bin/head program I sent you and not LWP's 'HEAD'
> script.  Here's a transcript from my shell, what does yours say?
> 
>    [localhost:~] ken% which head
>    /usr/bin/head
>    [localhost:~] ken% which HEAD
>    /usr/local/bin/HEAD

hi ken
thank you  for the pointer but this head file is really going on my
nerves ,-)

one thing: i have discovered that another problem i have had since
upgrading to perl 5.6.1 might be interfering with the one in this topic
(im not sure though -  it is concerning setenv)

look at this new fresh terminal window:

[localhost:~] aju% which head
/usr/local/bin/head
[localhost:~] aju% which HEAD
/usr/bin/HEAD
[localhost:~] aju% setenv LC_ALL C
[localhost:~] aju% setenv LANG "en_US"
[localhost:~] aju% which head
/usr/bin/head
[localhost:~] aju% which HEAD
/usr/local/bin/HEAD

one thing is certain even if dont use the setenv command:

the file called head inside /usr/bin is definetely the binary you sent me
the file called head inside /usr/local/bin is definetely the LWP one
inside these directories there are definetely only one head file (ie
there is no room for another with another capitalization)


nevertheless when i try to build mod_perl i will get the annoying:

Usage: head [-options] <url>...
    -m <method>   use method for the request (default is 'HEAD')


maybe i should just start all over, reformat and everything ...?

thanks once again
allan

Re: macintosh osX - mod_perl install problems

Posted by Ken Williams <ke...@forum.swarthmore.edu>.
lambretta@inet.uni2.dk (allan) wrote:
>im aware of the head/HEAD problem that comes with LWP on mac osX and
>have therefore copied a binary head that ken williams sent me into
>/usr/bin and moved the lwp head into /usr/local/bin.

Looks like that problem still isn't fixed, as shown by the following
error message:

>Usage: head [-options] <url>...
>    -m <method>   use method for the request (default is 'HEAD')

You may have a different PATH than I do, or different capitalization on
the binary files.  The upshot is that when you run the 'head' command,
it *must* run the /usr/bin/head program I sent you and not LWP's 'HEAD'
script.  Here's a transcript from my shell, what does yours say?

   [localhost:~] ken% which head
   /usr/bin/head
   [localhost:~] ken% which HEAD
   /usr/local/bin/HEAD


  -------------------                            -------------------
  Ken Williams                             Last Bastion of Euclidity
  ken@forum.swarthmore.edu                            The Math Forum