Compiling mod_perl

2000-05-05 Thread Rich Theisen

Hello,
  I can build Apache 1.3.11 with mod_perl 1.21 without any difficulties
using mod_perl. The problem comes in when I try to incorperate mod_ssl
or mod_jserv. I can build Apache with either mod_ssl or mod_jserv
without any problems. (I haven't tried yet combining both mod_ssl and
mod_jserv with Apache.)
  I've tried using mod_perl to build Apache and the third party modules.
I've also tried compiling mod_perl independantly and the compile Apache
with the other modules. When I try to compile the parts independantly,
mod_perl always comes back with errors stating undefined reference. I've
tried to include the required include files. I still get the same error.

  I've gotten to a point where I'm ready to not include mod_perl. Any
help is appreciated! The system I'm using is a Sun Ultra 2 running
Solaris 2.6.

Thank you,
  Richard




Error compiling mod_perl

2000-04-11 Thread Sam Carleton

This is the error message I got when I compiled mod_perl:

Perl lib version (5.00503) doesn't match executable version (5.006) at
/usr/lib/perl5/5.00503/i586-linux/Config.pm line 7.
Compilation failed in require at
/usr/lib/perl5/5.00503/ExtUtils/MakeMaker.pm line 13.
BEGIN failed--compilation aborted at
/usr/lib/perl5/5.00503/ExtUtils/MakeMaker.pm line 13.
Compilation failed in require.
BEGIN failed--compilation aborted.
make: *** [Version_check] Error 255

How do I fix this?

Sam




Trouble compiling mod_perl

2000-04-27 Thread Jean-Sebastien Morisset

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I first tried to compile mod_perl-1.22 using APXS, but whenever I would
load the module, the Apache child would die.

Here's the command line I used:

perl Makefile.PL NO_HTTPD=1 EVERYTHING=1
WITH_APXS=/opt/apache-1.3.12/bin/apxs USE_APXS=1

I then tried to compile mod_perl with Apache (not shared). When I do, the
make fails. Here's the mod_perl config I used:

perl Makefile.PL DO_HTTPD=1 EVERYTHING=1

And the configuration for Apache:

SSL_BASE=../openssl-0.9.5a
RSA_BASE=../rsaref-2.0/local
export SSL_BASE RSA_BASE

./configure \
- --prefix=/opt/apache-1.3.12 \
- --enable-rule=SHARED_CORE \
- --activate-module=src/modules/perl/libperl.a \
- --enable-module=ssl \
- --enable-module=unique_id \
- --enable-module=rewrite \
- --enable-module=expires \
- --enable-module=info \
- --enable-module=so \
- --enable-module=status \
- --enable-module=vhost_alias \
- --enable-shared=max \
- --disable-shared=perl \
- --disable-shared=vhost_alias \
- --disable-module=userdir \
- --disable-module=autoindex \
- --disable-module=imap

And here's the error which is generated by the make:

<=== src/modules
gcc -c  -I./os/unix -I./include   -DLINUX=2 -DMOD_SSL=206102 -DUSE_HSREGEX
- -DEAPI -DUSE_EXPAT -I./lib/expat-lite -fpic -DSHARED_CORE `./apaci`
modules.c
gcc -c  -I./os/unix -I./include   -DLINUX=2 -DMOD_SSL=206102 -DUSE_HSREGEX
- -DEAPI -DUSE_EXPAT -I./lib/expat-lite -fpic -DSHARED_CORE `./apaci`
buildmark.c
gcc -shared -o libhttpd.so buildmark.o modules.o modules/perl/libperl.a
modules/standard/libstandard.a main/libmain.a ./os/unix/libos.a ap/libap.a
regex/libregex.a lib/expat-lite/libexpat.a  
gcc  -I./os/unix -I./include   -DLINUX=2 -DMOD_SSL=206102 -DUSE_HSREGEX
- -DEAPI -DUSE_EXPAT -I./lib/expat-lite -fpic -DSHARED_CORE `./apaci`
- -rdynamic \
  -o libhttpd.ep -DSHARED_CORE_TIESTATIC main/http_main.c \
  -L. -lhttpd  -lm -lcrypt -lndbm -ldl
