compile problems

2004-12-17 Thread Matthew Berk
Apologies if I'm posting in the wrong place, but here goes: AMD Opteron, Suse 9.1, perl 5.8.6, Apache 2.0.52, mod_perl 1.99_17 Apache compiles fine. When compiling mod_perl, I execute "/usr/local/bin/perl Makefile.PL MP_APXS=/usr/local/apache2/bin/apxs" and then make, and get: /usr/lib64/gcc-l

Re: compile problems

2004-12-17 Thread Stas Bekman
Matthew Berk wrote: Apologies if I'm posting in the wrong place, but here goes: AMD Opteron, Suse 9.1, perl 5.8.6, Apache 2.0.52, mod_perl 1.99_17 Apache compiles fine. When compiling mod_perl, I execute "/usr/local/bin/perl Makefile.PL MP_APXS=/usr/local/apache2/bin/apxs" and then make, and ge

RE: compile problems

2004-12-17 Thread Barksdale, Ray
ED] > Sent: Friday, December 17, 2004 10:12 AM > To: Matthew Berk > Cc: [EMAIL PROTECTED] > Subject: Re: compile problems > > Matthew Berk wrote: > > Apologies if I'm posting in the wrong place, but here goes: > > > > AMD Opteron, Suse 9.1, perl 5.8.6, A

Re: compile problems

2004-12-17 Thread Stas Bekman
Barksdale, Ray wrote: On a side note everything works fine for a static build. Modules (Apache::Scoreboard and Apache::VMonitor) required a little tweaking but worked. What were the problems in those modules? -- __ Stas Bekman

Re: compile problems

2004-12-17 Thread Joe Schaefer
"Barksdale, Ray" <[EMAIL PROTECTED]> writes: [...] > /usr/bin/ld: > /usr/local/lib/perl5/5.8.5/x86_64-linux/auto/DynaLoader/DynaLoader.a(DynaLoa > der.o): relocation R_X86_64_32 can not be used when making a shared object; > recompile with -fPIC > /usr/local/lib/perl5/5.8.5/x86_64-linux/auto/Dyna

RE: compile problems

2004-12-17 Thread Barksdale, Ray
> Cc: [EMAIL PROTECTED] > Subject: Re: compile problems > > Barksdale, Ray wrote: > > > On a side note everything works fine for a static build. Modules > > (Apache::Scoreboard > > and Apache::VMonitor) required a little tweaking bu

Re: compile problems

2004-12-17 Thread Stas Bekman
Barksdale, Ray wrote: I mis-typed. It was only Apache::Scoreboard that needed tweaking. Don't recall the specific error message but when building a static mod_perl with 1.99_17 it mucked arround with the include files in the Apache build directory. The fix was changing INC = -I/usr/local/apache2/in

RE: compile problems

2004-12-17 Thread Barksdale, Ray
Built my own perl in /usr/local. Made sure they weren't comingling. > -Original Message- > From: news [mailto:[EMAIL PROTECTED] On Behalf Of Joe Schaefer > Sent: Friday, December 17, 2004 12:28 PM > To: [EMAIL PROTECTED] > Subject: Re: compile problems > >

Re: compile problems

2004-12-17 Thread Stas Bekman
Barksdale, Ray wrote: ok. Had "cccdlflags='-fPIC'". Just set "useshrplib=true". Rebuilt 5.8.5, tested ok, installed. Built mod_perl 1.99_17. Built ok. Failed two tests: apr-ext/finfo.t and apr-ext/util. Have to figure that out in a bit. Work has interrupted. If those are the same failures that I've

RE: compile problems

