The following reply was made to PR os-irix/2829; it has been noted by GNATS.
From: Greg McGurk <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: os-irix/2829: wrong client ip address in access log Date: 11 Nov 1998 17:07:35 -0500 I believe the wrong ip address is caused by an inet_ntoa incompatibility between gcc and the Irix libraries. See http://reality.sgi.com/ariel/freeware/gcc-2.8.1-notes.html "Gcc does not correctly pass/return structures which are smaller than 16 bytes and which are not 8 bytes. The problem is very involved and difficult to fix. It affects a number of other targets also, but irix6 is affected the most, because it is a 64 bit target, and 4 byte structures are common. The exact problem is that structures are being padded at the wrong end, e.g. a 4 byte structure is loaded into the lower 4 bytes of the register when it should be loaded into the upper 4 bytes of the register." Gcc is consistent with itself, but not consistent with the SGI C compiler [and the SGI supplied runtime libraries], so the only failures that can happen are when there are library functions that take/return such structures. There are very few such library functions. I can only recall seeing a few of them: inet_ntoa, inet_aton, inet_lnaof, inet_netof, and semctl." [EMAIL PROTECTED] writes: > > [In order for any reply to be added to the PR database, ] > [you need to include <[EMAIL PROTECTED]> in the Cc line ] > [and leave the subject line UNCHANGED. This is not done] > [automatically because of the potential for mail loops. ] > [If you do not include this Cc, your reply may be ig- ] > [nored unless you are responding to an explicit request ] > [from a developer. ] > [Reply only with text; DO NOT SEND ATTACHMENTS! ] > > > Synopsis: wrong client ip address in access log > > State-Changed-From-To: open-closed > State-Changed-By: randy > State-Changed-When: Wed Nov 11 13:03:00 PST 1998 > State-Changed-Why: > This problem seems to be caused by compilation with gcc 2.8.1 > and derivatives. Newer version of Apache now use FCNTL locking > on this platform. >
