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
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
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
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.
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
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