./libhttpd.so: undefined reference to `PL_dowarn'
./libhttpd.so: undefined reference to `Perl_gv_stashpv'
./libhttpd.so: undefined reference to `perl_get_sv'
./libhttpd.so: undefined reference to `Perl_croak'
./libhttpd.so: undefined reference to `Perl_sv_free'
./libhttpd.so: undefined reference to `Perl_markstack_grow'
./libhttpd.so: undefined reference to `PL_gid'
.
.
.


Does anyone have any idea what could be wrong?

Thanks,
js.
- -- 
Jean-Sebastien Morisset, Sr. UNIX Admin <[EMAIL PROTECTED]>
Personal Homepage  
UNIX, Internet, Homebrewing, Cigars, PCS, CP2020 and other Fun Stuff...
This is Linux Country. On a quiet night you can hear Windows NT reboot!

-BEGIN PGP SIGNATURE-
Version: PGP 6.5.1i
Comment: Personal Home Page 

iQA/AwUBOQiMc5xsiDnGGop4EQK8OQCeLJ8Gh5I1TI25aWVnQCVtsKEE1KcAoIZr
eZGPrCErESqVqlWXqwhd58oM
=KrJz
-END PGP SIGNATURE-



Re: Compiling mod_perl

2000-05-06 Thread Stas Bekman

On Fri, 5 May 2000, Rich Theisen wrote:

> Hello,
>   I can build Apache 1.3.11 with mod_perl 1.21 without any difficulties
> using mod_perl. The problem comes in when I try to incorperate mod_ssl
> or mod_jserv. I can build Apache with either mod_ssl or mod_jserv
> without any problems. (I haven't tried yet combining both mod_ssl and
> mod_jserv with Apache.)
>   I've tried using mod_perl to build Apache and the third party modules.
> I've also tried compiling mod_perl independantly and the compile Apache
> with the other modules. When I try to compile the parts independantly,
> mod_perl always comes back with errors stating undefined reference. I've
> tried to include the required include files. I still get the same error.
> 
>   I've gotten to a point where I'm ready to not include mod_perl. Any
> help is appreciated! The system I'm using is a Sun Ultra 2 running
> Solaris 2.6.

http://perl.apache.org/guide/install.html#Installation_Scenarios_for_mod_p


__
Stas Bekman | JAm_pH--Just Another mod_perl Hacker
http://stason.org/  | mod_perl Guide  http://perl.apache.org/guide 
mailto:[EMAIL PROTECTED]  | http://perl.orghttp://stason.org/TULARC/
http://singlesheaven.com| http://perlmonth.com http://sourcegarden.org
--




compiling mod_perl-1.24

2000-11-28 Thread Joseph Crotty

I am on a sun box:

uname -a

SunOS mailroom 5.6 Generic_105181-22 sun4u sparc SUNW,Ultra-5_10

I built and tested both perl 5.6.0 and apache_1.3.9 against gcc and they
check out OK:

gcc -v

Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.7.2.2/specs
gcc version 2.7.2.2

perl -V

Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
  Platform:
osname=solaris, osvers=2.6, archname=sun4-solaris
uname='sunos mailroom 5.6 generic_105181-22 sun4u sparc sunw,ultra-5_10
'
config_args='-Dcc=gcc'
hint=previous, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define 
use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
  Compiler:
cc='gcc', optimize='-O', gccversion=2.7.2.2
cppflags='-I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64'
ccflags ='-I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64'
stdchar='unsigned char', d_stdstdio=define, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, usemymalloc=y, prototype=define
  Linker and Libraries:
ld='gcc', ldflags =' -L/usr/local/lib '
libpth=/usr/local/lib /lib /usr/lib /usr/ccs/lib
libs=-lsocket -lnsl -lgdbm -ldl -lm -lc -lcrypt -lsec
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib'


Characteristics of this binary (from libperl): 
  Compile-time options: USE_LARGE_FILES
  Built under solaris
  Compiled at Nov 27 2000 16:41:31
  @INC:
/usr/local/lib/perl5/5.6.0/sun4-solaris
/usr/local/lib/perl5/5.6.0
/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris
/usr/local/lib/perl5/site_perl/5.6.0
/usr/local/lib/perl5/site_perl

So, I run the Makefile as follows:

perl Makefile.PL EVERYTHING=1 APACHE_PREFIX=/usr/local/apache

Configure mod_perl with ../apache_1.3.9/src ? [y] 
Shall I build httpd in ../apache_1.3.9/src for you? [y] 
Appending mod_perl to src/Configuration
Using config file: /home/dvlp/jcrotty/mod_perl-1.24/src/Configuration
Creating Makefile
 + configured for Solaris 260 platform
 + setting C compiler to gcc
 + setting C pre-processor to gcc -E
 + checking for system header files
 + adding selected modules
 + checking sizeof various data types
 + doing sanity check on compiler and options
Creating Makefile in support
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: -DSOLARIS2=260 -DUSE_EXPAT -I$(SRCDIR)/lib/expat-lite
PerlDispatchHandler.enabled
PerlChildInitHandlerenabled
PerlChildExitHandlerenabled
PerlPostReadRequestHandler..enabled
PerlTransHandlerenabled
PerlHeaderParserHandler.enabled
PerlAccessHandler...enabled
PerlAuthenHandler...enabled
PerlAuthzHandlerenabled
PerlTypeHandler.enabled
PerlFixupHandlerenabled
PerlHandler.enabled
PerlLogHandler..enabled
PerlInitHandler.enabled
PerlCleanupHandler..enabled
PerlRestartHandler..enabled
PerlStackedHandlers.enabled
PerlMethodHandlers..enabled
PerlDirectiveHandlers...enabled
PerlTableApienabled
PerlLogApi..enabled
PerlUriApi..enabled
PerlUtilApi.enabled
PerlFileApi.enabled
PerlConnectionApi...enabled
PerlServerApi...enabled
PerlSectionsenabled
PerlSSI.enabled
Will run tests as User: 'nobody' Group: 'other'
Checking CGI.pm VERSION..ok
Checking for LWP::UserAgent..ok
Checking for HTML::HeadParserok
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

I run make and get this:

gcc -c  -I../os/unix -I../include   -DSOLARIS2=260 -DUSE_EXPAT
-I../lib/expat-lite -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64  -I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE  -I.
-I../.. -DUSE_PERL_SSI -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -DMOD_PERL http_config.c
In file included from /usr/include/sys/vnode.h:41,
 from /

Re: Problems compiling mod_perl

1999-11-03 Thread Nick Moore

G'day all,

I've been having similar problems to Michael Wright, building 
mod_perl-1.21 on Linux 2.0.36 (Debian slink) with apache 1.3.9 and
perl 5.005_61.

I've been trying a static build ... in the final link of
httpd, two symbols (perl_eval_sv, perl_eval_pv) are used by mod_perl
code but can't be found.

These symbols are #define'd in perl header files, so I'm not
sure why they don't make it through. I found that #defining them
solves the problem (well, it builds, anyway).

This is the same solution as Doug MacEachern posted in the
thread "HTML::Embperl and 'undefined symbol: perl_eval_sv'". I've
copied his answer so anyone suffering from this problem won't have
to madly look up that thread. Just add the following lines to the
end of your existing mod_perl.h:

#ifdef eval_pv
#   ifndef perl_eval_pv
#  define perl_eval_pv eval_pv
#   endif
#endif
#ifdef eval_sv
#   ifndef perl_eval_sv
#  define perl_eval_sv eval_sv
#   endif
#endif

Hope that helps ...

-Nick 'Sharkey' Moore, [EMAIL PROTECTED]



Problem with compiling mod_perl

1999-12-08 Thread Craig Vincent



I must have now installed mod_perl a dozen times on 
a dozen machines and this is the first time I've come across this problem and I 
can't seem to solve it...nor have I had any luck through FAQs, DejaNews or even 
newsgroup postings :(
 
I have an RH Linux 6.1 box.  I currently have 
Apache 1.3.9 running on the server.  My problem is when I attempt to 
compile mod_perl...this is what I get...
 

SSL_BASE=/usr/local perl Makefile.PL EVERYTHING=1 
DO_HTTPD=1Appending mod_perl to src/ConfigurationUsing config file: 
/usr/home/sysadm/mod_perl-1.21/src/ConfigurationCreating Makefile + 
configured for Linux platform + setting C pre-processor to gcc 
-E + checking for system header files + adding selected 
modules
    o ssl_module uses 
ConfigStart/End  + SSL interface: 
mod_ssl/2.4.9  + SSL interface build type: 
OBJ  + SSL interface compatibility: 
disabled  + SSL interface experimental code: 
disabled  + SSL interface vendor extensions: 
disabled  + SSL interface plugin: Configured 
DBM (-ldbm)  + SSL library path: 
/usr/local  + SSL library version: OpenSSL 
0.9.4 09 Aug 1999  + SSL library type: 
installed package (stand-alone)  + SSL library 
plugin mode: none + enabling Extended API (EAPI) + checking 
sizeof various data types + doing sanity check on compiler and 
options** A test compilation with your Makefile configuration** failed. 
This is most likely because your C compiler** is not ANSI. Apache requires 
an ANSI C Compiler, such** as gcc. The above error message from your 
compiler** will also provide a clue.

 
This DOES NOT happen if I attempt to compile Apache 
on it's own...this error only occurs when I attempt to do an HTTPD build through 
mod_perl.  Now the one thing I have discovered is 95% of the time the test 
compilation error is not because of the compiler not supporting ANSI (I'm using 
the latest gcc btw) but is just something failed in the compiling whether it be 
a configuration error, problem running a function etc...  The main problem 
is that I don't receive any additional error messages so I don't know what the 
real problem is.  I have also tried using gcc with the -ansi switch as well 
just to be on the safe side but that didn't help either.
 
Has anyone ever encountered anything like this 
before?  Or have any ideas on what may be causing this error?
 
Sincerely,
 
Craig Vincent


Re: Error compiling mod_perl

2000-04-11 Thread Doug MacEachern

On Tue, 11 Apr 2000, Sam Carleton wrote:

> This is the error message I got when I compiled mod_perl:
> 
> Perl lib version (5.00503) doesn't match executable version (5.006) at
> /usr/lib/perl5/5.00503/i586-linux/Config.pm line 7.

you either installed a new Perl after running mod_perl's Makefile.PL or
have a broken Perl installation.  try building mod_perl from a fresh
source tree.




Re: Error compiling mod_perl

2000-04-12 Thread Sam Carleton

Doug MacEachern wrote:

> On Tue, 11 Apr 2000, Sam Carleton wrote:
>
> > This is the error message I got when I compiled mod_perl:
> >
> > Perl lib version (5.00503) doesn't match executable version (5.006) at
> > /usr/lib/perl5/5.00503/i586-linux/Config.pm line 7.
>
> you either installed a new Perl after running mod_perl's Makefile.PL or
> have a broken Perl installation.  try building mod_perl from a fresh
> source tree.

OK, I messed things up with CPAN, I believe that it installed 5.006 where my
distribution came with 5.003.  I decided to resolve the issue by installing
5.6.  I am able to run perl Makefile.PL without error and compile without
errors.  When I run make test, I get this error:

---make test error---
Syntax error on line 30 of /usr/src/mod_perl-1.21_03/t/conf/httpd.conf:
Invalid command '=pod', perhaps mis-spelled or defined by a module not
included in the server configuration
done
/usr/local/bin/perl t/TEST 0
still waiting for server to warm up...not ok
server failed to start! (please examine t/logs/error_log) at t/TEST line 95.

make: *** [run_tests] Error 111
---make test error---

I looked in t/logs for a error_log, but t/logs is empty.  I think I might
have issue with the way I am configuring apache and mod_perl.  This is my
.makepl_args.mod_perl:

---.makepl_args.mod_perl---
# File: .makepl_args.mod_erl
# enable all phase callbacks, API modules and misc features
EVERYTHING=1

# tell runtime diagnostics to active if MOD_PERL_TRACE environment
# variable is set at runtime
PERL_TRACE=1

# tell Makefile.pl where the Apache source tree is
APACHE_SRC=/usr/src/apache/src

# tell Makefile.PL where the Apache is to be isntalled
APACHE_PREFIX=/data01/apache

# disable Makefile.pl from compiling Apache
#PREP_APACHED=1

# tell Makefile.PL to use the first source found, which will be the
# path specified above by APACHE_SRC
DO_HTTPD=1

# tell Makefile.PL to configure Apache using the apaci interface
USE_APACI=1

# tell makefile.PL to configure ssl support, too
# SSL_BASE=/usr/local/ssl

# add mod_info, mod_status, mod_usertrack, and mod_unique_id
ADD_MODULE=info,status,usertrack,unique_id

# additional arguments to give Apache's configure script
# aruments can be delimited by comma and/or specified with multipal
# APACI_ARGS lines
#APACI_ARGS=--includedir=/usr/src/php
#APACI_ARGS=--activate-module=src/modules/php3/libphp3.a
APACI_ARGS=--with-layout=apache.config.layout:Sam-Layout
APACI_ARGS=--server-uid=wwwrun
APACI_ARGS=--server-gid=dosemu
APACI_ARGS=--enable-module=most
APACI_ARGS=--enable-shared=max
---.makepl_args.mod_perl---

And the options I am using to make apache:

---apache options---
configure \
--with-layout=/root/apache.config.layout:Sam-Layout \
--with-perl=src/modules/perl \
--enable-module=most \
--server-uid=wwwrun \
--server-gid==dosemu \
--enable-shared=max
---apache options---

Any thoughts on what I have wrong?

Sam

P.S.  Thanks a millon for having the .makepl_args.mod_perl idea!!!  It is an
outstanding one!




Re: Error compiling mod_perl

2000-04-12 Thread Sam Carleton

Geoffrey Young wrote:

> > ---make test error---
> > Syntax error on line 30 of
> > /usr/src/mod_perl-1.21_03/t/conf/httpd.conf:
> > Invalid command '=pod', perhaps mis-spelled or defined by a module not
> > included in the server configuration
> > done
> > /usr/local/bin/perl t/TEST 0
> > still waiting for server to warm up...not ok
> > server failed to start! (please examine t/logs/error_log) at
> > t/TEST line 95.
> >
> > make: *** [run_tests] Error 111
> > ---make test error---
>
> I think I remember that some people were able to get around this error by
> allowing the server more time to warm up.
>
> try editing TEST to allow for more time (around line 82)

I tried it but no avail.  I think the problem has something to do with the
fact that there is an invalid command in the httpd.conf file that apache is
reading when it starts.

Sam




Re: Trouble compiling mod_perl

2000-05-03 Thread Doug MacEachern

On Thu, 27 Apr 2000, Jean-Sebastien Morisset wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> I first tried to compile mod_perl-1.22 using APXS, but whenever I would
> load the module, the Apache child would die.
> 
> Here's the command line I used:
> 
> perl Makefile.PL NO_HTTPD=1 EVERYTHING=1
> WITH_APXS=/opt/apache-1.3.12/bin/apxs USE_APXS=1

your perl -V might help spot the problem.  as would a stacktrace (see
SUPPORT for hints)
 
> I then tried to compile mod_perl with Apache (not shared). When I do, the
> make fails. Here's the mod_perl config I used:

try using the steps in INSTALL.simple.mod_ssl instead.




compiling mod_perl with PERL_STATIC_EXTS

2000-06-05 Thread Timothy Chi

Hi all-

I'm trying to build mod_perl 1.21_02 (w/ apache 1.3.12) with GD statically
linked.

I've tried running 
perl Makefile.PL PERL_STATIC_EXTS='GD' EVERYTHING=1 USE_APACI=1
APACI_ARGS='--prefix=/usr/local/bb/httpd, --enable-module=proxy'

and I get:

gcc  -DLINUX=2 -DMOD_PERL -DUSE_PERL_SSI -Dbool=char -DHAS_BOOL
-DUSE_HSREGEX -DUSE_EXPAT -I./lib/expat-lite -DNO_DL_NEEDED `./apaci`\
  -o httpd buildmark.o modules.o modules/standard/libstandard.a
modules/proxy/libproxy.a modules/perl/libperl.a main/libmain.a
./os/unix/libos.a ap/libap.a regex/libregex.a lib/expat-lite/libexpat.a  -lm
-lcrypt -rdynamic  -L/usr/local/lib
/usr/local/bb/perl/lib/5.00503/i686-linux/auto/DynaLoader/DynaLoader.a
-L/usr/local/bb/perl/lib/5.00503/i686-linux/CORE -lperl -lnsl -lndbm -lgdbm
-ldb -ldl -lm -lc -lposix -lcrypt 
modules/perl/libperl.a(perlxsi.o): In function `xs_init':
perlxsi.o(.text+0xb4): undefined reference to `boot_GD'
collect2: ld returned 1 exit status
make[3]: *** [target_static] Error 1

The version of Perl is 5.005_03.  I have built GD and statically linked it
to Perl.

When I run:

# perl -MExtUtils::Embed -e ldopts -- -std GD
-rdynamic  -L/usr/local/lib
/usr/local/bb/perl/lib/site_perl/5.005/i686-linux/auto/GD/GD.a
/usr/local/bb/perl/lib/5.00503/i686-linux/auto/DynaLoader/DynaLoader.a
-L/usr/local/bb/perl/lib/5.00503/i686-linux/CORE -lperl -lnsl -lndbm -lgdbm
-ldb -ldl -lm -lc -lposix -lcrypt -L/usr/lib/X11 -L/usr/X11R6/lib
-L/usr/local/lib -lgd -lpng -lttf -lz -ljpeg -lm -lX11 -lXpm

Running this command (this was pulled from one of Doug M. earlier posts):
# perl -MExtUtiles::Embed -e xsinit -- -std GD
# cat perlxsi.c
EXTERN_C void xs_init _((void));

EXTERN_C void boot_GD _((CV* cv));
EXTERN_C void boot_DynaLoader _((CV* cv));

EXTERN_C void
xs_init(void)
{
char *file = __FILE__;
dXSUB_SYS;

newXS("GD::bootstrap", boot_GD, file);
/* DynaLoader is a special case */
newXS("DynaLoader::boot_DynaLoader", boot_DynaLoader, file);
}

It seems like the GD.a library can't be located by the linker for some
reason.  I've set my LD_LIBRARY_PATH, LD_RUN_PATH environment variables, and
I've tried modifying the Makefile to include the path to the GD.a
(/usr/local/bb/perl/lib/site_perl/5.005/i686-linux/auto/GD)

Any suggestions?  Sorry, I'm kinda new at all of this.

Thanks in advance.

--Tim






compiling mod_perl for solaris

2000-08-31 Thread Joseph Sirucka - Netics

Hi People

I've been trying to compile mod_perl for solaris 8 recently and I
recompiled perl 5.6.0 with _ubincompat5005 and -Uuselargefiles.

But no matter what I do with with mod_perl to compile it at
perl Makefile.PL blah i get this error

ld.so.1: perl: fatal: relocation error: file
/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/auto/HTML/Parser/Parser.so:

symbol perl_get_hv: referenced symbol not found
Killed

what am I doing wrong. What I'm trying to do is compile mod_perl as a
seperate module.

Hope to hear from someone soon.

--
   Joseph Sirucka

[EMAIL PROTECTED]







trouble compiling mod_perl-1.24_01

2000-11-14 Thread Jere C. Julian, Jr.

I'm on a FreeBSD 3.4-RELEASE box and I've just built and tested apache
1.3.14 from source.  Then I try to build mod_perl with the following
commands and get the errors below.

The full text of the process can be seen at
http://www.StageRigger.com/mod_perl-1.24_01.log

Has anyone run into this?  Suggestions?

Thanks,
-Jere Julian
-- 
  +---+
  | Jere C Julianmailto:[EMAIL PROTECTED]  |
  | Network Designer/Manager, Rigger, Sound Engineer  |
  |http://www.StageRigger.com/|
  +---+

perl Makefile.PL APACHE_SRC=../apache_1.3.14/src DO_HTTPD=1 USE_APACI=1


make

...
cp Server.pm ../blib/lib/Apache/Server.pm
mkdir ../blib/arch/auto/Apache/Server
mkdir ../blib/lib/auto/Apache/Server
cp Symbol.pm ../blib/lib/Apache/Symbol.pm
/usr/bin/perl -I/usr/local/lib/perl5/5.6.0/i386-freebsd
-I/usr/local/lib/perl5/5.6.0 /usr/local/lib/perl5/5.6.0/ExtUtils/xsubpp 
-typemap /usr/local/lib/perl5/5.6.0/ExtUtils/typemap Symbol.xs >
Symbol.xsc && mv Symbol.xsc Symbol.c
cc -c  -I/usr/local/include -O  -DVERSION=\"1.31\" 
-DXS_VERSION=\"1.31\" -DPIC -fpic
-I/usr/local/lib/perl5/5.6.0/i386-freebsd/CORE  Symbol.c
Symbol.xs: In function `XS_Apache__Symbol_cv_const_sv':
Symbol.xs:106: `na' undeclared (first use this function)
Symbol.xs:106: (Each undeclared identifier is reported only once
Symbol.xs:106: for each function it appears in.)
*** Error code 1

Stop.
*** Error code 1

Stop.



RE: compiling mod_perl-1.24

2000-11-28 Thread Lakshmanan, Srikrishnan

I ran into this problem a week ago on both Solaris 2.6 and 2.7 , and I was
using gnu cc 2.7.2.3 . I upgraded to gnu cc 2.95.2 . I had to recompile my
perl 5.6.0 from stable.tar at www.cpan.org using this compiler and rebuilt
Apache and mod_perl without any problems . 

You will find a pre-built binary for gnu cc 2.95.2 at www.sunfreeware.com
for your Solaris version.

Sri Lakshmanan

Koch Petroleum Group
[EMAIL PROTECTED]
"A doctor can bury his mistakes, an architect can only advise his client to
plant vines" -Frank Lloyd Wright


> -Original Message-
> From: Joseph Crotty [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday,November 28,2000 12:03 PM
> To:   '[EMAIL PROTECTED]'
> Subject:  compiling mod_perl-1.24
> 
> I am on a sun box:
> 
> uname -a
> 
> SunOS mailroom 5.6 Generic_105181-22 sun4u sparc SUNW,Ultra-5_10
> 
> I built and tested both perl 5.6.0 and apache_1.3.9 against gcc and they
> check out OK:
> 
> gcc -v
> 
> Reading specs from
> /usr/local/lib/gcc-lib/sparc-sun-solaris2.6/2.7.2.2/specs
> gcc version 2.7.2.2
> 
> perl -V
> 
> Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
>   Platform:
> osname=solaris, osvers=2.6, archname=sun4-solaris
> uname='sunos mailroom 5.6 generic_105181-22 sun4u sparc
> sunw,ultra-5_10
> '
> config_args='-Dcc=gcc'
> hint=previous, useposix=true, d_sigaction=define
> usethreads=undef use5005threads=undef useithreads=undef
> usemultiplicity=undef
> useperlio=undef d_sfio=undef uselargefiles=define 
> use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
>   Compiler:
> cc='gcc', optimize='-O', gccversion=2.7.2.2
> cppflags='-I/usr/local/include -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64'
> ccflags ='-I/usr/local/include -D_LARGEFILE_SOURCE
> -D_FILE_OFFSET_BITS=64'
> stdchar='unsigned char', d_stdstdio=define, usevfork=false
> intsize=4, longsize=4, ptrsize=4, doublesize=8
> d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
> ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
> lseeksize=8
> alignbytes=8, usemymalloc=y, prototype=define
>   Linker and Libraries:
> ld='gcc', ldflags =' -L/usr/local/lib '
> libpth=/usr/local/lib /lib /usr/lib /usr/ccs/lib
> libs=-lsocket -lnsl -lgdbm -ldl -lm -lc -lcrypt -lsec
> libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
>   Dynamic Linking:
> dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
> cccdlflags='-fPIC', lddlflags='-G -L/usr/local/lib'
> 
> 
> Characteristics of this binary (from libperl): 
>   Compile-time options: USE_LARGE_FILES
>   Built under solaris
>   Compiled at Nov 27 2000 16:41:31
>   @INC:
> /usr/local/lib/perl5/5.6.0/sun4-solaris
> /usr/local/lib/perl5/5.6.0
> /usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris
> /usr/local/lib/perl5/site_perl/5.6.0
> /usr/local/lib/perl5/site_perl
> 
> So, I run the Makefile as follows:
> 
> perl Makefile.PL EVERYTHING=1 APACHE_PREFIX=/usr/local/apache
> 
> Configure mod_perl with ../apache_1.3.9/src ? [y] 
> Shall I build httpd in ../apache_1.3.9/src for you? [y] 
> Appending mod_perl to src/Configuration
> Using config file: /home/dvlp/jcrotty/mod_perl-1.24/src/Configuration
> Creating Makefile
>  + configured for Solaris 260 platform
>  + setting C compiler to gcc
>  + setting C pre-processor to gcc -E
>  + checking for system header files
>  + adding selected modules
>  + checking sizeof various data types
>  + doing sanity check on compiler and options
> Creating Makefile in support
> 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: -DSOLARIS2=260 -DUSE_EXPAT -I$(SRCDIR)/lib/expat-lite
> PerlDispatchHandler.enabled
> PerlChildInitHandlerenabled
> PerlChildExitHandlerenabled
> PerlPostReadRequestHandler..enabled
> PerlTransHandlerenabled
> PerlHeaderParserHandler.enabled
> PerlAccessHandler...enabled
> PerlAuthenHandler...enabled
> PerlAuthzHandlerenabled
> PerlTypeHandler.enabled
> PerlFixupHandlerenabled
> PerlHandler.enabled
> PerlLogHandler..enabled
> PerlInitHandler.enabled
> PerlCleanupHandler..enabled
> PerlRestartHandler..enabled
> PerlStackedHandlers.enabled
> PerlMethodHandlers...

compiling mod_perl without root...

2001-02-13 Thread Joseph Crotty

HI all,

Situation:  I have compiled and installed apache_1.3.14/mod_perl-1.24 using
makepl_args.mod_perl.  All this was done as root.  But now of course that I
have the cgi software package dialed in and ready to delivere to production
my boss informs me that we need to be able to compile and delivere without
root or else by-by mod_perl.

Problem:  The whole compile is being done inside of CVS.  That is the apache
is installed in usr/local/apache under current.  But the make install wants
to "install" the apache perl modules, Apache.pm Constants.pm etc, in the
standard perl library.  How do I compile so the apache perl modules get
installed in a place of my choosing???

Thanks,

Joe Crotty 



Compiling mod_perl 1.27 on Win32

2002-06-21 Thread Vladimir Goncharov

Hello All,

 

I am failed to compile mod_perl on Win32 using "Apache mod_perl-1.xx installation 
instructions for Win32" from http://perl.apache.org/win32_compile.html

 

Used software :

 Apache 1.3.26 + mod_ssl 2.8.9

 mod_perl 1.27

 ActivePerl -5.6.1.631-MSWin32-x86

 MS VC++ 6.0

Win2k prof SP2

 

I could compile mod_perl.so using "Building with MS Developer Studio" instructions 
only with three additional steps.

 

First, after

  perl Makefile.PL

  nmake install

I need to add this lines to Makefile

ModuleConfig ::

cd src/modules/perl

$(PERL) -I$(PERL_ARCHLIB) -I$(PERL_LIB) $(XSUBPP) $(XSPROTOARG) 
$(XSUBPPARGS) $*.xs > $*.xsc && $(MV) $*.xsc $*.c

==

and then run "nmake ModuleConfig" to get ModuleConfig.c which is missing without this 
step.

 

 

Second, I need to select "Show directories for: [Include files]", and add

driveletter:\somewhere\APACHE_1.3.26\SRC\OS\WIN32

 

Third, for Apache compiled with mod_ssl, I need to add /D "EAPI" in 
Project/Settings/[C/C++]/"Project Options"

 

Question: Is there mistakes in instructions on 
http://perl.apache.org/win32_compile.html or I did something wrong?



Thanks,

Vladimir






compiling mod_perl statically under FreeBSD

2003-01-25 Thread Илья Шипицин
Dear Sirs,

I tried to follow apaci/README, but I couldn't compile mod_perl statically
under FreeBSD.

can anybody tell me (step by step ?) how to compile statically

www/apache13-modssl + www/mod_perl ?

Thanks!
Ilia Chipitsine




RE: Problem with compiling mod_perl

1999-12-08 Thread Eric Cholet

> I must have now installed mod_perl a dozen times on a dozen machines and 
this is the first time I've come across this problem and I can't seem to 
solve it...nor have I had any luck through FAQs, DejaNews or even newsgroup 
postings :(
>
> I have an RH Linux 6.1 box.  I currently have Apache 1.3.9 running on the 
server.  My problem is when I attempt to compile mod_perl...this is what I 
get...
>
> 
> SSL_BASE=/usr/local perl Makefile.PL EVERYTHING=1 DO_HTTPD=1
> Appending mod_perl to src/Configuration
> Using config file: /usr/home/sysadm/mod_perl-1.21/src/Configuration
> Creating Makefile
>  + configured for Linux platform
>  + setting C pre-processor to gcc -E
>  + checking for system header files
>  + adding selected modules
> o ssl_module uses ConfigStart/End
>   + SSL interface: mod_ssl/2.4.9
>   + SSL interface build type: OBJ
>   + SSL interface compatibility: disabled
>   + SSL interface experimental code: disabled
>   + SSL interface vendor extensions: disabled
>   + SSL interface plugin: Configured DBM (-ldbm)
>   + SSL library path: /usr/local
>   + SSL library version: OpenSSL 0.9.4 09 Aug 1999
>   + SSL library type: installed package (stand-alone)
>   + SSL library plugin mode: none
>  + enabling Extended API (EAPI)
>  + checking sizeof various data types
>  + doing sanity check on compiler and options
> ** A test compilation with your Makefile configuration
> ** failed. This is most likely because your C compiler
> ** is not ANSI. Apache requires an ANSI C Compiler, such
> ** as gcc. The above error message from your compiler
> ** will also provide a clue.
> 
>
> This DOES NOT happen if I attempt to compile Apache on it's own...this 
error only occurs when I attempt to do an HTTPD build through mod_perl. 
 Now the one thing I have discovered is 95% of the time the test 
compilation error is not because of the compiler not supporting ANSI (I'm 
using the latest gcc btw) but is just something failed in the compiling 
whether it be a configuration error, problem running a function etc...  The 
main problem is that I don't receive any additional error messages so I 
don't know what the real problem is.  I have also tried using gcc with the 
-ansi switch as well just to be on the safe side but that didn't help 
either.
>
> Has anyone ever encountered anything like this before?  Or have any ideas 
on what may be causing this error?

Apache was recently patched so that the original error mesage is
printed out, because as you say it's often not a problem with the
compiler being ANSI or not. So you might want to grab a CVS snapshot
of Apache, unless you can wait for 1.3.10 which will be out in a couple
of weeks I believe.

--
Eric



Re: Problem with compiling mod_perl

1999-12-08 Thread Scott Chapman

This looks just like what I saw when I built it on my RH 6.0 setup. 

I recompiled Perl first and it fixed this.

I think what is going on here is that the make file is determing what 
compiler that Perl was compiled with (cc in this case) and using that 
to compile Mod_Perl.  I read somewhere that Mod_Perl has to be 
compiled with gcc and this is the cause of the problem.

YMMV.
--
Scott sends
Happy Trails!



Re: Problem with compiling mod_perl

1999-12-08 Thread Autarch

On Wed, 8 Dec 1999, Craig Vincent wrote:

> I must have now installed mod_perl a dozen times on a dozen machines
> and this is the first time I've come across this problem and I can't
> seem to solve it...nor have I had any luck through FAQs, DejaNews or
> even newsgroup postings :(

> Has anyone ever encountered anything like this before?  Or have any
> ideas on what may be causing this error?

See my previous post about a problem with libgdbm in redhat installs.

Namely, try this:

cd /usr/lib

ln -s libgdbm.so.2.0.0 libgdbm.so


2 to 1 that fixes it.


-Dave


/*==
www.urth.org
We await the New Sun
==*/




Re: Problem with compiling mod_perl

1999-12-08 Thread Craig Vincent

I want to that all of your for your speedy reply and really good advice.
Although I originally had used GCC to compile perl (and was the same
compiler I was trying to use for mod_perl).  By recompiling the perl source
it seemed to fix whatever problem I was having before...perhaps I screwed up
with an optimization handler with the initial perl compilation.  In any case
mod_perl has now been successfully installed on the system I was ready to
toss into oncoming traffic.  So once again thank you.

Sincerely,

Craig Vincent



Compiling mod_perl as a DSO?

2000-01-30 Thread Bill Bradford

Is it possible to compile/install mod_perl as a DSO, on an existing
pre-compiled copy of apache (with mod_so enabled), yet?  If so, 
how?  I couldnt find it in the docs... and I'm tired of having to
statically compile the module in... so any help would be appreciated.

Thanks.

Bill

-- 
+---+--+--+
|Bill Bradford  | [EMAIL PROTECTED] | [EMAIL PROTECTED]|
|http://www.sunhelp.org | http://www.pdp11.org | http://www.mrbill.net|
+---+--+--+



Error compiling mod_perl on linux

2000-04-18 Thread Kenneth Lee

Hi all,

I tried to compile mod_perl with Apache on RedHat 6.1 and perl 
5.005_03, it gave me thousands of unresolved references when compiling 
httpd.c. I then went thru the FAQs on the Web, and it told me that my 
perl maybe corrupted. Then I go to grab the latest perl 5.6.0 source, 
compiled and installed it successfully. This time when I build Apache 
again, it dies even earlier. 

Below shows all the steps I used to built it:

# cd apache_1.3.12
# ./configure --prefix=/www

# cd ../php-3.0.16
# ./configure --with-apache=../apache_1.3.12 \
> ...other_stuffs...
# make && make install

# cd ../mod_perl-1.21
# perl Makefile.PL EVERYTHING=1 USE_APACI=1
# make && make install

# cd ../apache_1.3.12
# ./configure --prefix=/www \
> --enable-module=most \
> --activate-module=src/modules/php3/libphp3.a \
> --activate-module=src/modules/perl/libperl.a
# make   (died here)
[...snipped]
===> src/modules/perl
cc -O2 -g -DDEBUGGING -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE
_SOURCE -D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.6.0/i686-linux/CORE  -DMOD
_PERL_VERSION=\"1.21\" -DMOD_PERL_STRING_VERSION=\"mod_perl/1.21\" -I../..  
-I/usr/lib/perl5/5.6.0/i686-linux/CORE  -I../../os/unix -I../../include   -D
LINUX=2 -DMOD_PERL -DUSE_PERL_SSI -DDEBUGGING -fno-strict-aliasing -I/usr/lo
cal/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DUSE_HSREGEX -DUSE_E
XPAT -I../../lib/expat-lite -DNO_DL_NEEDED `../../apaci` -c mod_perl.c
mod_perl.c: In function `perl_handler':
mod_perl.c:783: `PL_siggv' undeclared (first use in this function)
mod_perl.c:783: (Each undeclared identifier is reported only once
mod_perl.c:783: for each function it appears in.)
make[4]: *** [mod_perl.o] Error 1
make[3]: *** [all] Error 1
make[2]: *** [subdirs] Error 1
make[2]: Leaving directory `/depot/apache_1.3.12/src'
make[1]: *** [build-std] Error 2
make[1]: Leaving directory `/depot/apache_1.3.12'
make: *** [build] Error 2


Attached are the outputs of perl -V of both versions.
Any help would be greatly appreciated.

Kenneth

Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration:
  Platform:
osname=linux, osvers=2.2.5-22smp, archname=i386-linux
uname='linux porky.devel.redhat.com 2.2.5-22smp #1 smp wed jun 2 09:11:51 edt 1999 
i686
unknown '
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef useperlio=undef d_sfio=undef
  Compiler:
cc='cc', optimize='-O2', gccversion=egcs-2.91.66 19990314/Linux (egcs-1.1.2 
release)
cppflags='-Dbool=char -DHAS_BOOL -I/usr/local/include'
ccflags ='-Dbool=char -DHAS_BOOL -I/usr/local/include'
stdchar='char', d_stdstdio=undef, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
alignbytes=4, usemymalloc=n, prototype=define
  Linker and Libraries:
ld='cc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib
libs=-lnsl -ldl -lm -lc -lposix -lcrypt
libc=, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
cccdlflags='-fpic', lddlflags='-shared -L/usr/local/lib'


Characteristics of this binary (from libperl): 
  Built under linux
  Compiled at Aug 30 1999 23:09:51
  @INC:
/usr/lib/perl5/5.00503/i386-linux
/usr/lib/perl5/5.00503
/usr/lib/perl5/site_perl/5.005/i386-linux
/usr/lib/perl5/site_perl/5.005
.

Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
  Platform:
osname=linux, osvers=2.2.12-20, archname=i686-linux
uname='linux tongtong.alfacomtech.com 2.2.12-20 #1 mon sep 27 10:40:35 edt 1999 
i686
unknown '
config_args='-der'
hint=previous, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define 
use64bitint=undef use64bitall=undef uselongdouble=undef usesocks=undef
  Compiler:
cc='cc', optimize='-O2 -g', gccversion=egcs-2.91.66 19990314/Linux (egcs-1.1.2 
release)
cppflags='-DDEBUGGING -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64'
ccflags ='-DDEBUGGING -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64'
stdchar='char', d_stdstdio=define, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
alignbytes=4, usemymalloc=n, prototype=define
  Linker and Libraries:
ld='cc', ldflags =' -L/usr/local/lib'
libpth=/usr/local/lib /lib /usr/lib
libs=-lnsl -lndbm -lgdbm -ldb -ldl -lm -lc -lposix -lcrypt
libc=/lib/libc-2.1.2.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic'
cccdlflags='-fpic', lddlflags='-shared -L/us

Compiling mod_perl on Windows NT

2000-04-26 Thread Steve Hay

Hi,

I've just been building Perl 5.6.0 / mod_perl 1.23 / Apache 1.3.12 on
Windows NT and found something which may be of some use.

The Apache installation does not seem to copy the headers and library
files from the build directory into the install directory (which it DOES
on Unix), so to build mod_perl you need to keep that Apache build build
directory handy.

I found that manually copying

apache_1.3.12\src\include
apache_1.3.12\src\os\win32\*.h
apache_1.3.12\src\CoreR\ApacheCore.lib

into the install directory and then pointing the DevStudio
include/library paths at these locations in the install directory works
fine, thus removing the need to keep the build directory floating about.

This presumably means that I can now ditch the build directory and still
be able to build mod_perl 1.24 when it comes using only my Apache
install directory.

- Steve Hay





Re: compiling mod_perl for solaris

2000-09-27 Thread Doug MacEachern

On Fri, 1 Sep 2000, Joseph Sirucka - Netics wrote:

> Hi People
> 
> I've been trying to compile mod_perl for solaris 8 recently and I
> recompiled perl 5.6.0 with _ubincompat5005 and -Uuselargefiles.
> 
> But no matter what I do with with mod_perl to compile it at
> perl Makefile.PL blah i get this error
> 
> ld.so.1: perl: fatal: relocation error: file
> /usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/auto/HTML/Parser/Parser.so:
> 
> symbol perl_get_hv: referenced symbol not found
> Killed

if you recompiled Perl with -Ubincompat5005, then you also need to
recompile any xs site-perl modules, e.g. HTML::Parser





Re: trouble compiling mod_perl-1.24_01

2000-11-22 Thread peter brown

glad to help
would anyone else be interested in a FreeBSD port to do this ??

At 02:23 PM 22/11/00 -0500, you wrote:
>Thanks!  I finally did a dirty hack but this sounds like a good way to
>fix it right.  I'll have to do that as soon as I get a chance.
>
>-Jere
>
>peter brown wrote:
> >
> > hi jere
> > i am running FreeBSD 4.1.1 at work and i have worked out the best way
> > to do a static compile of mod_perl with apache installed as a port
> >
> > i followed stas's mod_perl guide and changed it to work with FreeBSD
> > steps as follows
> >
> > # cd /usr/ports/www/apache13
> >
> > edit Makefile
> > add thisline in CONFIGURE_ARGS section
> > --activate-module=src/modules/perl/libperl.a
> >
> > # make extract
> > # cd /mod_perl_src_directory/
> > # perl Makefile.PL \
> > APACHE_SRC=/usr/ports/www/apache13/work/apache_1.3.14/src/ \
> > NO_HTTPD=1 \
> > USE_APACI=1 \
> > PREP_HTTPD=1 \
> > EVERYTHING=1
> > # make
> > # make test
> > # make install
> > # cd /usr/ports/www/apache13
> > # make
> > # make install
> >
> > works like a charm :)
> > i am thinking of writing a port to do this and submitting it
> >
> > happy mod_perling :)
> >
> > At 12:07 AM 15/11/00 -0500, you wrote:
> > >I'm on a FreeBSD 3.4-RELEASE box and I've just built and tested apache
> > >1.3.14 from source.  Then I try to build mod_perl with the following
> > >commands and get the errors below.
> > >
> > >The full text of the process can be seen at
> > >http://www.StageRigger.com/mod_perl-1.24_01.log
> > >
> > >Has anyone run into this?  Suggestions?
> > >
> > >Thanks,
> > >-Jere Julian
> > >--
> > >   +---+
> > >   | Jere C Julianmailto:[EMAIL PROTECTED]  |
> > >   | Network Designer/Manager, Rigger, Sound Engineer  |
> > >   |http://www.StageRigger.com/|
> > >   +---+
> > >
> > >perl Makefile.PL APACHE_SRC=../apache_1.3.14/src DO_HTTPD=1 USE_APACI=1
> > >
> > >
> > >make
> > >
> > >...
> > >cp Server.pm ../blib/lib/Apache/Server.pm
> > >mkdir ../blib/arch/auto/Apache/Server
> > >mkdir ../blib/lib/auto/Apache/Server
> > >cp Symbol.pm ../blib/lib/Apache/Symbol.pm
> > >/usr/bin/perl -I/usr/local/lib/perl5/5.6.0/i386-freebsd
> > >-I/usr/local/lib/perl5/5.6.0 /usr/local/lib/perl5/5.6.0/ExtUtils/xsubpp
> > >-typemap /usr/local/lib/perl5/5.6.0/ExtUtils/typemap Symbol.xs >
> > >Symbol.xsc && mv Symbol.xsc Symbol.c
> > >cc -c  -I/usr/local/include -O  -DVERSION=\"1.31\"
> > >-DXS_VERSION=\"1.31\" -DPIC -fpic
> > >-I/usr/local/lib/perl5/5.6.0/i386-freebsd/CORE  Symbol.c
> > >Symbol.xs: In function `XS_Apache__Symbol_cv_const_sv':
> > >Symbol.xs:106: `na' undeclared (first use this function)
> > >Symbol.xs:106: (Each undeclared identifier is reported only once
> > >Symbol.xs:106: for each function it appears in.)
> > >*** Error code 1
> > >
> > >Stop.
> > >*** Error code 1
> > >
> > >Stop.
>
>
>--
>   +---+
>   | Jere C Julianmailto:[EMAIL PROTECTED]  |
>   | Network Designer/Manager, Rigger, Sound Engineer  |
>   |  http://www.StageRigger.com/~julianje/|
>   +---+


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




Re: trouble compiling mod_perl-1.24_01

2000-12-21 Thread Doug MacEachern

On Wed, 15 Nov 2000, Jere C. Julian, Jr. wrote:

> I'm on a FreeBSD 3.4-RELEASE box and I've just built and tested apache
> 1.3.14 from source.  Then I try to build mod_perl with the following
> commands and get the errors below.
...
> Symbol.xs:106: `na' undeclared (first use this function)
> Symbol.xs:106: (Each undeclared identifier is reported only once
> Symbol.xs:106: for each function it appears in.)