2004-12-17 Thread Barksdale, Ray
book, I broke the binding :( > -Original Message- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Friday, December 17, 2004 3:20 PM > To: Barksdale, Ray > Cc: [EMAIL PROTECTED] > Subject: Re: compile problems > > Barksdale, Ray wrote: > > > ok. Had "cccdlflags=

Re: compile problems

2004-12-17 Thread Stas Bekman
Barksdale, Ray wrote: ok. 1.99_18 fixes the two test failures. Couldn't get to current svn. Kept timing out. Couldn't get to the cvs snapshots either. I'll try that again Monday. Yeah svn.apache.org has hardware problems. both reside on that machine. May try compiling everything with "-m64" just t

Re: compile problems

2004-12-20 Thread Matthew Berk
Found a solution worth writing about. I went through the perl configuration interactively, specifying the following non-defaults: - compile perl as shared - use gcc, not cc, as the compiler - provide -fPIC to the compiler After this, everything worked like a charm! On Dec 17, 2004, at 2:05 AM

RE: compile problems

2004-12-22 Thread Barksdale, Ray
age- > From: Matthew Berk [mailto:[EMAIL PROTECTED] > Sent: Monday, December 20, 2004 8:44 AM > To: modperl@perl.apache.org > Subject: Re: compile problems > > Found a solution worth writing about. I went through the perl > configuration interactively, specifying th

Re: compile problems

2004-12-22 Thread Stas Bekman
Barksdale, Ray wrote: Hmm, I managed to get it to work with either -fpic or -fPIC after switching to shared perl. Also built with -m64. I noticed Apache (at least 2.0.52) configures/compiles for -fPIC automagically. But once it loads, it is BIG. (note lotta Apache modules, Apache::Requ

RE: compile problems

2004-12-22 Thread Barksdale, Ray
> -Original Message- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 22, 2004 2:28 PM > To: Barksdale, Ray > Cc: Matthew Berk; modperl@perl.apache.org > Subject: Re: compile problems > > > Total: 608169K ( 580M) size, 145465K

Re: compile problems

2004-12-22 Thread Stas Bekman
Barksdale, Ray wrote: Total: 608169K ( 580M) size, 145465K ( 139M) approx real size (-shared) wow, that's a lot. Which mpm is that? Must be worker. And if you don't load any modules? Prefork. That's what you would think :\ PID Size Share VSize Rss M Elapsed LastReq Srvd Client

RE: compile problems

2004-12-22 Thread Barksdale, Ray
Original Message- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 22, 2004 3:17 PM > To: Barksdale, Ray > Cc: modperl@perl.apache.org > Subject: Re: compile problems > > Barksdale, Ray wrote: > > >>>Total: 608169K ( 580M) size

Re: compile problems

2004-12-22 Thread Stas Bekman
Barksdale, Ray wrote: 1 thru 6: without mod_perl 7 thru 12: with mod_perl. Kinda takes you're breath (and ram) away. 1 8738 root 17.1M 15.9M 17.1M 2.0M S httpd 2 8739 nobody 17.1M 15.9M 17.1M 2.0M S httpd 3 8740 nobody 17.1M 15.9M 17.1M 2.0M

RE: compile problems

2004-12-22 Thread Barksdale, Ray
> -Original Message- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 22, 2004 4:23 PM > To: Barksdale, Ray > Cc: modperl@perl.apache.org > Subject: Re: compile problems > > something is very wrong then. On linux I get: > > Apach

Re: compile problems

2004-12-22 Thread Stas Bekman
Barksdale, Ray wrote: I agree it should be much smaller. From your reply I seem to have given the impression I was running on something other than Linux. Sorry about that. We run Redhat's Fedora Core 2 Linux on x86 (32-bit) for prod/testing. This was our first try at 64-bit (Redhat Fedora Core 2 AM

RE: compile problems

2004-12-28 Thread Barksdale, Ray
Realized it just after I hit "send". Mail is moving rather quickly today... > -Original Message- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 28, 2004 4:48 PM > To: Barksdale, Ray > Subject: Re: compile problems > > Ray, p

Re: compile problems

2004-12-28 Thread Stas Bekman
Barksdale, Ray wrote: >>OK, so it has something to do with 64-bit-ness. But I didn't >>understand. >>Was this problem seen on a 64-bit CPU or on a 32-bit CPU, but >>then code >>was compiled for 64-bit? > > > The problem (more of an observation at this point) was the apparent > excessive memory usag

RE: compile problems

2004-12-28 Thread Barksdale, Ray
> -Original Message- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 28, 2004 5:02 PM > To: Barksdale, Ray > Cc: modperl@perl.apache.org > Subject: Re: compile problems > > > As far as the memory usage problem I thought I was on t

Re: compile problems

2004-12-28 Thread Stas Bekman
> (both without mod_perl) but this resulted in a minimal gain once > mod_perl was loaded. How much added in numbers? Should have said "minimal savings". From this: Total: 608169K ( 580M) size, 145465K ( 139M) approx real size (-shared) down to this: Total: 600129K ( 572M) size, 131588K (

RE: compile problems

2004-12-28 Thread Barksdale, Ray
> -Original Message- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 28, 2004 5:18 PM > To: Barksdale, Ray > Cc: modperl@perl.apache.org > Subject: Re: compile problems > > > >> > (both without mod_perl) but this resulted in

Re: compile problems

2004-12-28 Thread Joe Schaefer
"Barksdale, Ray" <[EMAIL PROTECTED]> writes: [...] >> >>From this: >> > Total: 608169K ( 580M) size, 145465K ( 139M) approx >> real size (-shared) >> > >> > down to this: >> > Total: 600129K ( 572M) size, 131588K ( 125M) approx >> real size (-shared) Are you sure this isn't just some

RE: compile problems

2004-12-29 Thread Barksdale, Ray
> -Original Message- > From: Joe Schaefer [mailto:[EMAIL PROTECTED] > Sent: Tuesday, December 28, 2004 7:30 PM > To: mod_perl user list > Subject: Re: compile problems > > "Barksdale, Ray" <[EMAIL PROTECTED]> writes: > > [...] > >

Re: compile problems

2004-12-29 Thread Stas Bekman
Barksdale, Ray wrote: Here's a possibly relevant link I found while googling for an answer: https://www.redhat.com/archives/amd64-list/2004-September/msg0 0003.html I'm glad you found this. I was going to build a new gcc and friends this afternoon. Looks like that's it. I'm seeing a 5-fold diffe

Compile Problems with perl-5.10.0

2008-01-04 Thread James Kosin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm in the process of updating all my packages for perl; however, mod_perl 2.0.3 fails as follows: + cd mod_perl-2.0.3 + LANG=C + export LANG + unset DISPLAY + CFLAGS=-O2 -g -pipe -march=i386 -mcpu=i686 + /usr/bin/perl Makefile.PL PREFIX=/var/tmp/

libapreq2-2.06-dev MM.pm compile problems

2005-10-15 Thread eps com estem
Hi, in the procedure to compile new apache+modperl2+apreq2 i'm finding problems with apreq2 compilation. perl 5.87 apache 2.0.55 modperl 2.01 ExtUtils-XSBuilder-0.27 libapreq2-2.06-dev The commands i do #perl /Configure -des -Dusethreads make make install #apache /configure --prefix=/usr/local

Re: Compile Problems with perl-5.10.0

2008-01-04 Thread Fred Moyer
James Kosin wrote: -BEGIN PGP SIGNED MESSAGE- modperl_interp.c: In function `modperl_interp_unselect': modperl_interp.c:294: error: structure has no member named `xmg_magic' modperl_interp.c: In function `modperl_interp_select': modperl_interp.c:509: error: structure has no member named `

Re: Compile Problems with perl-5.10.0

2008-01-07 Thread James Kosin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Kosin wrote: | + make 'OPTIMIZE=-O2 -g -pipe -march=i386 -mcpu=i686' | cd "src/modules/perl" && make | make[1]: Entering directory `/usr/src/redhat/BUILD/mod_perl-2.0.3/src/modules/perl' | gcc -I/usr/src/redhat/BUILD/mod_perl-2.0.3/src/modules/

Re: Compile Problems with perl-5.10.0

2008-01-07 Thread James Kosin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Kosin wrote: | + make 'OPTIMIZE=-O2 -g -pipe -march=i386 -mcpu=i686' | cd "src/modules/perl" && make | make[1]: Entering directory `/usr/src/redhat/BUILD/mod_perl-2.0.3/src/modules/perl' | gcc -I/usr/src/redhat/BUILD/mod_perl-2.0.3/src/modules/

Re: libapreq2-2.06-dev MM.pm compile problems

2005-10-15 Thread Philip M. Gollucci
eps com estem wrote: Hi, in the procedure to compile new apache+modperl2+apreq2 i'm finding problems with apreq2 compilation. perl 5.87 apache 2.0.55 modperl 2.01 ExtUtils-XSBuilder-0.27 libapreq2-2.06-dev The commands i do #perl /Configure -des -Dusethreads make make install good. #apache

Re: libapreq2-2.06-dev MM.pm compile problems

2005-10-16 Thread eps com estem
I've recompile everything with your purposed changes (i wasn't understanding what a mp2 statically build did mean), but i get the same error in apreq2. What i've done: #perl /Configure -des -Dusethreads make make install #modperl perl Makefile.PL MP_USE_STATIC=1 MP_AP_PREFIX="/blah/sources/htt

Re: libapreq2-2.06-dev MM.pm compile problems

2005-10-16 Thread Philip M. Gollucci
eps com estem wrote: I've recompile everything with your purposed changes (i wasn't understanding what a mp2 statically build did mean), but i get the same error in apreq2. #modperl perl Makefile.PL MP_USE_STATIC=1 MP_AP_PREFIX="/blah/sources/httpd-2.0.55/" \ MP_AP_CONFIGURE="--with-mpm=prefork

Re: libapreq2-2.06-dev MM.pm compile problems

2005-10-16 Thread eps com estem
Ok, you are right. A huge monkey is the cause that i didn't make && make install the modperl module o_O Done! I've had to compile also Parse-RecDescent cause apreq claimed it didn't found. Now apparently everything has gone right. Thanks! >eps com estem wrote: >> I've recompile everything