public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dennis Clarke <dclarke@blastwave.org>
To: gcc-help@gcc.gnu.org
Subject: Re: on old Red Hat : 9.4.0 fails in stage3 bootstrap due to __asm__ ("ntp_gettimex") __THROW;
Date: Sun, 15 May 2022 10:17:19 -0400	[thread overview]
Message-ID: <436925d7-7fb7-c7f4-3e81-26db8b1f33cb@blastwave.org> (raw)
In-Reply-To: <a6200280-da28-7c68-45c9-f45597e034ec@blastwave.org>

On 5/15/22 09:55, Dennis Clarke via Gcc-help wrote:
> 
> *baffled* again here.

Risking the self reply but maybe this is related :

     Bug 61955 - libsanitizer fails to compile on RHEL4
     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61955

The kernel on this box is old. This old server was installed from the
actual red coloured cardboard box and the installation DVD. I even
have the cute bumper stickers in the box still. Thus the Linux kernel
here is from way way back :

mimas$ cat /proc/version
Linux version 2.6.32-71.el6.x86_64 
(mockbuild@x86-007.build.bos.redhat.com) (gcc version 4.4.4 20100726 
(Red Hat 4.4.4-13) (GCC) ) #1 SMP Wed Sep 1 01:33:01 EDT 2010
mimas$

Looking into https://cdn.kernel.org/pub/linux/kernel/v2.6/  my guess is
somewhere from 2009 or so.

The last comment from Andrew Pinski in that bug report suggests it may
be possible ( no promise ) to start over with --disable-libsanitiser and
hope for the best.

Dennis

  reply	other threads:[~2022-05-15 14:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-15 13:55 Dennis Clarke
2022-05-15 14:17 ` Dennis Clarke [this message]
2022-05-15 20:45   ` Jonathan Wakely
2022-05-15 21:16     ` Dennis Clarke

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=436925d7-7fb7-c7f4-3e81-26db8b1f33cb@blastwave.org \
    --to=dclarke@blastwave.org \
    --cc=gcc-help@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).