this is supposed to be taken care of in Symbol.xs:
#include "patchlevel.h" 
#if ((PATCHLEVEL >= 4) && (SUBVERSION >= 76)) || (PATCHLEVEL >= 5) 
#define na PL_na 
#endif 

which probably means you have a bogus patchlevel.h (from an old tcl
install) in /usr/local/include either delete that or move it aside.  the
right thing for Symbol.xs todo is not to use na at all, patch below.

Index: Symbol/Symbol.xs
===
RCS file: /home/cvs/modperl/Symbol/Symbol.xs,v
retrieving revision 1.4
diff -u -r1.4 Symbol.xs
--- Symbol/Symbol.xs1998/11/24 19:10:56 1.4
+++ Symbol/Symbol.xs2000/12/22 06:01:06
@@ -2,11 +2,6 @@
 #include "perl.h"
 #include "XSUB.h"
 
-#include "patchlevel.h" 
-#if ((PATCHLEVEL >= 4) && (SUBVERSION >= 76)) || (PATCHLEVEL >= 5) 
-#define na PL_na 
-#endif 
-
 #ifdef PERL_OBJECT
 #define sv_name(svp) svp
 #define undef(ref) 
@@ -102,8 +97,10 @@
mg_get(sv);
sym = SvPOKp(sv) ? SvPVX(sv) : Nullch;
}
-   else
-   sym = SvPV(sv, na);
+   else {
+STRLEN n_a;
+sym = SvPV(sv, n_a);
+}
if(sym)
cv = perl_get_cv(sym, TRUE);
break;




RE: compiling mod_perl without root...

2001-02-13 Thread Joseph Crotty

Ged,

Thanks for the reply.  The heart of the problem is we need to compile
apache/mod_perl from source(i.e. apache_1.3.14.tar.gz and
mod_perl1-1.25.tar.gz) which lives in cvs.  The machine cvs resides on is
not the target machine for the apache/mod_perl install.  The plan is to
compile it and install it in a directory in cvs current, and then package
the whole thing up using the SUN package utilities.

To complicate matters we need to build apache/mod_perl from the cvs source
under a group other than root.  So I run as someone other then root, the
compile goes fine, but when make install comes I get the following:

Warning: You do not have permissions to install into
/usr/local/lib/perl5/site_perl/5.6.0 at
/usr/local/lib/perl5/5.6.0/ExtUtils/Install.pm line 62.
Cannot forceunlink /usr/local/man/man3/Apache.3: Permission denied at
/usr/local/lib/perl5/5.6.0/File/Find.pm line 475
make: Fatal error: Command failed for target `pure_site_install'

I assume its upset because /usr/local/lib/perl5/site_perl/5.6.0 is 
drwxr-xr-x  30 root other   2560 Nov 29 11:28 5.6.0

I don't know where to get a binary distribution of apache_x.x.x/mod_perl-x.x
so it looks like I am stuck if I want to compile with other than rootor
else edit the makefile.PL which sounds dreadful.

-Original Message-
From: G.W. Haywood [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, February 13, 2001 2:21 PM
To: Joseph Crotty
Cc: [EMAIL PROTECTED]
Subject: Re: compiling mod_perl without root...


Hi there,

On Tue, 13 Feb 2001, Joseph Crotty wrote:

> How do I compile so the apache perl modules get
> installed in a place of my choosing???

You can just copy them there yourself.  Then all you have to do is set
the @INC paths so they can be found at runtime.  I think you'll find
all you need about that in the Guide.  http://perl.apache.org/guide

But you still need to be root to attach to port 80, so root has to
start the server unless it's only going to listen to ports > 1024.

73,
Ged.



Re: compiling mod_perl without root...

2001-02-13 Thread G.W. Haywood

Hi there,

On Tue, 13 Feb 2001, Joseph Crotty wrote:

> How do I compile so the apache perl modules get
> installed in a place of my choosing???

You can just copy them there yourself.  Then all you have to do is set
the @INC paths so they can be found at runtime.  I think you'll find
all you need about that in the Guide.  http://perl.apache.org/guide

But you still need to be root to attach to port 80, so root has to
start the server unless it's only going to listen to ports > 1024.

73,
Ged.




RE: compiling mod_perl without root...

2001-02-13 Thread Stas Bekman

On Tue, 13 Feb 2001, Joseph Crotty wrote:

> Ged,
>
> Thanks for the reply.  The heart of the problem is we need to compile
> apache/mod_perl from source(i.e. apache_1.3.14.tar.gz and
> mod_perl1-1.25.tar.gz) which lives in cvs.

As Ged has mentioned, you need to read the guide:
http://perl.apache.org/guide/install.html#Installation_Without_Superuser_P

_
Stas Bekman  JAm_pH --   Just Another mod_perl Hacker
http://stason.org/   mod_perl Guide  http://perl.apache.org/guide
mailto:[EMAIL PROTECTED]   http://apachetoday.com http://logilune.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/





compiling mod_perl with Apaci 1.3_19

2001-04-19 Thread Murat Balkas


Hi,

I'm having troubles when compiling mod_perl with 1.3_19. My configuration
is below and my problem is that I can't force mod_perl to use gcc as
compiler. On the creating process of Makefile, gcc is used as compiler, but
when I 'make', at the beginning it uses gcc, but when cd'ed to Leak
directory, it tries to use 'cc' again.

Solaris 2.8 with apache 1.3_19, perl 5.6.0.




Compiling mod_perl 1.99 on Solaris 8

2002-04-18 Thread Darragh Sherwin

Hi,
I am trying to compile mod_perl 1.99 with apacche 2.0.35, I give  up with 
mod_perl 1.24 after numberous headaches and lots of profanties.

It build configured Apache with following options :

  ./configure --with-mpm=prefork --prefix=/export/home/website/apache 
--enable-so --with-port=80 --enable-info

I then did a make and make install for Apache
Then  I configured mod_perl with the following options:

  perl Makefile.PL MP_AP_PREFIX=../httpd-2.0.35
(httpd-2.0.35 is the source of apache)

then I edit all the Makefiles for mod_perl, so the compiler use the 
option "-DUSE_ITHREADS", then I did a make and make install,
I got out a mod_perl.so file and put this under the Apache 
$PREFIX/modules and edit my httpd.conf to correspond,
when I start apache, I get the following error:

Cannot load /export/home/website/apache/modules/mod_perl.so into server: 
ld.so.1: /export/home/website/apache/bin/httpd: fatal: relocation error: 
file /export/home/website/apache/modules/mod_perl.so: symbol PL_thr_key: 
referenced symbol not found


Can anybody tell me, if I am configuring something wrong, or building it 
the wrong way??
I need to get a quick resolution to this problem, so any help is greatly 
appreciated

Thank you

-- 
___
Darragh Sherwin
[EMAIL PROTECTED]

"To alcohol, the cause of, and solution to, all of life's problems"
Homer Simpson




Re: Compiling mod_perl 1.27 on Win32

2002-06-21 Thread Randy Kobes

On Fri, 21 Jun 2002, Vladimir Goncharov wrote:

> Hello All, I am failed to compile mod_perl on Win32 using
> "Apache mod_perl-1.xx installation instructions for Win32"
> from http://perl.apache.org/win32_compile.html
>
> Used software :
>  Apache 1.3.26 + mod_ssl 2.8.9
>  mod_perl 1.27
>  ActivePerl -5.6.1.631-MSWin32-x86
>  MS VC++ 6.0
> Win2k prof SP2
>
> I could compile mod_perl.so using "Building with MS Developer
> Studio" instructions only with three additional steps.
>
> First, after
>
>   perl Makefile.PL
>   nmake install
> I need to add this lines to Makefile
>
> ModuleConfig ::
>
> cd src/modules/perl
>
> $(PERL) -I$(PERL_ARCHLIB) -I$(PERL_LIB) $(XSUBPP)
> $(XSPROTOARG) $(XSUBPPARGS) $*.xs > $*.xsc && $(MV) $*.xsc
> $*.c
>
> ==
> and then run "nmake ModuleConfig" to get ModuleConfig.c which
> is missing without this step.

Thanks for pointing that out ... ModuleConfig builds when using
the 'perl Makefile.PL APACHE_SRC=...' method, described later on
in the page, so something seems missing when using the Developer
Studio method. I'll look into that 

> Second, I need to select "Show directories for: [Include
> files]", and add
>
> driveletter:\somewhere\APACHE_1.3.26\SRC\OS\WIN32

This is mentioned in the docs, but very briefly - perhaps it
could be given more prominence 

> Third, for Apache compiled with mod_ssl, I need to add /D
> "EAPI" in Project/Settings/[C/C++]/"Project Options"

This is missing in the Developer Studio docs, and should be added
(it is available in the 'perl Makefile.PL  EAPI=1' way of
building). I'll add it to the docs.

> Question: Is there mistakes in instructions on
> http://perl.apache.org/win32_compile.html or I did something
> wrong?

As long as 'nmake test' passes all tests, things are probably
fine ... I'll look into the issues above - thanks.

best regards,
randy kobes




Trouble Compiling Mod_Perl 1.27 on SGI

2002-10-14 Thread Kent, Mr. John

Greetings,

Having trouble building mod_perl-1.27 against Apache_1.3.27 on an SGI

Gettting:

Will run tests as User: 'webuser' Group: 'webgroup'
(cd ../apache_1.3.27 && CC="cc -n32" CFLAGS=" -D_BSD_TYPES -D_BSD_TIME -woff
1184 1552 -OPT:Olimit=0:space=ON -I/usr/local/include -DLANGUAGE_C"
./configure --activate-module=src/modules/perl/libperl.a
--disable-rule=EXPAT --prefix=/users/webuser/apache_heavy)
Configuring for Apache, Version 1.3.27
 + using installation path layout: Apache (config.layout)
 + activated perl module (modules/perl/libperl.a)
Creating Makefile
Creating Configuration.apaci in src
Creating Makefile in src
You are running 64-bit Irix. For now, we will compile 32-bit
but if you would care to port to 64-bit, send us the patches.
 + configured for SGI IRIX-64 platform
 + setting C pre-processor to cc -n32 -E
 + checking for system header files
 + adding selected modules
o perl_module uses ConfigStart/End
  + mod_perl build type: OBJ
  + id: mod_perl/1.27
  + id: Perl/v5.8.0 (irix) [perl]
  + setting up mod_perl build environment
  + adjusting Apache build environment
 + checking sizeof various data types
 + doing sanity check on compiler and options
** A test compilation with your Makefile configuration
** failed.  The below error output from the compilation
** test will give you an idea what is failing. Note that
** Apache requires an ANSI C Compiler, such as gcc. 

 Error Output for sanity check 
cd ..; cc -n32  -DIRIX -DMOD_PERL -DUSE_HSREGEX -DNO_DL_NEEDED
-D_BSD_TYPES -D_BSD_TIME -woff 1184 1552 -OPT:Olimit=0:space=ON
-I/usr/local/include -DLANGUAGE_C `./apaci` -o helpers/dummy
helpers/dummy.c   -L/usr/local/lib32 -L/usr/local/lib -Wl,-woff,84
/users/webuser/perl/lib/5.8.0/IP25-irix/auto/DynaLoader/DynaLoader.a
-L/users/webuser/perl/lib/5.8.0/IP25-irix/CORE -lperl -lm -lc 
ld32: FATAL 9: I/O error (1552): No such file or directory
*** Error code 2 (bu21)
= End of Error Report =

Tried it on several different SGI boxes with the same result.

Any suggestions would be appreciated.

Thank You,

John Kent
Monterey, CA



make error compiling mod_perl on RH7.1

2002-11-08 Thread Witchy
Hi all,

Trying to compile mod_perl 2.0 for my RH7.1/Apache 2.0.39 server and it
falls over with this error:

apr_perlio.c: In function `apr_perlio_apr_file_to_glob':
apr_perlio.c:573: `IoTYPE_WRONLY' undeclared (first use in this function)
apr_perlio.c:573: (Each undeclared identifier is reported only once
apr_perlio.c:573: for each function it appears in.)
apr_perlio.c:577: `IoTYPE_RDONLY' undeclared (first use in this function)
make[3]: *** [apr_perlio.o] Error 1
make[3]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR/PerlIO'
make[2]: *** [subdirs] Error 2
make[2]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR'
make[1]: *** [subdirs] Error 2
make[1]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs'
make: *** [subdirs] Error 2

