public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/100787] [12 Regression] Bootstrap failure caused by r12-1077
Date: Thu, 27 May 2021 07:21:28 +0000	[thread overview]
Message-ID: <bug-100787-4-7qhkL98uIu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100787-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100787

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'm using
mkdir ~/hbin
cat > ~/hbin/as <<\END
#!/bin/sh
exec /usr/bin/as --32 "$@"
END
cat > ~/hbin/g++ <<\END
#!/bin/sh
exec /usr/bin/g++ -m32 "$@"
END
cat > ~/hbin/gcc <<\END
#!/bin/sh
exec /usr/bin/gcc -m32 "$@"
END
cat > ~/hbin/ld <<\END
#!/bin/sh
case "$*" in
  --version) cat <<\EOF
GNU ld version 2.20.52.0.1-10.fc17 20100131
Copyright 2012 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.
EOF
  exit 0;;
esac
exec /usr/bin/ld -m elf_i386 -L /usr/lib/ "$@"
END
chmod 755 ~/hbin/{as,g++,gcc,ld}

and then use
PATH=~/hbin:$PATH i386 .../configure ...
PATH=~/hbin:$PATH i386 make ...
etc.

  parent reply	other threads:[~2021-05-27  7:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27  2:32 [Bug bootstrap/100787] New: " hjl.tools at gmail dot com
2021-05-27  3:25 ` [Bug middle-end/100787] " pinskia at gcc dot gnu.org
2021-05-27  6:55 ` [Bug tree-optimization/100787] " aldyh at gcc dot gnu.org
2021-05-27  7:21 ` jakub at gcc dot gnu.org [this message]
2021-05-27 11:38 ` aldyh at gcc dot gnu.org
2021-05-27 11:52 ` hjl.tools at gmail dot com
2021-05-28 10:35 ` rguenth at gcc dot gnu.org
2021-05-28 17:49 ` ro at gcc dot gnu.org
2021-05-28 18:02 ` jakub at gcc dot gnu.org
2021-05-28 18:02 ` aldyh at redhat dot com
2021-05-28 20:51 ` aldyh at gcc dot gnu.org
2021-05-29  5:45 ` cvs-commit at gcc dot gnu.org
2021-05-29  5:50 ` aldyh at gcc dot gnu.org
2021-05-29 21:39 ` ro at CeBiTec dot Uni-Bielefeld.DE
2021-06-01 15:00 ` aldyh at gcc dot gnu.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=bug-100787-4-7qhkL98uIu@http.gcc.gnu.org/bugzilla/ \
    --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).