You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Austin Gonyou <au...@coremetrics.com> on 2002/03/08 00:52:15 UTC

Compiling apache2 against glibc 2.2.5

Glibc 2.2.5 was compiled with gcc3. This is supposed to be allowable
with glibc 2.2.5, since it was unsupported prior. Does anyone know of
any issues doing this?

My binaries are portable, and that doesn't seem to be a problem. I'm
trying to gather information as I continue to try to chase down the
php4.2-dev + apache2 issue on this target platform. 

TIA.
-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb

Re: Compiling apache2 against glibc 2.2.5

Posted by Austin Gonyou <au...@coremetrics.com>.
On Fri, 2002-03-08 at 01:14, Justin Erenkrantz wrote:
> On Thu, Mar 07, 2002 at 05:52:15PM -0600, Austin Gonyou wrote:
>
> > My binaries are portable, and that doesn't seem to be a problem. I'm
> > trying to gather information as I continue to try to chase down the
> > php4.2-dev + apache2 issue on this target platform. 
> 
> What's your problem again?  -- justin

The problem is using PHP on glibc2.2.5 compiled by gcc3 with
apache2.0.32. I can use PHP as a cgi, no problem, but trying to use it
as  .so, is where I have problems. I've also sent another request to the
PHP list in the realm of glibc compiled by gcc3, and if I need to
explicitly specify the libgcc_s info. 

I think that may be part of the issue. 

I've found that PHP 4.2-dev works just fine, with apache 2.0.32, just
not my target.

-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb

Re: Compiling apache2 against glibc 2.2.5

Posted by David Ford <da...@blue-labs.org>.
GCC 3.x has been working quite well for me across my farm of servers. 
 I've been using it since it came out and I upgrade glibc when it comes 
out as well.

No problems noted w/ 24x7 uptime across a variety of cpu and hardware types.

David

Justin Erenkrantz wrote:

>On Thu, Mar 07, 2002 at 05:52:15PM -0600, Austin Gonyou wrote:
>
>>Glibc 2.2.5 was compiled with gcc3. This is supposed to be allowable
>>with glibc 2.2.5, since it was unsupported prior. Does anyone know of
>>any issues doing this?
>>
>
>I think you need the latest gcc version (3.0.4?) to compile glibc
>2.2.5 properly.  But, I'm not sure.  I'm not seeing any problems
>here with 2.2.4, but I don't trust gcc3 to compile glibc for a
>few more point releases.
>
>>My binaries are portable, and that doesn't seem to be a problem. I'm
>>trying to gather information as I continue to try to chase down the
>>php4.2-dev + apache2 issue on this target platform. 
>>
>
>What's your problem again?  -- justin
>


Re: Compiling apache2 against glibc 2.2.5

Posted by Justin Erenkrantz <je...@ebuilt.com>.
On Thu, Mar 07, 2002 at 05:52:15PM -0600, Austin Gonyou wrote:
> Glibc 2.2.5 was compiled with gcc3. This is supposed to be allowable
> with glibc 2.2.5, since it was unsupported prior. Does anyone know of
> any issues doing this?

I think you need the latest gcc version (3.0.4?) to compile glibc
2.2.5 properly.  But, I'm not sure.  I'm not seeing any problems
here with 2.2.4, but I don't trust gcc3 to compile glibc for a
few more point releases.

> My binaries are portable, and that doesn't seem to be a problem. I'm
> trying to gather information as I continue to try to chase down the
> php4.2-dev + apache2 issue on this target platform. 

What's your problem again?  -- justin


Re: Compiling apache2 against glibc 2.2.5

Posted by Austin Gonyou <au...@coremetrics.com>.
Right. I read that as well. There's info in the glibc docs about that.
Anyway, I've found that as LONG as you are using glibc 3.0.3 or 3.0.4,
with glibc 2.2.5, then the compatibility problem goes away. (per the
glibc changelog from 2.2.5)

This is specifically in the realm of 2.2.x, not previous.

On Fri, 2002-03-08 at 04:03, Sascha Schumann wrote:
> > My binaries are portable, and that doesn't seem to be a problem. I'm
> > trying to gather information as I continue to try to chase down the
> > php4.2-dev + apache2 issue on this target platform.
> 
>     Note that "portable" (as in can be used on various Linux
>     distributions) programs should be built with a glibc-2.1 (or
>     even 2.0).  Programs which are built with glibc-2.2.x don't
>     necessarily work with older versions, e.g. there is no
>     guarantee that a build against 2.2.5 will work with 2.2.4.
> 
>     - Sascha                                     Experience IRCG
>       http://schumann.cx/                http://schumann.cx/ircg
-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-698-7250
email: austin@coremetrics.com

"It is the part of a good shepherd to shear his flock, not to skin it."
Latin Proverb

Re: Compiling apache2 against glibc 2.2.5

Posted by Sascha Schumann <sa...@schumann.cx>.
> My binaries are portable, and that doesn't seem to be a problem. I'm
> trying to gather information as I continue to try to chase down the
> php4.2-dev + apache2 issue on this target platform.

    Note that "portable" (as in can be used on various Linux
    distributions) programs should be built with a glibc-2.1 (or
    even 2.0).  Programs which are built with glibc-2.2.x don't
    necessarily work with older versions, e.g. there is no
    guarantee that a build against 2.2.5 will work with 2.2.4.

    - Sascha                                     Experience IRCG
      http://schumann.cx/                http://schumann.cx/ircg