When I ran 'perl Makefile.PL' etc with the correct location for my apache
setup the only thing it complained about was the fact I was using Perl 5.6.0
and it recommended 5.6.1 or above. Before I trawl the dependencies tree
trying to install a later version has anyone seen that problem before and do
I really need to upgrade my perl installation?

Thanks in advance,

--
adrian/witchy
www.binarydinosaurs.co.uk - the online computer museum
www.snakebiteandblack.co.uk - monthly gothic shenanigans




Problem compiling mod_perl 1.27 on Windows

2002-12-16 Thread Steve Hay
Hi,

I'm having trouble compiling mod_perl 1.27 (with Apache 1.3.27 / Perl 
5.8.0) on Windows (XP SP1 with MS VC++ 6.0 SP5).

It builds fine with Perl 5.8.0 standard sources, but I'm just trying to 
upgrade my Perl to the slightly patched sources that ActivePerl Build 
804 uses.  I've built Perl from these new sources with the same build 
options that I used before for the standard source build (no threading, 
and Perl's malloc).  (The output of "Perl -V" is at the bottom of this 
mail.)

I run the following commands to build mod_perl:

   perl Makefile.PL APACHE_SRC=C:/apache INSTALL_DLL=C:/apache/modules EAPI
   nmake

The first command runs fine, but the second has the following error:

   Apache.xs(1963) : error C2115: '=' : incompatible types

The line referred to by this error is:

   statcache = r->finfo;

I've no idea why this should be causing a problem with the new Perl.  If 
I switch the Perl that I'm building against back to the standard 5.8.0 
(by simply re-naming directories) and then re-run the "nmake" command 
above then mod_perl compiles and links with no errors.

Can anyone shed any light on this?

- Steve

=

Summary of my perl5 (revision 5 version 8 subversion 0) configuration:
 Platform:
   osname=MSWin32, osvers=4.0, archname=MSWin32-x86-perlio
   uname=''
   config_args='undef'
   hint=recommended, useposix=true, d_sigaction=undef
   usethreads=undef use5005threads=undef useithreads=undef 
usemultiplicity=undef
   useperlio=define d_sfio=undef uselargefiles=define usesocks=undef
   use64bitint=undef use64bitall=undef uselongdouble=undef
   usemymalloc=y, bincompat5005=undef
 Compiler:
   cc='cl', ccflags ='-nologo -Gf -W3 -MD -DNDEBUG -O1 -DWIN32 
-D_CONSOLE -DNO_STRICT -DHAVE_DES_FCRYPT  -DUSE_PERLIO 
-DPERL_MSVCRT_READFIX',
   optimize='-MD -DNDEBUG -O1',
   cppflags='-DWIN32'
   ccversion='', gccversion='', gccosandvers=''
   intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234
   d_longlong=undef, longlongsize=8, d_longdbl=define, longdblsize=10
   ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='__int64', 
lseeksize=8
   alignbytes=8, prototype=define
 Linker and Libraries:
   ld='link', ldflags ='-nologo -nodefaultlib -release  
-libpath:"C:\perl5\lib\CORE"  -machine:x86'
   libpth=C:\PROGRA~1\MICROS~2\VC98\lib C:\openssl\lib
   libs=libeay32.lib  oldnames.lib kernel32.lib user32.lib gdi32.lib 
winspool.lib  comdlg32.lib advapi32.lib shell32.lib ole32.lib 
oleaut32.lib  netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib  
version.lib odbc32.lib odbccp32.lib msvcrt.lib
   perllibs=libeay32.lib  oldnames.lib kernel32.lib user32.lib 
gdi32.lib winspool.lib  comdlg32.lib advapi32.lib shell32.lib ole32.lib 
oleaut32.lib  netapi32.lib uuid.lib wsock32.lib mpr.lib winmm.lib  
version.lib odbc32.lib odbccp32.lib msvcrt.lib
   libc=msvcrt.lib, so=dll, useshrplib=yes, libperl=perl58.lib
   gnulibc_version='undef'
 Dynamic Linking:
   dlsrc=dl_win32.xs, dlext=dll, d_dlsymun=undef, ccdlflags=' '
   cccdlflags=' ', lddlflags='-dll -nologo -nodefaultlib -release  
-libpath:"C:\perl5\lib\CORE"  -machine:x86'


Characteristics of this binary (from libperl):
 Compile-time options: USE_LARGE_FILES
 Built under MSWin32
 Compiled at Dec 13 2002 08:42:43
 @INC:
   C:/perl5/lib
   C:/perl5/site/lib
   .




Re: compiling mod_perl statically under FreeBSD

2003-01-26 Thread Nick Tonkin
On Sun, 26 Jan 2003, [koi8-r] éÌØÑ ûÉÐÉÃÉÎ wrote:

> Dear Sirs,
> 
> I tried to follow apaci/README, but I couldn't compile mod_perl statically
> under FreeBSD.
> 
> can anybody tell me (step by step ?) how to compile statically
> 
> www/apache13-modssl + www/mod_perl ?
> 
> Thanks!
> Ilia Chipitsine
> 
> 

Have you read the mod_perl guide? Especially
http://perl.apache.org/docs/1.0/guide/install.html#Installation_Scenarios_for_mod_perl_and_Other_Components
?

- nick

   
Nick Tonkin   {|8^)>





Re: [PATCH] Compiling mod_perl with ActivePerl

1999-12-21 Thread Doug MacEachern

On Tue, 7 Sep 1999, Jochen Wiedmann wrote:

> 
> Hi,
> 
> attached you find a somewhat larger patch as a first step in order to
> get mod_perl running with ActivePerl. This is mainly to get the public
> source tree in sync with my work: I am still far away from getting it
> running. What I did so far is eliminate compiler problems, except for
> about 5 or 6 compiler errors that seem somewhat deeper.

sorry for the looong delay, I have applied your patch to the cvs tree.
however, I have no way to test ActivePerl or vanilla win32 at the moment.



Re: Compiling mod_perl as a DSO?

2000-01-30 Thread Michael Robinton

On Sun, 30 Jan 2000, Bill Bradford wrote:

> Is it possible to compile/install mod_perl as a DSO, on an existing
> pre-compiled copy of apache (with mod_so enabled), yet?  If so, 
> how?  I couldnt find it in the docs... and I'm tired of having to
> statically compile the module in... so any help would be appreciated.
> 
I read on the list at one time that the DSO verson has a memory leak. 
Don't know if this is still true or not. The static version apparently 
did not have that problem. If someone knows the answer to this I'd like 
to know myself as the DSO version is considerably easier to put together 
with other modules.

Michael



Re: Compiling mod_perl as a DSO?

2000-01-31 Thread Bill Jones

>> Is it possible to compile/install mod_perl as a DSO, on an existing
>> pre-compiled copy of apache (with mod_so enabled), yet?  If so,
>> how?  I couldnt find it in the docs... and I'm tired of having to
>> statically compile the module in... so any help would be appreciated.
>> 
> I read on the list at one time that the DSO verson has a memory leak.
> Don't know if this is still true or not. The static version apparently
> did not have that problem. If someone knows the answer to this I'd like
> to know myself as the DSO version is considerably easier to put together
> with other modules.


Plus my studies this weekend indicate that other
conflicting issues come up...

Better to go hybrid - static mod_perl, and
DSO whatever you are able to DSO...

Bill Jones * Systems Programmer * http://www.fccj.org/cgi/mail?sneex

   ('>   Running -
   //\   Perl, Apache, MySQL, PHP3,
   v_/_  Ultra 10, LinuxPPC, BeOS...



Re: Compiling mod_perl as a DSO?

2000-01-31 Thread Bill Jones

After much fighting - 2/3 success  :/  Better than nothing :]

> Server Version: Apache/1.3.12-dev (Unix) mod_perl/1.21_01-dev
> Server Built: Jan 31 2000 10:55:04
> API Version: 19990320:6
> Run Mode: standalone
> User/Group: sneex(69)/69
> Hostname/port: insecurity.org:80
> Daemons: start: 5    min idle: 5    max idle: 10    max: 150
> Max Requests: per child: 0    keep alive: on    max per connection: 100
> Threads: per child: 0   
> Excess requests: per child: 0   
> Timeouts: connection: 300    keep-alive: 15
> Server Root: /usr/local/apache
> Config File: conf/httpd.conf
> PID File: /usr/local/apache/logs/httpd.pid
> Scoreboard File: /usr/local/apache/logs/httpd.scoreboard


Integrating PHP4 is my next battle - wish me luck...

Thanks to all who helped!  -Sneex-  :]

Bill Jones * Systems Programmer * http://www.fccj.org/cgi/mail?sneex

   ('>   Running -
   //\   Perl, Apache, MySQL, PHP3,
   v_/_  Ultra 10, LinuxPPC, BeOS...


> From: Bill Jones <[EMAIL PROTECTED]>
> Date: Mon, 31 Jan 2000 09:42:16 -0500
> To: <[EMAIL PROTECTED]>
> Subject: Re: Compiling mod_perl as a DSO?
> 
>>> Is it possible to compile/install mod_perl as a DSO, on an existing
>>> pre-compiled copy of apache (with mod_so enabled), yet?  If so,
>>> how?  I couldnt find it in the docs... and I'm tired of having to
>>> statically compile the module in... so any help would be appreciated.
>>> 
>> I read on the list at one time that the DSO verson has a memory leak.
>> Don't know if this is still true or not. The static version apparently
>> did not have that problem. If someone knows the answer to this I'd like
>> to know myself as the DSO version is considerably easier to put together
>> with other modules.
> 
> 
> Plus my studies this weekend indicate that other
> conflicting issues come up...
> 
> Better to go hybrid - static mod_perl, and
> DSO whatever you are able to DSO...
> 
> Bill Jones * Systems Programmer * http://www.fccj.org/cgi/mail?sneex
> 
> ('>   Running -
> //\   Perl, Apache, MySQL, PHP3,
> v_/_  Ultra 10, LinuxPPC, BeOS...
> 
> 



Re: Compiling mod_perl as a DSO?

2000-01-31 Thread Matt Sergeant

I'm not sure why people are struggling with this so much this week. Here's
what to do in a nutshell:

download and untar apache
download and untar modperl - at the same directory level.

cd modperl
perl Makefile.PL \
EVERYTHING=1 \
APACHE_PREFIX=/usr/apache \
ADD_MODULE=log_referer,rewrite,proxy,so,vhost_alias,mime_magic,expires \
DYNAMIC=1 USE_APACI=1
make
su
make install

To build DSO libraries just make sure you now use apxs from /usr/apache/bin.

On Mon, 31 Jan 2000, Bill Jones wrote:
> After much fighting - 2/3 success  :/  Better than nothing :]
> 
> > Server Version: Apache/1.3.12-dev (Unix) mod_perl/1.21_01-dev
> > Server Built: Jan 31 2000 10:55:04
> > API Version: 19990320:6
> > Run Mode: standalone
> > User/Group: sneex(69)/69
> > Hostname/port: insecurity.org:80
> > Daemons: start: 5    min idle: 5    max idle: 10    max: 150
> > Max Requests: per child: 0    keep alive: on    max per connection: 100
> > Threads: per child: 0   
> > Excess requests: per child: 0   
> > Timeouts: connection: 300    keep-alive: 15
> > Server Root: /usr/local/apache
> > Config File: conf/httpd.conf
> > PID File: /usr/local/apache/logs/httpd.pid
> > Scoreboard File: /usr/local/apache/logs/httpd.scoreboard
> 
> 
> Integrating PHP4 is my next battle - wish me luck...
> 
> Thanks to all who helped!  -Sneex-  :]
> 
> Bill Jones * Systems Programmer * http://www.fccj.org/cgi/mail?sneex
> 
>('>   Running -
>//\   Perl, Apache, MySQL, PHP3,
>v_/_  Ultra 10, LinuxPPC, BeOS...
> 
> 
> > From: Bill Jones <[EMAIL PROTECTED]>
> > Date: Mon, 31 Jan 2000 09:42:16 -0500
> > To: <[EMAIL PROTECTED]>
> > Subject: Re: Compiling mod_perl as a DSO?
> > 
> >>> Is it possible to compile/install mod_perl as a DSO, on an existing
> >>> pre-compiled copy of apache (with mod_so enabled), yet?  If so,
> >>> how?  I couldnt find it in the docs... and I'm tired of having to
> >>> statically compile the module in... so any help would be appreciated.
> >>> 
> >> I read on the list at one time that the DSO verson has a memory leak.
> >> Don't know if this is still true or not. The static version apparently
> >> did not have that problem. If someone knows the answer to this I'd like
> >> to know myself as the DSO version is considerably easier to put together
> >> with other modules.
> > 
> > 
> > Plus my studies this weekend indicate that other
> > conflicting issues come up...
> > 
> > Better to go hybrid - static mod_perl, and
> > DSO whatever you are able to DSO...
> > 
> > Bill Jones * Systems Programmer * http://www.fccj.org/cgi/mail?sneex
> > 
> > ('>   Running -
> > //\   Perl, Apache, MySQL, PHP3,
> > v_/_  Ultra 10, LinuxPPC, BeOS...
> > 
> >
-- 


Details: FastNet Software Ltd - XML, Perl, Databases.
Tagline: High Performance Web Solutions
Web Sites: http://come.to/fastnet http://sergeant.org
Available for Consultancy, Contracts and Training.



Re: Compiling mod_perl as a DSO?

2000-01-31 Thread Bill Jones

Thanks for responding :)

Question:
ADD_MODULE=log_referer,rewrite,proxy,so,vhost_alias,mime_magic,expires

Is this required?   Why can't I just use APACI_ARGS to get 'all' ?

Bill Jones * Systems Programmer * http://www.fccj.org/cgi/mail?sneex

   ('>   Running -
   //\   Perl, Apache, MySQL, PHP3,
   v_/_  Ultra 10, LinuxPPC, BeOS...

> From: Matt Sergeant <[EMAIL PROTECTED]>
> Date: Mon, 31 Jan 2000 17:19:55 +
> To: Bill Jones <[EMAIL PROTECTED]>, <[EMAIL PROTECTED]>
> Subject: Re: Compiling mod_perl as a DSO?
> 
> I'm not sure why people are struggling with this so much this week. Here's
> what to do in a nutshell:
> 
> download and untar apache
> download and untar modperl - at the same directory level.
> 
> cd modperl
> perl Makefile.PL \
> EVERYTHING=1 \
> APACHE_PREFIX=/usr/apache \
> ADD_MODULE=log_referer,rewrite,proxy,so,vhost_alias,mime_magic,expires \
> DYNAMIC=1 USE_APACI=1
> make
> su
> make install
> 
> To build DSO libraries just make sure you now use apxs from /usr/apache/bin.



Re: Compiling mod_perl as a DSO?

2000-01-31 Thread Matt Sergeant

On Mon, 31 Jan 2000, Bill Jones wrote:
> Thanks for responding :)
> 
> Question:
> ADD_MODULE=log_referer,rewrite,proxy,so,vhost_alias,mime_magic,expires
> 
> Is this required?   Why can't I just use APACI_ARGS to get 'all' ?

While I don't build apache very often, I don't see what configure option
that corresponds to. You'd have to have:

APACI_ARGS='--enable-module="log_referer" --enable-module="rewrite"
--enable-module="proxy" ...'

for each and every module. There's no configure option "all" that I can
see. Am I missing something?

-- 


Details: FastNet Software Ltd - XML, Perl, Databases.
Tagline: High Performance Web Solutions
Web Sites: http://come.to/fastnet http://sergeant.org
Available for Consultancy, Contracts and Training.



Re: Compiling mod_perl as a DSO?

2000-01-31 Thread Bill Jones

>> Question:
>> ADD_MODULE=log_referer,rewrite,proxy,so,vhost_alias,mime_magic,expires
>> 
>> Is this required?   Why can't I just use APACI_ARGS to get 'all' ?
> 
> While I don't build apache very often, I don't see what configure option
> that corresponds to. You'd have to have:
> 
> APACI_ARGS='--enable-module="log_referer" --enable-module="rewrite"
> --enable-module="proxy" ...'
> 
> for each and every module. There's no configure option "all" that I can
> see. Am I missing something?


Yes.  :)  Not to worry, it's hidden in the section just before
List of Available Modules in the INSTALL file.

