Re: [mp2] modperl2 compile error

[prev] [thread] [next] [Date index for 2005/05/04]

From: Marc =?ISO-8859-1?Q?Gr=E0cia?=
Subject: Re: [mp2] modperl2 compile error
Date: 10:09 on 04 May 2005

--=-DSZOq1uObV2jrGbOkKVx
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

El dl 02 de 05 del 2005 a les 10:05 -0700, en/na Stas Bekman va
escriure:

> Marc Gràcia wrote:
> > I had some problems like this on my new x86_64 machine with mod_perl2,
> > seems that not only perl must be compiled with -fPIC , also apache and
> > all libraries or modules you plan to use. I think it's a general issue
> > with this architecture, not mod_perl related.
> 
> That's correct, Marc.
> 
> > If not, there are runtime linking relocation errors everywhere.. (I also
> > had to recompile with -fPIC db and libz, for example)
> > Maybe that's the problem...
> 
> I supposed that Tom has recompiled everything after rebuilding perl. 
> mod_perl will pick up -fPIC automatically at compile time, if perl was 
> compiled with it.

Yes that's Ok for all perl modules.
But BTW, my Perl Compilation did not put automaticaly the -fPIC flag
when configuring and also didn't detect the needed libraries (The line
when Config script lets you add additional libraries was empty except
for the ones i compiled for myself, see below).
I had to put all that manually (After a lot of recompilations trying to
find what was happening)

I was using a closed environment in a user with no root permissions. All
dependencies except most basic ones (libc,lpthreads,etc..) are compiled
and self contained in the user's home (I'm doing a untar-and-forget
instalation for our product).
The same procedure went OK on all other kind of machines... so maybe
perl Config has some problem with x86_64.
The base system was a Fedora Core 3 EM64T version with no 32bits
compatibility packages installed.
But everything is running OK after all, only the Configure script
failed..

> 

        -- 
        Marc Gràcia <mgracia@xxxxxxxxx.xxx>

--=-DSZOq1uObV2jrGbOkKVx
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.2.4">
</HEAD>
<BODY>
El dl 02 de 05 del 2005 a les 10:05 -0700, en/na Stas Bekman va escriure:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Marc Gr&#224;cia wrote:</FONT>
<FONT COLOR="#000000">&gt; I had some problems like this on my new x86_64 machine with mod_perl2,</FONT>
<FONT COLOR="#000000">&gt; seems that not only perl must be compiled with -fPIC , also apache and</FONT>
<FONT COLOR="#000000">&gt; all libraries or modules you plan to use. I think it's a general issue</FONT>
<FONT COLOR="#000000">&gt; with this architecture, not mod_perl related.</FONT>

<FONT COLOR="#000000">That's correct, Marc.</FONT>

<FONT COLOR="#000000">&gt; If not, there are runtime linking relocation errors everywhere.. (I also</FONT>
<FONT COLOR="#000000">&gt; had to recompile with -fPIC db and libz, for example)</FONT>
<FONT COLOR="#000000">&gt; Maybe that's the problem...</FONT>

<FONT COLOR="#000000">I supposed that Tom has recompiled everything after rebuilding perl. </FONT>
<FONT COLOR="#000000">mod_perl will pick up -fPIC automatically at compile time, if perl was </FONT>
<FONT COLOR="#000000">compiled with it.</FONT>
</PRE>
</BLOCKQUOTE>
Yes that's Ok for all perl modules.<BR>
But BTW, my Perl Compilation did not put automaticaly the -fPIC flag when configuring and also didn't detect the needed libraries (The line when Config script lets you add additional libraries was empty except for the ones i compiled for myself, see below).<BR>
I had to put all that manually (After a lot of recompilations trying to find what was happening)<BR>
<BR>
I was using a closed environment in a user with no root permissions. All dependencies except most basic ones (libc,lpthreads,etc..) are compiled and self contained in the user's home (I'm doing a untar-and-forget instalation for our product).<BR>
The same procedure went OK on all other kind of machines... so maybe perl Config has some problem with x86_64.<BR>
The base system was a Fedora Core 3 EM64T version with no 32bits compatibility packages installed.<BR>
But everything is running OK after all, only the Configure script failed..<BR>
<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>

</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
-- <BR>
Marc Gr&#224;cia &lt;<A HREF="mailto:mgracia@xxxxxxxxx.xxx">mgracia@xxxxxxxxx.xxx</A>&gt;
</TD>
</TR>
</TABLE>
</BODY>
</HTML>

--=-DSZOq1uObV2jrGbOkKVx--

(message missing)

[mp2] modperl2 compile error
Tom Caldwell 16:35 on 27 Apr 2005

Re: [mp2] modperl2 compile error
Stas Bekman 16:41 on 27 Apr 2005

Re: [mp2] modperl2 compile error
Stas Bekman 16:36 on 28 Apr 2005

Re: [mp2] modperl2 compile error
Tom Caldwell 19:46 on 28 Apr 2005

Re: [mp2] modperl2 compile error
Stas Bekman 20:55 on 28 Apr 2005

Re: [mp2] modperl2 compile error
Tom Caldwell 18:54 on 29 Apr 2005

Re: [mp2] modperl2 compile error
Stas Bekman 06:25 on 30 Apr 2005

Re: [mp2] modperl2 compile error
Marc =?ISO-8859-1?Q?Gr=E0cia?= 07:53 on 02 May 2005

Re: [mp2] modperl2 compile error
Stas Bekman 17:05 on 02 May 2005

Re: [mp2] modperl2 compile error
Marc =?ISO-8859-1?Q?Gr=E0cia?= 10:09 on 04 May 2005

Re: [mp2] modperl2 compile error
Tom Caldwell 15:09 on 04 May 2005

Re: [mp2] modperl2 compile error
Marc =?ISO-8859-1?Q?Gr=E0cia?= 10:26 on 05 May 2005

Re: [mp2] modperl2 compile error
Stas Bekman 05:23 on 06 May 2005

Re: [mp2] modperl2 compile error
Tom Caldwell 20:03 on 09 May 2005

Re: [mp2] modperl2 compile error
Tom Caldwell 22:24 on 02 May 2005

Re: [mp2] modperl2 compile error
Stas Bekman 06:40 on 03 May 2005

Re: [mp2] modperl2 compile error
Stas Bekman 05:51 on 03 May 2005

Re: [mp2] modperl2 compile error
Stas Bekman 20:46 on 09 May 2005