All of lore.kernel.org
 help / color / mirror / Atom feed
From: "José de Paula" <espinafre@gmail.com>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: post 2.6.7 BK change breaks Java?
Date: Fri, 9 Jul 2004 13:37:18 -0300	[thread overview]
Message-ID: <5ef8c2f004070909372db80ca8@mail.gmail.com> (raw)
In-Reply-To: <40EEB1B2.7000800@kolivas.org>

I found that compiling 2.6.7-bk18 and 2.6.7-bk20 with  GCC 2.95 does
away with these random Java segmentation faults. Kernels compiled with
GCC 3.3, 3.2 and 3.0 on the same system, however, have this Java
problem. I hope this helps.

  reply	other threads:[~2004-07-09 16:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-05 23:11 post 2.6.7 BK change breaks Java? Matthias Andree
2004-07-06 15:55 ` John Richard Moser
2004-07-06 16:14   ` Matthias Andree
2004-07-06 17:49     ` John Richard Moser
2004-07-06 22:45     ` Andy Isaacson
2004-07-09 13:51 ` Jesper Juhl
2004-07-09 14:54   ` Con Kolivas
2004-07-09 16:37     ` José de Paula [this message]
2004-07-09 17:55     ` Jesper Juhl
2004-07-10 11:41       ` Go Taniguchi
2004-07-11 15:16       ` Jesper Juhl
2004-07-11 15:19         ` Con Kolivas
2004-07-11 15:35           ` Jesper Juhl
2004-07-11 15:35         ` Grzegorz Kulewski
2004-07-11 15:38           ` Jesper Juhl
2004-07-12  0:56             ` Jesper Juhl
2004-07-12  3:20               ` Brian Gerst
2004-07-12  3:57                 ` Brian Gerst
2004-07-12 11:01                   ` Jesper Juhl
2004-07-12 12:38                     ` Brian Gerst
2004-07-12 14:05                       ` Matthias Andree
2004-07-12 15:59                       ` Linus Torvalds
2004-07-12 21:50                   ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2004-07-06 18:38 Ray Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ef8c2f004070909372db80ca8@mail.gmail.com \
    --to=espinafre@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.