Re -
Use the --enable-module=NAME and --disable-module=NAME options
to enable or disable a particular already distributed module from
the Apache src/Configuration.tmpl file. The correct module names
(no `mod_' prefix!) and defaults (yes=enabled, no=disabled) can be
seen when running `./configure --help'.  There are two special
NAME variants: `all' for enabling or disabling all modules and
`most' for enabling or disabling only these modules which are
useable on all platforms (currently this is  `all' minus the
modules `auth_db', `log_agent', `log_referer', `example',
`so' and `mmap_static'). For a compact overview of available
modules see the following list (remove the `mod_' prefix
to get the NAME).

HTH, -Sneex-  :]

Bill Jones * Systems Programmer * http://www.fccj.org/cgi/mail?sneex

   ('>   Running -
   //\   Perl, Apache, MySQL, PHP3,
   v_/_  Ultra 10, LinuxPPC, BeOS...




Re: Error compiling mod_perl on linux

2000-04-18 Thread Jeffrey W. Baker

On Tue, 18 Apr 2000, Kenneth Lee wrote:

> Hi all,
> 
> I tried to compile mod_perl with Apache on RedHat 6.1 and perl 
> 5.005_03, it gave me thousands of unresolved references when compiling 
> httpd.c. I then went thru the FAQs on the Web, and it told me that my 
> perl maybe corrupted. Then I go to grab the latest perl 5.6.0 source, 
> compiled and installed it successfully. This time when I build Apache 
> again, it dies even earlier. 

Kenneth,

You need to get mod_perl-1.22:

http://www.perl.com/CPAN-local/modules/by-module/Apache/mod_perl-1.22.tar.gz

-jwb




Compiling mod_perl on HP-UX 10.20

2000-06-16 Thread Guy Saldanha

Hi!

Has anyone had problems compiling mod_perl 1.24 on HP-UX 10.20? No
matter what parameters are passed to perl Makefile.PL, the make is
stopped:

ld -b -s -a shared -o libperl.so mod_perl.lo perlxsi.lo
perl_config.lo perl_util.lo perlio.lo mod_perl_opmask.lo  Apache.lo
Constants.lo Connection.lo Server.lo -Wl,-E -Wl,-B,deferred  
/opt/perl5/lib/5.00503/PA-RISC1.1/auto/DynaLoader/DynaLoader.a
-L/opt/perl5/lib/5.00503/PA-RISC1.1/CORE -lperl -lnsl_s -lndbm -ldld -lm
-lc -lndir -lcrypt 
ld: Unrecognized argument: -Wl,-E
ld: Usage:  ld flags... files...
*** Error exit code 1

Stop.

I'd be very grateful for help.

Guy.



Pb compiling mod_perl (1.21 to 1.24.01)

2000-11-14 Thread Laurent Perez

Hi list

I can't get mod_perl to compile with my apache_source.
I always get ' /usr/bin/ld : cannot find -lgdbm : No such file or 
directory ' with 'make'.
I'm running a Debian 2.2 box, i added /usr/lib to ld.so.conf, and 
libgdbmg1 is installed.

Thanks for your answer

Laurent





Re: Compiling mod_perl into Apache 1.3.14

2001-01-25 Thread andrewl

I've been otherwise occupied for a while and am finally able to spend a few
moments, once again, on trying to get mod_perl compiled into Apache.

I am using:
Apache 1.3.14
Perl 5.6.0
mod_perl-1.24_01
on Linux 2.2.16

I have a string of arguments that I would like to pass to the compile routine
at, I believe, the
%perl Makefile.PL
stage.  These are contained in a file supplied by our esteemed colleague, G.W.
Haywood, in a file
called makepl_args.mod_perl.

Would the syntax for inclusion be
%perl Makefile.PL < makepl_args.mod_perl

I'm not certain how to pass the arguments contained in this file to the
execution process without typing them out line by line.

Also, if anyone know of the existence of an Apache server configuration that is
vanilla but will support proxy and mod_perl, and is in binary form for Redhat
Linux 7.0, I am ready to give up on trying to become a guru on this.  I am all
out of time and just need to get this going ASAP.

And if G. W. Haywood has his ears on, would you be willing to answer this
question.  If I change the value for the Apache_prefix to something like
/usr/local/apache2 would I be able to set up a whole separate test server, and
then run this on something like port "5080"?  I need to keep my current server
running while I try to implement mod_perl and the Perl::DBI interface (with the
original goal still in mind to allow access and editing of a mySQL database).

TIA,
Andrew Lietzow







Re: Compiling mod_perl into Apache 1.3.14

2001-01-25 Thread G.W. Haywood

Hi Andrew,

On Thu, 25 Jan 2001, andrewl wrote:

> Would the syntax for inclusion be
> %perl Makefile.PL < makepl_args.mod_perl

Nope.  Just put the makepl_args.mod_perl file in the mod_perl
top-level directory, where you found Makefile.PL.

Then you just say:

% perl Makefile.PL

73,
Ged.




Re: Compiling mod_perl 1.99 on Solaris 8

2002-04-18 Thread Stas Bekman

Darragh Sherwin wrote:
> Hi,
> I am trying to compile mod_perl 1.99 with apacche 2.0.35, I give  up 
> with mod_perl 1.24 after numberous headaches and lots of profanties.
> 
> It build configured Apache with following options :
> 
>  ./configure --with-mpm=prefork --prefix=/export/home/website/apache 
> --enable-so --with-port=80 --enable-info
> 
> I then did a make and make install for Apache
> Then  I configured mod_perl with the following options:
> 
>  perl Makefile.PL MP_AP_PREFIX=../httpd-2.0.35
> (httpd-2.0.35 is the source of apache)
> 
> then I edit all the Makefiles for mod_perl, so the compiler use the 
> option "-DUSE_ITHREADS", then I did a make and make install,
> I got out a mod_perl.so file and put this under the Apache 
> $PREFIX/modules and edit my httpd.conf to correspond,
> when I start apache, I get the following error:
> 
> Cannot load /export/home/website/apache/modules/mod_perl.so into server: 
> ld.so.1: /export/home/website/apache/bin/httpd: fatal: relocation error: 
> file /export/home/website/apache/modules/mod_perl.so: symbol PL_thr_key: 
> referenced symbol not found
> 
> 
> Can anybody tell me, if I am configuring something wrong, or building it 
> the wrong way??
> I need to get a quick resolution to this problem, so any help is greatly 
> appreciated

Why did you have to manually edit the Makefiles? All the Perl flags are 
automatically used in the build process, so if you have build perl  with 
-Dusethreads, it's all you need to do.
Also why do you need to use MP_AP_PREFIX? Use MP_APXS= instead. You 
don't need Apache sources to build mod_perl as DSO.

Please refer to this document:
http://perl.apache.org/preview/modperl-docs/dst_html/docs/2.0/user/install/install.html

And when you report a problem, please do as explained here;
http://perl.apache.org/preview/modperl-docs/dst_html/docs/2.0/user/help/help.html#Reporting_Problems

__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com




Re: Compiling mod_perl 1.99 on Solaris 8

2002-04-18 Thread Darragh Sherwin

Hi,

Stas Bekman wrote:

> Darragh Sherwin wrote:
> 
>> Hi,
>> I am trying to compile mod_perl 1.99 with apacche 2.0.35, I give  
>> up with mod_perl 1.24 after numberous headaches and lots of profanties.
>>
>> It build configured Apache with following options :
>>

>>  ./configure --with-mpm=prefork --prefix=/export/home/website/apache 
>> --enable-so --with-port=80 --enable-info



I did this with the enviromental varible CFLAGS=-DUSE_ITHREADS


>>
>> I then did a make and make install for Apache
>> Then  I configured mod_perl with the following options:
>>
>>  perl Makefile.PL MP_AP_PREFIX=../httpd-2.0.35
>> (httpd-2.0.35 is the source of apache)


I used perl Makefile.PL MP_APXS=/export/home/website/apache/bin/apxs 
MP_CCOPTS=-DUSE_ITHREADS

The ITHREADS library is need on Solaris/Sparc to compile


>>
>> then I edit all the Makefiles for mod_perl, so the compiler use the 
>> option "-DUSE_ITHREADS", then I did a make and make install,
>> I got out a mod_perl.so file and put this under the Apache 
>> $PREFIX/modules and edit my httpd.conf to correspond,
>> when I start apache, I get the following error:
>>
>> Cannot load /export/home/website/apache/modules/mod_perl.so into 
>> server: ld.so.1: /export/home/website/apache/bin/httpd: fatal: 
>> relocation error: file 
>> /export/home/website/apache/modules/mod_perl.so: symbol PL_thr_key: 
>> referenced symbol not found


However, I am still getting the above error, should I just copy the 
mod_perl.so file from the mod_perl sources directory to the 
$APACHE/modules?? I am right in doing that??


>>
>>
>> Can anybody tell me, if I am configuring something wrong, or building 
>> it the wrong way??
>> I need to get a quick resolution to this problem, so any help is 
>> greatly appreciated
> 
> 
> Why did you have to manually edit the Makefiles? All the Perl flags are 
> automatically used in the build process, so if you have build perl  with 
> -Dusethreads, it's all you need to do.
> Also why do you need to use MP_AP_PREFIX? Use MP_APXS= instead. You 
> don't need Apache sources to build mod_perl as DSO.
> 
> Please refer to this document:
> 
>http://perl.apache.org/preview/modperl-docs/dst_html/docs/2.0/user/install/install.html
> 
> 


I read this, but it was of little help


> 
> And when you report a problem, please do as explained here;
> 
>http://perl.apache.org/preview/modperl-docs/dst_html/docs/2.0/user/help/help.html#Reporting_Problems
> 
> 
> 
> __
> Stas BekmanJAm_pH --> Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide ---> http://perl.apache.org
> mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com
> 


-- 
___
Darragh Sherwin
[EMAIL PROTECTED]

"To alcohol, the cause of, and solution to, all of life's problems"
Homer Simpson




Re: Compiling mod_perl 1.99 on Solaris 8

2002-04-18 Thread Stas Bekman

Darragh Sherwin wrote:
> Hi,
> 
> Stas Bekman wrote:
> 
>> Darragh Sherwin wrote:
>>
>>> Hi,
>>> I am trying to compile mod_perl 1.99 with apacche 2.0.35, I give  
>>> up with mod_perl 1.24 after numberous headaches and lots of profanties.
>>>
>>> It build configured Apache with following options :
>>>
> 
>>>  ./configure --with-mpm=prefork --prefix=/export/home/website/apache 
>>> --enable-so --with-port=80 --enable-info
>>
> 
> 
> 
> I did this with the enviromental varible CFLAGS=-DUSE_ITHREADS
> 
> 
>>>
>>> I then did a make and make install for Apache
>>> Then  I configured mod_perl with the following options:
>>>
>>>  perl Makefile.PL MP_AP_PREFIX=../httpd-2.0.35
>>> (httpd-2.0.35 is the source of apache)
>>
> 
> 
> I used perl Makefile.PL MP_APXS=/export/home/website/apache/bin/apxs 
> MP_CCOPTS=-DUSE_ITHREADS
> 
> The ITHREADS library is need on Solaris/Sparc to compile
> 
> 
>>>
>>> then I edit all the Makefiles for mod_perl, so the compiler use the 
>>> option "-DUSE_ITHREADS", then I did a make and make install,
>>> I got out a mod_perl.so file and put this under the Apache 
>>> $PREFIX/modules and edit my httpd.conf to correspond,
>>> when I start apache, I get the following error:
>>>
>>> Cannot load /export/home/website/apache/modules/mod_perl.so into 
>>> server: ld.so.1: /export/home/website/apache/bin/httpd: fatal: 
>>> relocation error: file 
>>> /export/home/website/apache/modules/mod_perl.so: symbol PL_thr_key: 
>>> referenced symbol not found
>>
> 
> 
> However, I am still getting the above error, should I just copy the 
> mod_perl.so file from the mod_perl sources directory to the 
> $APACHE/modules?? I am right in doing that??

what do you get from:

nm libperl.so | grep PL_thr_key

Do you have this symbol? You don't say how you have built perl.


>>>
>>>
>>> Can anybody tell me, if I am configuring something wrong, or building 
>>> it the wrong way??
>>> I need to get a quick resolution to this problem, so any help is 
>>> greatly appreciated
>>
>>
>>
>> Why did you have to manually edit the Makefiles? All the Perl flags 
>> are automatically used in the build process, so if you have build 
>> perl  with -Dusethreads, it's all you need to do.
>> Also why do you need to use MP_AP_PREFIX? Use MP_APXS= instead. You 
>> don't need Apache sources to build mod_perl as DSO.
>>
>> Please refer to this document:
>> 
>http://perl.apache.org/preview/modperl-docs/dst_html/docs/2.0/user/install/install.html
> 
>>
> 
> 
> 
> I read this, but it was of little help
> 
> 
>>
>> And when you report a problem, please do as explained here;
>> 
>http://perl.apache.org/preview/modperl-docs/dst_html/docs/2.0/user/help/help.html#Reporting_Problems
> 

But your report was incomplete. why wasting time and doing error-prone 
copy and
paste of things when there is a script to do it right for you and help 
us all?


__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com




Re: Compiling mod_perl 1.99 on Solaris 8

2002-04-18 Thread Doug MacEachern

On Thu, 18 Apr 2002, Darragh Sherwin wrote:
 
> I did this with the enviromental varible CFLAGS=-DUSE_ITHREADS
...
> MP_CCOPTS=-DUSE_ITHREADS

you can't do that.  and that is the source of your problems.
if you are going to use a threaded mpm, *perl* needs to be built with 
ithreads enabled.  perl's generated config.h will then have #define 
USE_ITHREADS which modperl will get compiled with.






Re: Compiling mod_perl 1.99 on Solaris 8

2002-04-18 Thread Doug MacEachern

On Thu, 18 Apr 2002, Stas Bekman wrote:

> Also why do you need to use MP_AP_PREFIX? Use MP_APXS= instead. You 
> don't need Apache sources to build mod_perl as DSO.

MP_AP_PREFIX is not the source tree, it is the install tree.  all modperl 
needs is the include/ directory from the install tree, it does not need 
apxs.  MP_AP_PREFIX works everywhere.  MP_APXS does not work on windows.





error compiling mod_perl-1.99_05 with Apache 2.0.42

2002-09-26 Thread Yue Luo

  Hi, I have installed Apache 2.0.42.  When I run the configuration
script:
perl Makefile.PL MP_AP_PREFIX=$HOME/httpd/prefork  MP_INST_APACHE2=1
  I got error:
Unable to determine server version.

I believe the bug is in /mod_perl-1.99_05/lib/Apache/Build.pm Line 746:
next unless /^\#define\s+AP_SERVER_BASEREVISION\s+\"(.*)\"/;

It expect a line of integers in double quote.  While in this version of
Apache include/ap_release.h, the #define line is:
#define AP_SERVER_BASEREVISION  AP_SERVER_MINORREVISION "." 
AP_SERVER_PATCHLEVEL

Therefore, it won't be able to find the correct version of the server.

Yue
   

__
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com



Re: Trouble Compiling Mod_Perl 1.27 on SGI

2002-10-15 Thread Ged Haywood

Hi there,

On Mon, 14 Oct 2002, Kent, Mr. John wrote:

> Having trouble building mod_perl-1.27 against Apache_1.3.27 on an SGI

Have you looked at the file mod_perl-1.27/SUPPORT ?
Did you build the Perl installation on these machines?
Could you use a different compiler?

73,
Ged.






Re: make error compiling mod_perl on RH7.1

2002-11-10 Thread Stas Bekman
Witchy wrote:

Hi all,

Trying to compile mod_perl 2.0 for my RH7.1/Apache 2.0.39 server and it
falls over with this error:

apr_perlio.c: In function `apr_perlio_apr_file_to_glob':
apr_perlio.c:573: `IoTYPE_WRONLY' undeclared (first use in this function)
apr_perlio.c:573: (Each undeclared identifier is reported only once
apr_perlio.c:573: for each function it appears in.)
apr_perlio.c:577: `IoTYPE_RDONLY' undeclared (first use in this function)
make[3]: *** [apr_perlio.o] Error 1
make[3]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR/PerlIO'
make[2]: *** [subdirs] Error 2
make[2]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR'
make[1]: *** [subdirs] Error 2
make[1]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs'
make: *** [subdirs] Error 2

When I ran 'perl Makefile.PL' etc with the correct location for my apache
setup the only thing it complained about was the fact I was using Perl 5.6.0
and it recommended 5.6.1 or above. Before I trawl the dependencies tree
trying to install a later version has anyone seen that problem before and do
I really need to upgrade my perl installation?


As somebody else has pointed out you won't have a problem if you run 
Perl 5.6.1 or higher. Let me check with other developers if 2.0 will 
eventually require 5.6.1 which is much better thatn 5.6.0. Or whether we 
should backport things to 5.6.0 as well. The reason is that macros 
IoTYPE_WRONLY and IoTYPE_RDONLY were introduced in 5.6.1.


__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@;stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com



RE: make error compiling mod_perl on RH7.1

2002-11-11 Thread Witchy
Thanks for that, Stas. I'll see if I can get my hands on 5.6.1 since the
current release has too many dependencies to resolve with RH7.1 without the
possibility of something getting Broken :)

cheers!

--
adrian/witchy
www.binarydinosaurs.co.uk - the online computer museum
www.snakebiteandblack.co.uk - monthly gothic shenanigans


> -Original Message-
> From: Stas Bekman [mailto:stas@;stason.org]
> Sent: 11 November 2002 04:36
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: make error compiling mod_perl on RH7.1
>
>
> Witchy wrote:
> > Hi all,
> >
> > Trying to compile mod_perl 2.0 for my RH7.1/Apache 2.0.39 server and it
> > falls over with this error:
> >
> > apr_perlio.c: In function `apr_perlio_apr_file_to_glob':
> > apr_perlio.c:573: `IoTYPE_WRONLY' undeclared (first use in this
> function)
> > apr_perlio.c:573: (Each undeclared identifier is reported only once
> > apr_perlio.c:573: for each function it appears in.)
> > apr_perlio.c:577: `IoTYPE_RDONLY' undeclared (first use in this
> function)
> > make[3]: *** [apr_perlio.o] Error 1
> > make[3]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR/PerlIO'
> > make[2]: *** [subdirs] Error 2
> > make[2]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR'
> > make[1]: *** [subdirs] Error 2
> > make[1]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs'
> > make: *** [subdirs] Error 2
> >
> > When I ran 'perl Makefile.PL' etc with the correct location for
> my apache
> > setup the only thing it complained about was the fact I was
> using Perl 5.6.0
> > and it recommended 5.6.1 or above. Before I trawl the dependencies tree
> > trying to install a later version has anyone seen that problem
> before and do
> > I really need to upgrade my perl installation?
>
> As somebody else has pointed out you won't have a problem if you run
> Perl 5.6.1 or higher. Let me check with other developers if 2.0 will
> eventually require 5.6.1 which is much better thatn 5.6.0. Or whether we
> should backport things to 5.6.0 as well. The reason is that macros
> IoTYPE_WRONLY and IoTYPE_RDONLY were introduced in 5.6.1.
>
>
> __
> Stas BekmanJAm_pH --> Just Another mod_perl Hacker
> http://stason.org/ mod_perl Guide ---> http://perl.apache.org
> mailto:stas@;stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org   http://ticketmaster.com
>




RE: make error compiling mod_perl on RH7.1

2002-11-11 Thread Witchy


> -Original Message-
> From: Stas Bekman [mailto:stas@;stason.org]
> Sent: 11 November 2002 10:24
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: make error compiling mod_perl on RH7.1
>
> I think moving to 5.6.1 from 5.6.0 should be very easy. I'm sure RH has
> RPMs with 5.6.1.

I'll check.

> When you say current release, do you mean 5.8.0? I still have almost 4K
> emails to catch up with at p5p, but I'm being told by those who work
> instead of traveling, that 5.8.0 has some problems :(

The version I've got here is 5.8.0-55 so I'll stick with trying the one
point release first :)

cheers

w




Re: make error compiling mod_perl on RH7.1

2002-11-25 Thread Stas Bekman
Witchy wrote:

Thanks for that, Stas. I'll see if I can get my hands on 5.6.1 since the
current release has too many dependencies to resolve with RH7.1 without the
possibility of something getting Broken :)


Doug says that we want 2.0 to compile under perl 5.6.0, even though you 
won't get all the features (e.g. perlio, on which other features depend) 
and you should remember that perl version is very buggy.

In any case, if you try the current cvs you should be able to compile 
2.0 with 5.6.0 again.

-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]]
Sent: 11 November 2002 04:36
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: make error compiling mod_perl on RH7.1


Witchy wrote:


Hi all,

Trying to compile mod_perl 2.0 for my RH7.1/Apache 2.0.39 server and it
falls over with this error:

apr_perlio.c: In function `apr_perlio_apr_file_to_glob':
apr_perlio.c:573: `IoTYPE_WRONLY' undeclared (first use in this


function)


apr_perlio.c:573: (Each undeclared identifier is reported only once
apr_perlio.c:573: for each function it appears in.)
apr_perlio.c:577: `IoTYPE_RDONLY' undeclared (first use in this


function)


