On Mon, Jun 25, 2001 at 08:16:06AM -0700, Ian Holsman wrote:
> There was a update to GCC from redhat over the weekend, did you
> apply that patch perhaps?
I didn't touch anything. That's what makes it odd. It didn't work, and
now it does. -- justin
On 24 Jun 2001 20:07:02 -0700, Justin Erenkrantz wrote:
> FWIW, I can't seem to reproduce the problem now. I know that I was
> getting odd things last night, but I can't seem to get it to happen
> again today. Grr. I feel silly. I could put a note in the STATUS
> file that we've seen some oddi
> > > Thoughts? Should we just avoid this problem and tell anyone using a
> > > default install of Mandrake that they are screwed? Or, do we just
> > > disable compiler optimizations with gcc 2.96? -- justin
> >
> > We shouldn't have to work around bugs in beta versions of the compiler.
> > If
FWIW, I can't seem to reproduce the problem now. I know that I was
getting odd things last night, but I can't seem to get it to happen
again today. Grr. I feel silly. I could put a note in the STATUS
file that we've seen some oddities with GCC 2.96. I swear I wasn't
making it up - I *was* get
On Sun, 24 Jun 2001 [EMAIL PROTECTED] wrote:
> "Your compiler is known to have bugs which stop Apache from working
> properly. Please re-configure with CFLAGS=-O2"
CFLAGS=-O0
+1
> This gets around the problem, but doesn't make us responsible for fixing
> RH and Mandrake's mistakes. If there w
On Sun, 24 Jun 2001 [EMAIL PROTECTED] wrote:
> > Thoughts? Should we just avoid this problem and tell anyone using a
> > default install of Mandrake that they are screwed? Or, do we just
> > disable compiler optimizations with gcc 2.96? -- justin
>
> We shouldn't have to work around bugs in bet
On Sun, Jun 24, 2001 at 01:09:11AM -0700, Justin Erenkrantz wrote:
> On Sat, Jun 23, 2001 at 07:42:28PM -0700, Justin Erenkrantz wrote:
> > I just ran across a compiler bug when dealing with long long in the GCC
> > shipped with Mandrake 8.0 (Intel). When -O2 is specified (it's in the
> > default)
> I just ran across a compiler bug when dealing with long long in the GCC
> shipped with Mandrake 8.0 (Intel). When -O2 is specified (it's in the
> default), it seems to lose the upper 32 bits of the 64 bit integers.
> (I was playing with the XML code in apr-util and the return values from
> elem
On Sun, 24 Jun 2001, Dale Ghent wrote:
> When Apache was compile sans -O2, everything worked well and there was no
> segfault.
What about -O?
> You're right... because of a 2.96 snapshot was used in RH, the use of
> 2.96 (I'm assuming any snapshot. I see that your's was older than mine)
> should
On Sat, 23 Jun 2001, Justin Erenkrantz wrote:
| I just ran across a compiler bug when dealing with long long in the GCC
| shipped with Mandrake 8.0 (Intel). When -O2 is specified (it's in the
| default), it seems to lose the upper 32 bits of the 64 bit integers.
| (I was playing with the XML code
On Sat, Jun 23, 2001 at 07:42:28PM -0700, Justin Erenkrantz wrote:
> I just ran across a compiler bug when dealing with long long in the GCC
> shipped with Mandrake 8.0 (Intel). When -O2 is specified (it's in the
> default), it seems to lose the upper 32 bits of the 64 bit integers.
> (I was playi
I just ran across a compiler bug when dealing with long long in the GCC
shipped with Mandrake 8.0 (Intel). When -O2 is specified (it's in the
default), it seems to lose the upper 32 bits of the 64 bit integers.
(I was playing with the XML code in apr-util and the return values from
elem_size() wer
12 matches
Mail list logo
