public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/20349] [multilib] libjava(32) doesn't build.
Date: Wed, 23 Mar 2005 05:36:00 -0000	[thread overview]
Message-ID: <20050323053600.25664.qmail@sourceware.org> (raw)
In-Reply-To: <20050306201934.20349.pluto@pld-linux.org>


------- Additional Comments From pinskia at gcc dot gnu dot org  2005-03-23 05:35 -------
This looks like a bug in your installation of glibc.
#define INIT_SEGV                                       \
do                                                      \
  {                                                     \
    struct old_i386_kernel_sigaction kact;              \
    kact.k_sa_handler = catch_segv;                     \
    kact.k_sa_mask = 0;                                 \
    kact.k_sa_flags = 0x4000000;                        \
    kact.sa_restorer = restore;                         \
    syscall (SYS_sigaction, SIGSEGV, &kact, NULL);      \
  }                                                     \
while (0)   


This works on a "native" 32bit compiler with a "native" 32bit glibc.

Can you confirm that this is your bug in your installation of glibc?

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20349


  parent reply	other threads:[~2005-03-23  5:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-06 20:19 [Bug other/20349] New: " pluto at pld-linux dot org
2005-03-06 20:23 ` [Bug other/20349] " pinskia at gcc dot gnu dot org
2005-03-07  7:21 ` pluto at pld-linux dot org
2005-03-23  5:36 ` pinskia at gcc dot gnu dot org [this message]
2005-03-25 12:37 ` pluto at pld-linux dot org
2005-03-25 13:02 ` aj at gcc dot gnu dot org
2005-03-25 14:05 ` pluto at pld-linux dot org
2005-03-25 15:07 ` schwab at suse dot de
2005-03-25 17:10 ` pinskia at gcc dot gnu dot org

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=20050323053600.25664.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).