make[3]: *** [apr_perlio.o] Error 1
make[3]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR/PerlIO'
make[2]: *** [subdirs] Error 2
make[2]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs/APR'
make[1]: *** [subdirs] Error 2
make[1]: Leaving directory `/home/adrian/mod_perl-1.99_07/xs'
make: *** [subdirs] Error 2

When I ran 'perl Makefile.PL' etc with the correct location for


my apache


setup the only thing it complained about was the fact I was


using Perl 5.6.0


and it recommended 5.6.1 or above. Before I trawl the dependencies tree
trying to install a later version has anyone seen that problem


before and do


I really need to upgrade my perl installation?


As somebody else has pointed out you won't have a problem if you run
Perl 5.6.1 or higher. Let me check with other developers if 2.0 will
eventually require 5.6.1 which is much better thatn 5.6.0. Or whether we
should backport things to 5.6.0 as well. The reason is that macros
IoTYPE_WRONLY and IoTYPE_RDONLY were introduced in 5.6.1.


__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com






--


__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com




Problems compiling mod_perl 1.99_07 in RH 8.0

2002-11-26 Thread J. J. Merelo
Hi,
This new RH 8.0 installation is resulting in a calvary. After finding
that mod_cgi does not work, that the mod_perl that comes with it breaks
all scripts I've got, I have decided to build the latest apache version
and mod_perl from scratch. But looks like I am also bumping into
problems here: when compiling it, I get this error

LD_RUN_PATH="/usr/lib" gcc  -shared -L/usr/local/lib APR.o  -o
../../../blib/arch/auto/APR/APR.so   -L/usr/local/apache2/lib -lapr
-laprutil
/usr/bin/ld: cannot find -lapr

Looks like that corresponds to libapreq ; but I'm not too sure where to
get it. Is it included in the Apache release? Is it in apache-devel? I
have found a RPM for it, but now I'm not sure that's reliable either. 
¿Any idea?

JJ
-- 
J. J. Merelo <[EMAIL PROTECTED]>
GeNeura




Re: Problem compiling mod_perl 1.27 on Windows

2002-12-16 Thread Randy Kobes
On Mon, 16 Dec 2002, Steve Hay wrote:

> Hi,
> 
> I'm having trouble compiling mod_perl 1.27 (with Apache 1.3.27 / Perl 
> 5.8.0) on Windows (XP SP1 with MS VC++ 6.0 SP5).
> 
> It builds fine with Perl 5.8.0 standard sources, but I'm just trying to 
> upgrade my Perl to the slightly patched sources that ActivePerl Build 
> 804 uses.  I've built Perl from these new sources with the same build 
> options that I used before for the standard source build (no threading, 
> and Perl's malloc).  (The output of "Perl -V" is at the bottom of this 
> mail.)
> 
> I run the following commands to build mod_perl:
> 
> perl Makefile.PL APACHE_SRC=C:/apache
>   INSTALL_DLL=C:/apache/modules EAPI
> nmake
> 
> The first command runs fine, but the second has the following error:
> 
> Apache.xs(1963) : error C2115: '=' : incompatible types
> 
> The line referred to by this error is:
> 
> statcache = r->finfo;
> 
> I've no idea why this should be causing a problem with the new
> Perl.  If I switch the Perl that I'm building against back to
> the standard 5.8.0 (by simply re-naming directories) and then
> re-run the "nmake" command above then mod_perl compiles and
> links with no errors.
> 
> Can anyone shed any light on this?
> 
> - Steve
[ .. ] 
> Characteristics of this binary (from libperl):
>   Compile-time options: USE_LARGE_FILES

I've found the same thing - I believe it's because of the
USE_LARGE_FILES support that ActivePerl 8xx has enabled, and this
runs into a conflict with the standard Win32 apache-1 which
doesn't have such support (in the above, statcache is from the
Perl side, and r->finfo is from Apache). This is still being
looked into ...

One possibility is to recompile Apache with large_file support,
but this is non-trivial. And since the bulk of Win32 development
on Apache is going into Apache-2, it may be hard to get an Apache
developer to look at this.

By the way, mod_perl-2 (for use with Apache2) compiles fine with
the ActivePerl sources.

-- 
best regards,
randy kobes




Re: Problem compiling mod_perl 1.27 on Windows

2002-12-16 Thread Steve Hay
Randy Kobes wrote:


On Mon, 16 Dec 2002, Steve Hay wrote:
 

I'm having trouble compiling mod_perl 1.27 (with Apache 1.3.27 / Perl 
5.8.0) on Windows (XP SP1 with MS VC++ 6.0 SP5).

It builds fine with Perl 5.8.0 standard sources, but I'm just trying to 
upgrade my Perl to the slightly patched sources that ActivePerl Build 
804 uses.  I've built Perl from these new sources with the same build 
options that I used before for the standard source build (no threading, 
and Perl's malloc).  (The output of "Perl -V" is at the bottom of this 
mail.)
   

[ .. ] 
 

Characteristics of this binary (from libperl):
 Compile-time options: USE_LARGE_FILES
   


I've found the same thing - I believe it's because of the
USE_LARGE_FILES support that ActivePerl 8xx has enabled, and this
runs into a conflict with the standard Win32 apache-1 which
doesn't have such support (in the above, statcache is from the
Perl side, and r->finfo is from Apache). This is still being
looked into ...

One possibility is to recompile Apache with large_file support,
but this is non-trivial. And since the bulk of Win32 development
on Apache is going into Apache-2, it may be hard to get an Apache
developer to look at this.


Looking at mod_perl (1.27)'s Makefile.PL I see that there is a 
uselargefiles_check() routine that originally warned about conflicts, 
but now (as of 1.27, according to the Changes file) automatically sets 
PERL_USELARGEFILES=0 to try to avert disaster.  But the only difference 
that this seems to make is to stop Perl's $Config{ccflags} from being 
appended to PERL_EXTRA_CFLAGS.  However, my Perl (804)'s 
$Config{ccflags} doesn't mention anything to do with large_files, so 
it's hardly surprising that disaster is not averted (if this is indeed 
the problem).

Is there some other way, for Win32, to achieve what the 
PERL_USELARGEFILES=0 hack tried to do?

I also see that the warning that was originally output by 
uselargefiles_check() suggested re-building Apache with large_files 
support by simply specifying a couple of extra defines.  I take it from 
what you're saying that it isn't quite as trivial as that on Win32?

By the way, mod_perl-2 (for use with Apache2) compiles fine with
the ActivePerl sources.
 

I've been reluctant to use mod_perl 2 for anything more than testing 
purposes yet because its current version number (1.99_07) doesn't fill 
me with confidence that it's sufficiently stable.  The mod_perl setup 
that I'm trying to build is destined for a production environment, so 
I'd rather stick to more tried and tested things for now.

I would be interested to hear how stable people think mod_perl 2 
currently is on Win32.

- Steve



Re: Problem compiling mod_perl 1.27 on Windows

2002-12-16 Thread Randy Kobes
On Mon, 16 Dec 2002, Steve Hay wrote:

> Randy Kobes wrote:
> >
> >I've found the same thing - I believe it's because of the
> >USE_LARGE_FILES support that ActivePerl 8xx has enabled, and this
> >runs into a conflict with the standard Win32 apache-1 which
> >doesn't have such support (in the above, statcache is from the
> >Perl side, and r->finfo is from Apache). This is still being
> >looked into ...
> >
> >One possibility is to recompile Apache with large_file support,
> >but this is non-trivial. And since the bulk of Win32 development
> >on Apache is going into Apache-2, it may be hard to get an Apache
> >developer to look at this.
> >
> Looking at mod_perl (1.27)'s Makefile.PL I see that there is a 
> uselargefiles_check() routine that originally warned about conflicts, 
> but now (as of 1.27, according to the Changes file) automatically sets 
> PERL_USELARGEFILES=0 to try to avert disaster.  But the only difference 
> that this seems to make is to stop Perl's $Config{ccflags} from being 
> appended to PERL_EXTRA_CFLAGS.  However, my Perl (804)'s 
> $Config{ccflags} doesn't mention anything to do with large_files, so 
> it's hardly surprising that disaster is not averted (if this is indeed 
> the problem).

That's true - Perl's ccflags don't mention USE_LARGE_FILES; it
only gets mentioned in the compile-time options. 
 
> Is there some other way, for Win32, to achieve what the 
> PERL_USELARGEFILES=0 hack tried to do?

This seems hard to do without recompiling either the standard
Apache sources (to enable large_files support) or else the
standard ActivePerl 8xx sources (to disable large_files support).
One possibility is to define one's own statcache (presently
defined in the header files under /Perl/lib/CORE/) as is defined
in a Win32 Perl without large_files support. That may get around
the problem in Apache.xs about incompatible types between
statcache and r->finfo, but this might lead to other problems
later.
  
> I also see that the warning that was originally output by
> uselargefiles_check() suggested re-building Apache with
> large_files support by simply specifying a couple of extra
> defines.  I take it from what you're saying that it isn't quite
> as trivial as that on Win32?

I tried just adding a couple of extra defines in compiling apache
- this starts a series of error messages in various C files about
incompatibilities, which then leads to having to put in a bunch
of #ifdef ...  statemements. Ultimately this probably could be
worked out, but I'd be very uncomfortable using such a hacked
version without some official Apache support.
 
> >By the way, mod_perl-2 (for use with Apache2) compiles fine with
> >the ActivePerl sources.
> >  
> >
> I've been reluctant to use mod_perl 2 for anything more than testing 
> purposes yet because its current version number (1.99_07) doesn't fill 
> me with confidence that it's sufficiently stable.  The mod_perl setup 
> that I'm trying to build is destined for a production environment, so 
> I'd rather stick to more tried and tested things for now.
> 
> I would be interested to hear how stable people think mod_perl 2 
> currently is on Win32.

That would be interesting 

-- 
best regards,
randy 




Re: Problem compiling mod_perl 1.27 on Windows

2002-12-17 Thread Steve Hay
Randy Kobes wrote:


On Mon, 16 Dec 2002, Steve Hay wrote:
 

Is there some other way, for Win32, to achieve what the 
PERL_USELARGEFILES=0 hack tried to do?
   

This seems hard to do without recompiling either the standard
Apache sources (to enable large_files support) or else the
standard ActivePerl 8xx sources (to disable large_files support).


Sounds like recompiling Perl from the ActivePerl 804 sources with 
large_files support disabled is my best bet.

Am I correct in thinking that all I need to do to achieve this is change 
"uselargefiles='define'" back to "uselargefiles='undef'" in 
win32/config.vc, or is there anything else that I need to fiddle with too?

- Steve



Re: Problem compiling mod_perl 1.27 on Windows

2002-12-17 Thread Randy Kobes
On Tue, 17 Dec 2002, Steve Hay wrote:

> Randy Kobes wrote:
> 
> >On Mon, 16 Dec 2002, Steve Hay wrote:
> >
> >>Is there some other way, for Win32, to achieve what the 
> >>PERL_USELARGEFILES=0 hack tried to do?
> >>
> >This seems hard to do without recompiling either the standard
> >Apache sources (to enable large_files support) or else the
> >standard ActivePerl 8xx sources (to disable large_files support).
> >
> Sounds like recompiling Perl from the ActivePerl 804 sources with 
> large_files support disabled is my best bet.

That would most probably fix the problem with mod_perl. Doing
this may lead to an incompatibility in principle with trying to
use a particular ppm package (having an xs component) provided by
ActiveState, but since you have a compiler, that's not a problem
for you.
 
> Am I correct in thinking that all I need to do to achieve this
> is change "uselargefiles='define'" back to
> "uselargefiles='undef'" in win32/config.vc, or is there
> anything else that I need to fiddle with too?

I'm not sure  Probably the safest thing to do is to compare
the relevant files (Makefile, config*, *.h) under the win32/
subdirectory of the ActivePerl sources with those in the CPAN
Perl sources.
 
-- 
best regards,
randy




Re: Compiling mod_perl as a static module....

2003-06-08 Thread Ged Haywood
Subject: Returned mail: see transcript for details

The original message was received at Sun, 8 Jun 2003 23:22:26 +0100
from IDENT:[EMAIL PROTECTED] [212.22.195.7]

   - The following addresses had permanent fatal errors -
<[EMAIL PROTECTED]>
(reason: 553 5.3.0 Zone rejected due to abuse.)

   - Transcript of session follows -
... while talking to forrie.com.:
>>> MAIL From:<[EMAIL PROTECTED]>
<<< 553 5.3.0 Zone rejected due to abuse.
==
Hi there,

As you can see mail from me doesn't reach you directly.
What's this abuse?

On Sun, 8 Jun 2003, Forrest Aldrich wrote:

> I'm finally getting down to trying this out, per your directions.

As I recall I have already asked you to keep your messages on the List.

Please read

http://perl.apache.org/maillist/email-etiquette.html

73,
Ged.






Compiling mod_perl with different versions of Perl

1999-12-01 Thread Clinton Gormley

I have a working version of Perl and mod_perl on a live system at the
moment.  Since installation, I have installed pgcc.

I want to recompile Apache and mod_perl to use a proxy front end, and
would like to do this using pgcc and its optimisations.

Stas says in his guide that Perl and mod_perl should be compiled with
the same compiler, so it seems that I should recompile Perl with pgcc at
the same time. I would prefer to compile Perl into a separate place to
my current Perl.  

My question is, when I compile mod_perl, how do I specify which version
of Perl it should refer to?  

Does it matter at compile time, or is it sufficient that the default
Perl binary is the correct one at run time?  Does the binary you use to
run Makefile.pl have any influence?

Any help greatly appreciated

Thanks

Clinton Gormley



Re: Compiling mod_perl as a DSO? (fwd)

2000-01-30 Thread Michael Robinton

On Sun, 30 Jan 2000, Bill Bradford wrote:

> Is it possible to compile/install mod_perl as a DSO, on an existing
> pre-compiled copy of apache (with mod_so enabled), yet?  If so, 
> how?  I couldnt find it in the docs... and I'm tired of having to
> statically compile the module in... so any help would be appreciated.
> 
I read on the list at one time that the DSO verson has a memory leak. 
Don't know if this is still true or not. The static version apparently 
did not have that problem. If someone knows the answer to this I'd like 
to know myself as the DSO version is considerably easier to put together 
with other modules.

Michael



Re: Compiling mod_perl as a DSO? (fwd)

2000-01-30 Thread Bill Bradford

On Sun, Jan 30, 2000 at 10:37:24PM -0800, Michael Robinton wrote:
> I read on the list at one time that the DSO verson has a memory leak. 
> Don't know if this is still true or not. The static version apparently 
> did not have that problem. If someone knows the answer to this I'd like 
> to know myself as the DSO version is considerably easier to put together 
> with other modules.

Exactly - right now, there's no easy way to compile a static 
apache + mod_perl + php3.  Heck, I cant even get apache + mod_perl
to work (I need to do --enable-module=so during apache configuration,
but the modperl setup/build re-configures apache and leaves it out).

I'd be happy with being able to do apache + static mod_perl + DSO'ed
PHP3, if anybody can point out how to do apache + static mod_perl +
"--enable-module=so".

Thanks.

Bill

-- 
+---+--+--+
|Bill Bradford  | [EMAIL PROTECTED] | [EMAIL PROTECTED]|
|http://www.sunhelp.org | http://www.pdp11.org | http://www.mrbill.net|
+---+--+--+



Problem compiling mod_perl 1.23 on Solaris 2.4

2000-04-26 Thread Steve Hay

Hi,

I'm having a problem compiling mod_perl 1.23 (with Apache 1.3.12 / Perl
5.6.0) as a DSO using APXS on Solaris 2.4.  This worked fine using
Apache 1.3.6 / Perl 5.005_03 / mod_perl 1.22.

Can anybody help?

I built the Perl with "-Uusemymalloc" which I had found was necessary
under the previous setup.

Here's the output:-

radsun2-4% perl Makefile.PL USE_APXS=1
WITH_APXS=/usr/local/apache/bin/apxs EVERYTHING=1
Will configure via APXS (apxs=/usr/local/apache/bin/apxs)
PerlDispatchHandler.enabled
PerlChildInitHandlerenabled
PerlChildExitHandlerenabled
PerlPostReadRequestHandler..enabled
PerlTransHandlerenabled
PerlHeaderParserHandler.enabled
PerlAccessHandler...enabled
PerlAuthenHandler...enabled
PerlAuthzHandlerenabled
PerlTypeHandler.enabled
PerlFixupHandlerenabled
PerlHandler.enabled
PerlLogHandler..enabled
PerlInitHandler.enabled
PerlCleanupHandler..enabled
PerlRestartHandler..enabled
PerlStackedHandlers.enabled
PerlMethodHandlers..enabled
PerlDirectiveHandlers...enabled
PerlTableApienabled
PerlLogApi..enabled
PerlUriApi..enabled
PerlUtilApi.enabled
PerlFileApi.enabled
PerlConnectionApi...enabled
PerlServerApi...enabled
PerlSectionsenabled
PerlSSI.enabled
Will run tests as User: 'radan' Group: 'usr'
Configuring mod_perl for building via APXS
 + Creating a local mod_perl source tree
 + Setting up mod_perl build environment (Makefile)
 + id: mod_perl/1.23
 + id: Perl/v5.6.0 (solaris) [perl]
Now please type 'make' to build libperl.so
Checking CGI.pm VERSION..ok
Checking for LWP::UserAgent..ok
Checking for HTML::HeadParserok
Checking if your kit is complete...
Looks good
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
radsun2-4% make
(cd ./apaci && make)
cc -KPIC -O  -I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE
-DMOD_PERL_VERSION=\"1.23\" -DMOD_PERL_STRING_VERSION=\"mod_perl/1.23\"
-I/usr/local/apache/include -DMOD_PERL -DSOLARIS2=240 -DUSE_HSREGEX
-DUSE_EXPAT -I../lib/expat-lite -c mod_perl.c && mv mod_perl.o
mod_perl.lo
"/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE/perl.h", line 1929:
warning: operand treated as unsigned: 0x87654321
"./mod_perl.h", line 584: warning: macro replacement within a string
literal
"./mod_perl.h", line 587: warning: macro replacement within a string
literal
"./mod_perl.h", line 590: warning: macro replacement within a string
literal
"./mod_perl.h", line 593: warning: macro replacement within a string
literal
"mod_perl.c", line 344: fatal: macro recursion
cc: acomp failed for mod_perl.c
*** Error code 2
make: Fatal error: Command failed for target `mod_perl.lo'
Current working directory /tmp/mod_perl-1.23/apaci
*** Error code 1
make: Fatal error: Command failed for target `apxs_libperl'
radsun2-4%





Problem compiling mod_perl 1.24 on Solaris 2.6

2000-05-23 Thread Fred Miller

On 4/26/2000, Steve Hay wrote about "Problem compiling mod_perl 1.23 on
Solaris 2.4"

I am experiencing what appears to be a very similar problem, but with
more recent modules and OS. I am running mod_perl 1.24, Perl 5.6.0,
Apache 1.3.12, Solaris 2.6

Perl Makefile.PL with options runs successfully.

When I run make, I get output nearly identical to that reported by Steve
Hay. Here are the last few lines output from my make:

 "/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE/perl.h", line 1929:
warning: operand treated as unsigned: 0x87654321
"./mod_perl.h", line 584: warning: macro replacement within a string
literal
"./mod_perl.h", line 587: warning: macro replacement within a string
literal
"./mod_perl.h", line 590: warning: macro replacement within a string
literal
"./mod_perl.h", line 593: warning: macro replacement within a string
literal
"mod_perl.c", line 347: fatal: macro recursion
cc: acomp failed for mod_perl.c
make[5]: *** [mod_perl.o] Error 2
make[4]: *** [all] Error 1
make[3]: *** [subdirs] Error 1
make[3]: Leaving directory `/export/home/fmiller/apache_1.3.12/src'
make[2]: *** [build-std] Error 2
make[2]: Leaving directory `/export/home/fmiller/apache_1.3.12'
make[1]: *** [build] Error 2
make[1]: Leaving directory `/export/home/fmiller/apache_1.3.12'
make: *** [apaci_httpd] Error 2


I have previously successfully installed Apache 1.3.12 on this system
without mod_perl.

Steve Hay reported that he solved his problem by re=compiling
"everything with the -Xa compiler flag".

I confess to being a bit naive when it comes to compiling and
installing.

Are there some simple steps I should follow to proceed?


Thanks for all the support.

Fred Miller
-- 
[EMAIL PROTECTED]
http://titan.iwu.edu/~fmiller/



Re: Pb compiling mod_perl (1.21 to 1.24.01)

2000-11-14 Thread Stas Bekman

On Tue, 14 Nov 2000, Laurent Perez wrote:

> Hi list
> 
> I can't get mod_perl to compile with my apache_source.
> I always get ' /usr/bin/ld : cannot find -lgdbm : No such file or 
> directory ' with 'make'.
> I'm running a Debian 2.2 box, i added /usr/lib to ld.so.conf, and 
> libgdbmg1 is installed.

http://thingy.kcilink.com/modperlguide/install/Missing_or_Misconfigured_libgdbm.html

> 
> Thanks for your answer
> 
> Laurent
> 
> 
> 



_
Stas Bekman  JAm_pH --   Just Another mod_perl Hacker
http://stason.org/   mod_perl Guide  http://perl.apache.org/guide 
mailto:[EMAIL PROTECTED]   http://apachetoday.com http://jazzvalley.com
http://singlesheaven.com http://perlmonth.com   perl.org   apache.org





Re: Problems compiling mod_perl 1.99_07 in RH 8.0

2002-11-26 Thread Stas Bekman
J. J. Merelo wrote:

Hi,
	This new RH 8.0 installation is resulting in a calvary. After finding
that mod_cgi does not work, that the mod_perl that comes with it breaks
all scripts I've got, I have decided to build the latest apache version
and mod_perl from scratch. But looks like I am also bumping into
problems here: when compiling it, I get this error

LD_RUN_PATH="/usr/lib" gcc  -shared -L/usr/local/lib APR.o  -o
../../../blib/arch/auto/APR/APR.so   -L/usr/local/apache2/lib -lapr
-laprutil
/usr/bin/ld: cannot find -lapr

Looks like that corresponds to libapreq ; but I'm not too sure where to
get it. Is it included in the Apache release? Is it in apache-devel? I
have found a RPM for it, but now I'm not sure that's reliable either. 
¿Any idea?

you have to install httpd-2.0, before you build mod_perl 2.0, and it 
installs apr and apr-util libs. see the online docs.



__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com



Re: Problems compiling mod_perl 1.99_07 in RH 8.0

2002-11-26 Thread Stas Bekman
[please, post followups to the list! everybody else on the list wants to 
know the answer, not only you. thanks!]

J. J. Merelo wrote:
Hi,



Looks like that corresponds to libapreq ; but I'm not too sure where to
get it. Is it included in the Apache release? Is it in apache-devel? I
have found a RPM for it, but now I'm not sure that's reliable either. 
¿Any idea?

you have to install httpd-2.0, before you build mod_perl 2.0, and it 
installs apr and apr-util libs. see the online docs.


Sorry I didn't mention it, but I built apache 2.0.43 under the same
upper dir, and installed it under /usr/local/apache2. The command line
for building was:
perl Makefile.PL MP_AP_PREFIX=/usr/local/apache2

It does have the apr and apr-util libs, in the correct directory I
guess. 
ls /usr/local/apache2/lib/
apr.exp  libapr-0.lalibapr-0.so.0.9.2  libaprutil-0.so
aprutil.exp  libapr-0.solibaprutil-0.a libaprutil-0.so.0
libapr-0.a   libapr-0.so.0  libaprutil-0.lalibaprutil-0.so.0.9.2

Do I have to define another config variable or something?

Oops, they did it again. Around mid-Sept the apr project has changed the 
way they name libs. None of us have had problems because we still had 
the old libs with the old conventions linked instead of the new ones.

what used to be libapr.so.0.9.2, now is named libapr-0.so.0.0.2 (same 
for aprutil), similar to libdb's naming convention.

So here is the patch that will get you going if you use the current cvs. 
Though it won't work with older aprs. Should probably hide the 
differences in the ModPerl::MM build.

Index: xs/APR/APR/Makefile.PL
===
RCS file: /home/cvs/modperl-2.0/xs/APR/APR/Makefile.PL,v
retrieving revision 1.4
diff -u -r1.4 Makefile.PL
--- xs/APR/APR/Makefile.PL  6 Apr 2002 04:42:00 -   1.4
+++ xs/APR/APR/Makefile.PL  26 Nov 2002 13:56:11 -
@@ -4,12 +4,11 @@

 my $prefix = ModPerl::MM::build_config()->apxs(-q => 'PREFIX');

-my $libdir = "$prefix/lib";
-
-my @libs = map "-l$_", qw(apr aprutil);
+my @libs = map { qx{$prefix/bin/$_-config --link-ld} } qw(apr apu);
+chomp @libs;

 ModPerl::MM::WriteMakefile(
 'NAME'=> 'APR',
 'VERSION_FROM' => 'APR.pm',
-'LIBS' => ["-L$libdir @libs"],
+'LIBS' => \@libs,
 );


__
Stas BekmanJAm_pH --> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com



Re: Problems compiling mod_perl 1.99_07 in RH 8.0

2002-11-26 Thread J. J. Merelo
Hi,

> > Looks like that corresponds to libapreq ; but I'm not too sure where to
> > get it. Is it included in the Apache release? Is it in apache-devel? I
> > have found a RPM for it, but now I'm not sure that's reliable either. 
> > ¿Any idea?
> 
> you have to install httpd-2.0, before you build mod_perl 2.0, and it 
> installs apr and apr-util libs. see the online docs.

Sorry I didn't mention it, but I built apache 2.0.43 under the same
upper dir, and installed it under /usr/local/apache2. The command line
for building was:
perl Makefile.PL MP_AP_PREFIX=/usr/local/apache2

It does have the apr and apr-util libs, in the correct directory I
guess. 
ls /usr/local/apache2/lib/
apr.exp  libapr-0.lalibapr-0.so.0.9.2  libaprutil-0.so
aprutil.exp  libapr-0.solibaprutil-0.a libaprutil-0.so.0
libapr-0.a   libapr-0.so.0  libaprutil-0.lalibaprutil-0.so.0.9.2

Do I have to define another config variable or something?

JJ
-- 
J. J. Merelo <[EMAIL PROTECTED]>
GeNeura




Re: Compiling mod_perl with different versions of Perl

1999-12-01 Thread Stas Bekman

> I have a working version of Perl and mod_perl on a live system at the
> moment.  Since installation, I have installed pgcc.
> 
> I want to recompile Apache and mod_perl to use a proxy front end, and
> would like to do this using pgcc and its optimisations.
> 
> Stas says in his guide that Perl and mod_perl should be compiled with
> the same compiler, so it seems that I should recompile Perl with pgcc at
> the same time. I would prefer to compile Perl into a separate place to
> my current Perl.  
> 
> My question is, when I compile mod_perl, how do I specify which version
> of Perl it should refer to?  

Assuming that you have:

/usr/bin/perl5.00503
/usr/bin/perl5.6052

if you do:

perl5.00503 Makefile.PL ... it would use the perl5.00503 for mod_perl, if
you do:

perl5.6052 Makefile.PL ... - it would use the perl5.6052

Hope that this answers your question...

___
Stas Bekman  mailto:[EMAIL PROTECTED]www.singlesheaven.com/stas  
Perl,CGI,Apache,Linux,Web,Java,PC at  www.singlesheaven.com/stas/TULARC
www.apache.org  & www.perl.com  == www.modperl.com  ||  perl.apache.org
single o-> + single o-+ = singlesheavenhttp://www.singlesheaven.com



Re: Problem compiling mod_perl 1.23 on Solaris 2.4

2000-04-27 Thread Steve Hay

Steve Hay wrote:

> I'm having a problem compiling mod_perl 1.23 (with Apache 1.3.12 / Perl
> 5.6.0) as a DSO using APXS on Solaris 2.4.

In case anyone is interested...

I've solved my own problem (just as well, really).  If I re-compile
everything with the -Xa compiler flag then it all works out fine.





RE: Problem compiling mod_perl 1.23 on Solaris 2.4

2000-04-27 Thread FEITO Nazareno

Good For you buddie:)
We know that you can do that... ;)

bybye

Nazareno
Perl Programmer www.obsequie.com



Re: Problem compiling mod_perl 1.23 on Solaris 2.4

2000-05-05 Thread Doug MacEachern

On Thu, 27 Apr 2000, Steve Hay wrote:

> Steve Hay wrote:
> 
> > I'm having a problem compiling mod_perl 1.23 (with Apache 1.3.12 / Perl
> > 5.6.0) as a DSO using APXS on Solaris 2.4.
> 
> In case anyone is interested...
> 
> I've solved my own problem (just as well, really).  If I re-compile
> everything with the -Xa compiler flag then it all works out fine.

what does -Xa mean?  gcc or ld flag?  i don't see anything in the gcc
manpage, 2.6 ld manpage says:

  Options No Longer Supported
 The following SunOS 4.x.y options do not have  any  replace-
 ment in this release: -B nosymbolic (this is now the default
 if -B symbolic is not used), -d, -dc, and  -dp,  (these  are
 now  the default; see -b above to override the default), -M,
 -S, -t, -x, -X, and -ysym.

maybe that means -Xa is on by default in newer solaris?




Re: Problem compiling mod_perl 1.23 on Solaris 2.4

2000-05-06 Thread John D Groenveld

-Xa is a Sun WorkShop Compiler C 4.2 option,
 -X[a|c|s|t]
  Specifies the degree of conformance to the ANSI C stan-
  dard.  Specifies one of the following:

  a (ANSI)
   ANSI C plus K&R C compatibility  extensions,  with
   semantic  changes required by ANSI C.  Where K&R C
   and ANSI C specify  different  semantics  for  the
   same  construct,  the compiler will issue warnings
   about the conflict and use the ANSI C  interpreta-
   tion. This is the default compiler mode.
John
[EMAIL PROTECTED]





Re: Problem compiling mod_perl 1.23 on Solaris 2.4

2000-05-08 Thread Steve Hay

John D Groenveld wrote:

> -Xa is a Sun WorkShop Compiler C 4.2 option,
>  -X[a|c|s|t]
>   Specifies the degree of conformance to the ANSI C stan-
>   dard.  Specifies one of the following:
>
>   a (ANSI)
>ANSI C plus K&R C compatibility  extensions,  with
>semantic  changes required by ANSI C.  Where K&R C
>and ANSI C specify  different  semantics  for  the
>same  construct,  the compiler will issue warnings
>about the conflict and use the ANSI C  interpreta-
>tion. This is the default compiler mode.

The machine I was building on was Solaris 2.4 with the Sun Compiler v3.0
in which the cc manpage says "-Xt" ('transition') is the default.  I
also have a Solaris 2.6 machine with the Sun Compiler v4.0 which says,
like the snippet above, that "-Xa" is the default.

Steve Hay





Re: Problem compiling mod_perl 1.24 on Solaris 2.6

2000-05-23 Thread Doug MacEachern

On Tue, 23 May 2000, Fred Miller wrote:

> On 4/26/2000, Steve Hay wrote about "Problem compiling mod_perl 1.23 on
> Solaris 2.4"
> 
> I am experiencing what appears to be a very similar problem, but with
> more recent modules and OS. I am running mod_perl 1.24, Perl 5.6.0,
> Apache 1.3.12, Solaris 2.6

perl -V would help.  is your cc gcc or sun's?
looking at the line number, i would try replacing any occurance of:

perl_eval_sv -> eval_sv
perl_call_sv -> call_sv
perl_call_pv -> call_pv

why your compiler is tripping on those macros, i have no idea.




Re: Problem compiling mod_perl 1.24 on Solaris 2.6

2000-05-24 Thread Fred Miller

Doug MacEachern wrote:
> 
> On Tue, 23 May 2000, Fred Miller wrote:
> > I am experiencing what appears to be a very similar problem, but with
> > more recent modules and OS. I am running mod_perl 1.24, Perl 5.6.0,
> > Apache 1.3.12, Solaris 2.6
> 
> perl -V would help.  is your cc gcc or sun's?

# perl -V
Summary of my perl5 (revision 5.0 version 6 subversion 0) configuration:
  Platform:
osname=solaris, osvers=2.6, archname=sun4-solaris
uname='sunos dmci 5.6 generic_105181-03 sun4u sparc sunw,ultra-1 '
config_args=''
hint=recommended, useposix=true, d_sigaction=define
usethreads=undef use5005threads=undef useithreads=undef
usemultiplicity=undef
useperlio=undef d_sfio=undef uselargefiles=define 
use64bitint=undef use64bitall=undef uselongdouble=undef
usesocks=undef
  Compiler:
cc='cc', optimize='-O', gccversion=
cppflags='-I/usr/local/include'
ccflags ='-I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64'
stdchar='unsigned char', d_stdstdio=define, usevfork=false
intsize=4, longsize=4, ptrsize=4, doublesize=8
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, usemymalloc=y, prototype=define
  Linker and Libraries:
ld='cc', ldflags =' -L/usr/local/lib -L/opt/gnu/lib '
libpth=/usr/local/lib /opt/gnu/lib /lib /usr/lib /usr/ccs/lib
libs=-lsocket -lnsl -ldl -lm -lc -lcrypt -lsec
libc=/lib/libc.so, so=so, useshrplib=false, libperl=libperl.a
  Dynamic Linking:
dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' '
cccdlflags='-KPIC', lddlflags='-G -L/usr/local/lib -L/opt/gnu/lib'


Characteristics of this binary (from libperl): 
  Compile-time options: USE_LARGE_FILES
  Built under solaris
  Compiled at May 16 2000 16:01:12
  @INC:
/usr/local/lib/perl5/5.6.0/sun4-solaris
/usr/local/lib/perl5/5.6.0
/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris
/usr/local/lib/perl5/site_perl/5.6.0
/usr/local/lib/perl5/site_perl
.

Like I said, I'm a bit naive in these matters. I didn't specify using
gcc or cc. I used the same path to compile Perl, Apache, and Mod_Perl.
When I aaksed which gcc and which cc, my machine does report gcc
appearing in my path ahead of cc. Could that be the problem?

>looking at the line number, i would try replacing any occurance of:
>
> perl_eval_sv -> eval_sv
> perl_call_sv -> call_sv
> perl_call_pv -> call_pv

I wish I was experienced enough to know what this means.

Thanks for the help.

Fred


-- 
[EMAIL PROTECTED]
http://titan.iwu.edu/~fmiller/



Re: Problem compiling mod_perl 1.24 on Solaris 2.6

2000-05-24 Thread Fred Miller

Fred Miller wrote:
> 
> Doug MacEachern wrote: 
> >looking at the line number, i would try replacing any occurance of:
> >
> > perl_eval_sv -> eval_sv
> > perl_call_sv -> call_sv
> > perl_call_pv -> call_pv
> 
> I wish I was experienced enough to know what this means.


Now I think I'm starting to get confused.

I tried building Apache and mod_perl by hand, loosely following some
instructions I found on the web labeled "mod_perl installation".

This part worked
perl Makefile.PL APACHE_SRC=../apache_1.3.12/src NO_HTTPD=1 EVERYTHING=1
make
make install

All looked good

I added to apache_1.3.12/src/Configuration
addModule module/perl/libperl.a

and the following EXTRA_LIBS and EXTRA_CFLAGS
EXTRA_LIBS=`perl -MExtUtils::Embed -l ldopts`
EXTRA_CFLAGS='perl -MExtUtils::Embed -e ccopts`

I checked apache_1.3.12/src/modules/perl and a bunch of stuff had been
put in there from my mod_perl build

I then ran ./Configure form within apache_1.3.12/src - no problem
but when I ran make, I received familiar errors:

gcc -c -I../.. -I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE
-I../../os/unix -I../../include   -DSOLARIS2=260 -DMOD_PERL
-DUSE_PERL_SSI -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -DUSE_EXPAT -I../../lib/expat-lite -DNO_DL_NEEDED
`perl -MExtUtils::Embed -e ccopts` mod_auth.c
gcc -c -I../.. -I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE
-I../../os/unix -I../../include   -DSOLARIS2=260 -DMOD_PERL
-DUSE_PERL_SSI -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -DUSE_EXPAT -I../../lib/expat-lite -DNO_DL_NEEDED
`perl -MExtUtils::Embed -e ccopts` mod_setenvif.c
rm -f libstandard.a
ar cr libstandard.a mod_env.o mod_log_config.o mod_mime.o
mod_negotiation.o mod_status.o mod_include.o mod_autoindex.o mod_dir.o
mod_cgi.o mod_asis.o mod_imap.o mod_actions.o mod_userdir.o mod_alias.o
mod_access.o mod_auth.o mod_setenvif.o 
ranlib libstandard.a
<=== modules/standard
===> modules/perl
cc -O -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE
-DMOD_PERL_VERSION=\"1.24\" -DMOD_PERL_STRING_VERSION=\"mod_perl/1.24\"
-I../.. -I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE -I../../os/unix
-I../../include   -DSOLARIS2=260 -DMOD_PERL -DUSE_PERL_SSI
-I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64
-DUSE_EXPAT -I../../lib/expat-lite -DNO_DL_NEEDED `perl
-MExtUtils::Embed -e ccopts` -c mod_perl.c
"/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE/perl.h", line 1929:
warning: operand treated as unsigned: 0x87654321
"./mod_perl.h", line 584: warning: macro replacement within a string
literal
"./mod_perl.h", line 587: warning: macro replacement within a string
literal
"./mod_perl.h", line 590: warning: macro replacement within a string
literal
"./mod_perl.h", line 593: warning: macro replacement within a string
literal
"mod_perl.c", line 347: fatal: macro recursion
cc: acomp failed for mod_perl.c
make[2]: *** [mod_perl.o] Error 2
make[1]: *** [all] Error 1
make: *** [subdirs] Error 1

Recommendations for how best to proceed?
I find this quite curious, as I have Apache-1.3.12 working without
mod_perl, and mod_perl seemed to build just fine separate from Apache.

Thanks,
Fred

-- 
[EMAIL PROTECTED]
http://titan.iwu.edu/~fmiller/



Re: Problem compiling mod_perl 1.24 on Solaris 2.6

2000-05-25 Thread Doug MacEachern

On Wed, 24 May 2000, Fred Miller wrote:

> Like I said, I'm a bit naive in these matters. I didn't specify using
> gcc or cc. I used the same path to compile Perl, Apache, and Mod_Perl.
> When I aaksed which gcc and which cc, my machine does report gcc
> appearing in my path ahead of cc. Could that be the problem?

i could try re-building Perl like so:

% ./Configure -des -Dcc=gcc && make test && make install

that is, go with all the defaults, but force Perl to use gcc.




Re: Problem compiling mod_perl 1.24 on Solaris 2.6

2000-05-26 Thread Fred Miller

Doug MacEachern wrote:
> 
> On Wed, 24 May 2000, Fred Miller wrote:
> 
> > Like I said, I'm a bit naive in these matters. I didn't specify using
> > gcc or cc. I used the same path to compile Perl, Apache, and Mod_Perl.
> > When I aaksed which gcc and which cc, my machine does report gcc
> > appearing in my path ahead of cc. Could that be the problem?
> 
> i could try re-building Perl like so:
> 
> % ./Configure -des -Dcc=gcc && make test && make install
> 
> that is, go with all the defaults, but force Perl to use gcc.

Thank you very much. Sorry for being such a newbie. 
I rebuilt Perl with gcc, and then was able to get a build of Apache with
mod_perl.
Now to try and make this puppy learn a few tricks...

I appreciate your help and patience.

Best regards,

Fred Miller
-- 
[EMAIL PROTECTED]
http://titan.iwu.edu/~fmiller/



Re: Problem compiling mod_perl 1.24 on Solaris 2.6

2000-06-01 Thread Doug MacEachern

On Fri, 26 May 2000, Fred Miller wrote:
 
> Thank you very much. Sorry for being such a newbie. 

no need to apologize, this sort of problem isn't normal, if anyone should
say sorry, it's sun for their flawed compiler kit.

> I rebuilt Perl with gcc, and then was able to get a build of Apache with
> mod_perl.

great news.




Re: Trouble compiling mod_perl 1.24 with Apache 1.3.12

2000-08-08 Thread William R. Ward

[EMAIL PROTECTED] writes:
>On Tue, 1 Aug 2000, William R. Ward wrote:
>
>> 
>> When I try to run "perl Makefile.PL" I get this error:
>> 
>> sh: ./Configure: No such file or directory
>> can't open /Makefile No such file or directory at Makefile.PL line 617,  
>chunk 1.
>> 
>> The "configure" script that comes with Apache is spelled with a
>> lowercase "c".  When I edited Makefile.PL to fix this error and run it
>> again, I get this error:
>
>look again, apache has both a configure script and a src/Configure script.

Right you are.  In that case, I think the Makefile.PL is pretty
stupid.  It should check for the "src" directory and DWIM.

>please use the [EMAIL PROTECTED] list for support questions.

Then please put that e-mail address somewhere obvious on the
perl.apache.org website.  Yours was the only one I could find.
(It was listed as [EMAIL PROTECTED] too, which bounced).

>http://perl.apache.org/guide/ also has good install docs.

I was only able to find a link to this once I knew what to look for.
I was looking in the FAQ and found your e-mail address.

I'd suggest putting a link to this at the very top.  But even that
guide doesn't make the answer very obvious.

--Bill.

-- 
William R Ward  Bay View Consulting Services   http://www.bayview.com/~wrw/
[EMAIL PROTECTED]   PMB 339, 1803 Mission Stphone +1 831/423-3295
PGP Key 0x2BD331E5Santa Cruz, CA 95060 USA  fax +1 831/423-6499
Public key at http://www.bayview.com/~wrw/pubkey.txt  pager +1 831/458-8862



Re: Trouble compiling mod_perl 1.24 with Apache 1.3.12

2000-08-09 Thread Frank D. Cringle

[EMAIL PROTECTED] (William R. Ward) writes:
> [EMAIL PROTECTED] writes:
> >please use the [EMAIL PROTECTED] list for support questions.
> 
> Then please put that e-mail address somewhere obvious on the
> perl.apache.org website.  Yours was the only one I could find.
> (It was listed as [EMAIL PROTECTED] too, which bounced).
> 
> >http://perl.apache.org/guide/ also has good install docs.
> 
> I was only able to find a link to this once I knew what to look for.
> I was looking in the FAQ and found your e-mail address.

Which FAQ was that?

The only addresses in the mod_perl faq are
[EMAIL PROTECTED], [EMAIL PROTECTED] and my
own.

-- 
Frank Cringle,  [EMAIL PROTECTED]
voice: (+49 2304) 467101; fax: 943357



Re: Trouble compiling mod_perl 1.24 with Apache 1.3.12

2000-08-09 Thread William R. Ward

Frank D. Cringle writes:
>[EMAIL PROTECTED] (William R. Ward) writes:
>> [EMAIL PROTECTED] writes:
>> >please use the [EMAIL PROTECTED] list for support questions.
>> 
>> Then please put that e-mail address somewhere obvious on the
>> perl.apache.org website.  Yours was the only one I could find.
>> (It was listed as [EMAIL PROTECTED] too, which bounced).
>> 
>> >http://perl.apache.org/guide/ also has good install docs.
>> 
>> I was only able to find a link to this once I knew what to look for.
>> I was looking in the FAQ and found your e-mail address.
>
>Which FAQ was that?
>
>The only addresses in the mod_perl faq are
>[EMAIL PROTECTED], [EMAIL PROTECTED] and my
>own.

Sorry, I remembered wrong.  It wasn't the FAQ, actually, it was the
download page.

http://apache.perl.org/dist/

--Bill.

-- 
William R Ward  Bay View Consulting Services   http://www.bayview.com/~wrw/
[EMAIL PROTECTED]   PMB 339, 1803 Mission Stphone +1 831/423-3295
PGP Key 0x2BD331E5Santa Cruz, CA 95060 USA  fax +1 831/423-6499
Public key at http://www.bayview.com/~wrw/pubkey.txt  pager +1 831/458-8862



prob compiling mod_perl 1.24/perl 5.6.0/apache 1.3.12?

2000-08-30 Thread Daniel Piczak

can anyone be so kind to point out what i'm doing wrong ;o)

[beast]/home/beast/daniel/src/perl/mod_perl-1.24{139} root : make
(cd ../apache_1.3.12/src &&  make CC="cc";)
===> os/unix
<=== os/unix
===> ap
<=== ap
===> main
cc -c -I.. -I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE -I../os/unix -I../
include   -DSOLARIS2=260 -DMOD_PERL -DUSE_PERL_SSI -I/usr/local/include -D_L
ARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DUSE_EXPAT -I../lib/expat-lite -DNO_
DL_NEEDED `perl -MExtUtils::Embed -e
ccopts`   -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64  -
I/usr/local/lib/perl5/5.6.0/sun4-solaris/CORE  -I. -I../.. -DUSE_PERL_SSI -I
/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DMOD_PERL
http_config.c
In file included from /usr/include/sys/vnode.h:41,
 from /usr/include/sys/stream.h:21,
 from /usr/include/netinet/in.h:38,
 from ../include/ap_config.h:1081,
 from ../include/httpd.h:71,
 from http_config.c:75:
/usr/include/sys/resource.h:148: warning: `struct rlimit64' declared inside
parameter list
/usr/include/sys/resource.h:148: warning: its scope is only this definition
or declaration,
/usr/include/sys/resource.h:148: warning: which is probably not what you
want.
/usr/include/sys/resource.h:149: warning: `struct rlimit64' declared inside
parameter list
http_config.c: In function `ap_init_virtual_host':
http_config.c:1296: storage size of `limits' isn't known
*** Error code 1
make: Fatal error: Command failed for target `http_config.o'
Current working directory /ext4/home/daniel/src/perl/apache_1.3.12/src/main
*** Error code 1
make: Fatal error: Command failed for target `subdirs'
Current working directory /ext4/home/daniel/src/perl/apache_1.3.12/src
*** Error code 1
make: Fatal error: Command failed for target `apache_httpd'





Compiling mod_perl 1.24 with the Sun Solaris C Compiler

2001-01-19 Thread Matisse Enzer

I'm having trouble getting mod_perl 1.24 to compile using the Solaris compiler
(Version is: Sun WorkShop 6 2000/04/07 C 5.1)

Any ideas?

For various reasons I'm using the Apache 1.3.12 source tree, and I can compile
fine using gcc, but the Solaris compiler complains:


/opt/SUNWspro/WS6/bin/cc -c  -I../../os/unix -I../../include 
-DSOLARIS2=270 -DUSE_EXPAT -I../../lib/expat-lite 
`/export/home/matisse/devel/apache/apache_1.3.12/src/apaci` 
-I/usr/local/include 
-I/usr/local/lib/perl5/5.00503/sun4-solaris/CORE  -I. -I../.. 
-DUSE_PERL_SSI -DMOD_PERL -KPIC -DSHARED_MODULE mod_include.c && mv 
mod_include.o mod_include.lo
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: formal parameter lacks name: param #1
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: formal parameter lacks name: param #2
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: formal parameter lacks name: param #3
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: syntax error before or at: __attribute__
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: warning: syntax error:  empty declaration
"/usr/include/ctype.h", line 48: cannot recover from previous errors
cc: acomp failed for mod_include.c



PS: I need to use this compiler becaue i want to compile in another 
module, mod_curl.c (StoryServer)
which require the Solaris compiler.


-- 
---
Matisse Enzer
TechTv Web Engineering
[EMAIL PROTECTED]
415-355-4364 (desk)
415-225-6703 (cellphone)



Compiling mod_perl 1.24 with the Sun Solaris C Compiler

2001-01-23 Thread Matisse Enzer


This is a re-posting with a  bit more information:

I'm having trouble getting mod_perl 1.24 to compile using the Solaris compiler.


Compiler Version is: Sun WorkShop 6 2000/04/07 C 5.1)
OS is:   Solaris 2.7


Details:

For various reasons I'm using the Apache 1.3.12 source tree, and I can compile
fine using gcc, but the Solaris compiler complains:


/opt/SUNWspro/WS6/bin/cc -c  -I../../os/unix -I../../include 
-DSOLARIS2=270 -DUSE_EXPAT -I../../lib/expat-lite 
`/export/home/matisse/devel/apache/apache_1.3.12/src/apaci` 
-I/usr/local/include 
-I/usr/local/lib/perl5/5.00503/sun4-solaris/CORE  -I. -I../.. 
-DUSE_PERL_SSI -DMOD_PERL -KPIC -DSHARED_MODULE mod_include.c && mv 
mod_include.o mod_include.lo
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: formal parameter lacks name: param #1
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: formal parameter lacks name: param #2
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: formal parameter lacks name: param #3
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: syntax error before or at: __attribute__
"/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
319: warning: syntax error:  empty declaration
"/usr/include/ctype.h", line 48: cannot recover from previous errors
cc: acomp failed for mod_include.c

Line 319 of   /usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h   is:

 __attribute__((format (printf, 3, 4)));


which is part of:



#ifndef PerlIO_sprintf
extern int  PerlIO_sprintf  _((char *, int, const char *,...))
 __attribute__((format (printf, 3, 4)));
#endif


Steven Lembark <[EMAIL PROTECTED]> suggested:
>
>yup, a macro expansion.  thou art getting bit by the way in which
>the compiler on Solaris is hacking up the token replacement in
>this C macro.


Any ideas on how I can get this to compile with the Solaris compiler??

PS: I need to use this compiler because i want to compile in another 
module, mod_curl.c (StoryServer)
which requires the Solaris compiler.
-- 
---
Matisse Enzer
TechTv Web Engineering
[EMAIL PROTECTED]
415-355-4364 (desk)
415-225-6703 (cellphone)



OS X 10.1.5 problem: alloc.c not compiling mod_perl-1.27 / apache_1.3.26

2002-09-10 Thread Noam Solomon



The subject more or less says it all.  I've 
found one bug report online which is pretty similar, but
does not say much about a solution:
 
http://citadelle.intrinsec.com/mailing/current/HTML/ml_apache-server-bugs/0424.html
 
The errors look like:
alloc.c: in function 
'spawn_child_core':

alloc.c: 2291'STDIN_FILENO' 
undeclared
alloc.c: 2297 'STDIN_FILENO' 
undeclared

alloc.c: 2303 'STDIN_FILENO' 
undeclared
 
The compile command is the basic:
 
sudo perl Makefile.PL src="../apache_1.3.26/src" 
USE_APACI=1 EVERYTHING=1 DO_HTTPD=1
 
The one thing that is perhaps slightly unusual 
about the installation is that it's entirely offline.  This is an 
unfortunate fact of the security conscious network environment I'm operating 
in.
 
 


Re: Compiling mod_perl 1.24 with the Sun Solaris C Compiler

2001-01-24 Thread Jens-Uwe Mager

On Tue, Jan 23, 2001 at 02:02:57PM -0800, Matisse Enzer wrote:
> 
> This is a re-posting with a  bit more information:
> 
> I'm having trouble getting mod_perl 1.24 to compile using the Solaris compiler.
> 
> 
> Compiler Version is: Sun WorkShop 6 2000/04/07 C 5.1)
> OS is:   Solaris 2.7
> 
> 
> Details:
> 
> For various reasons I'm using the Apache 1.3.12 source tree, and I can compile
> fine using gcc, but the Solaris compiler complains:
> 
> 
> /opt/SUNWspro/WS6/bin/cc -c  -I../../os/unix -I../../include 
> -DSOLARIS2=270 -DUSE_EXPAT -I../../lib/expat-lite 
> `/export/home/matisse/devel/apache/apache_1.3.12/src/apaci` 
> -I/usr/local/include 
> -I/usr/local/lib/perl5/5.00503/sun4-solaris/CORE  -I. -I../.. 
> -DUSE_PERL_SSI -DMOD_PERL -KPIC -DSHARED_MODULE mod_include.c && mv 
> mod_include.o mod_include.lo
> "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
> 319: formal parameter lacks name: param #1
> "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
> 319: formal parameter lacks name: param #2
> "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
> 319: formal parameter lacks name: param #3
> "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
> 319: syntax error before or at: __attribute__
> "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line 
> 319: warning: syntax error:  empty declaration
> "/usr/include/ctype.h", line 48: cannot recover from previous errors
> cc: acomp failed for mod_include.c
> 
> Line 319 of   /usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h   is:
> 
>  __attribute__((format (printf, 3, 4)));
> 
> 

This probably means that perl is configured using the gcc compiler. As
with most plug-in systems it is recommended to compile all parts that
are loaded into one address space using the exactly same compiler, that
means in the modperl case all of Apache, Apache plug-ins, perl and perl
plug-ins should be compiled using the Sun Workshop C compiler. Mixing
compilers arbitrarily is asking for trouble.

-- 
Jens-Uwe Mager

HELIOS Software GmbH
Steinriede 3
30827 Garbsen
Germany

Phone:  +49 5131 709320
FAX:+49 5131 709325
Internet:   [EMAIL PROTECTED]



Re: Compiling mod_perl 1.24 with the Sun Solaris C Compiler

2001-01-24 Thread Matisse Enzer

Thanks, I'll try compiling perl with the Solaris compiler, and then 
Apache + mod_perl .


At 2:44 PM +0100 1/24/01, Jens-Uwe Mager wrote:
>On Tue, Jan 23, 2001 at 02:02:57PM -0800, Matisse Enzer wrote:
>>
>>  This is a re-posting with a  bit more information:
>>
>>  I'm having trouble getting mod_perl 1.24 to compile using the 
>>Solaris compiler.
>>
>>
>>  Compiler Version is: Sun WorkShop 6 2000/04/07 C 5.1)
>>  OS is:   Solaris 2.7
>>
>>
>>  Details:
>  >
>>  For various reasons I'm using the Apache 1.3.12 source tree, and I 
>>can compile
>>  fine using gcc, but the Solaris compiler complains:
>>
>>
>>  /opt/SUNWspro/WS6/bin/cc -c  -I../../os/unix -I../../include
>>  -DSOLARIS2=270 -DUSE_EXPAT -I../../lib/expat-lite
>>  `/export/home/matisse/devel/apache/apache_1.3.12/src/apaci`
>>  -I/usr/local/include
>>  -I/usr/local/lib/perl5/5.00503/sun4-solaris/CORE  -I. -I../..
>>  -DUSE_PERL_SSI -DMOD_PERL -KPIC -DSHARED_MODULE mod_include.c && mv
>>  mod_include.o mod_include.lo
>>  "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line
>>  319: formal parameter lacks name: param #1
>>  "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line
>>  319: formal parameter lacks name: param #2
>>  "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line
>>  319: formal parameter lacks name: param #3
>>  "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line
>>  319: syntax error before or at: __attribute__
>>  "/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h", line
>>  319: warning: syntax error:  empty declaration
>>  "/usr/include/ctype.h", line 48: cannot recover from previous errors
>>  cc: acomp failed for mod_include.c
>>
>>  Line 319 of 
>>/usr/local/lib/perl5/5.00503/sun4-solaris/CORE/iperlsys.h   is:
>>
>>   __attribute__((format 
>>(printf, 3, 4)));
>>
>  >
>
>This probably means that perl is configured using the gcc compiler. As
>with most plug-in systems it is recommended to compile all parts that
>are loaded into one address space using the exactly same compiler, that
>means in the modperl case all of Apache, Apache plug-ins, perl and perl
>plug-ins should be compiled using the Sun Workshop C compiler. Mixing
>compilers arbitrarily is asking for trouble.
>
>--
>Jens-Uwe Mager
>
>HELIOS Software GmbH
>Steinriede 3
>30827 Garbsen
>Germany
>
>Phone: +49 5131 709320
>FAX:   +49 5131 709325
>Internet:  [EMAIL PROTECTED]

-- 
---
Matisse Enzer
TechTv Web Engineering
[EMAIL PROTECTED]
415-355-4364 (desk)
415-225-6703 (cellphone)



Re: Compiling mod_perl 1.24 with the Sun Solaris C Compiler

2001-01-24 Thread G.W. Haywood

Hi all,

On Wed, 24 Jan 2001, Matisse Enzer wrote:

> Thanks, I'll try compiling perl with the Solaris compiler, and then 
> Apache + mod_perl .

Check the List archives for stuff about Solaris recently,
I'm sure you'll find some useful pointers.

73,
Ged.





  1   2   >