public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gaius at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/106443] Many 32-bit tests FAIL to link on Solaris/sparcv9
Date: Sun, 07 Aug 2022 23:08:46 +0000	[thread overview]
Message-ID: <bug-106443-4-g9pPVBjkPL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106443-4@http.gcc.gnu.org/bugzilla/>

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

Gaius Mulley <gaius at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2022-08-07
            Version|12.0                        |13.0

--- Comment #1 from Gaius Mulley <gaius at gcc dot gnu.org> ---
I've pushed a fix to devel/modula2 to fix multilib install (seen on amd64).  It
now builds and installs multilib.  Prior to this fix the 32 bit libraries were
installed over the 64 bit libraries when multilib was enabled.  Curious as to
whether this fixes the linking bugs on Solaris.

  reply	other threads:[~2022-08-07 23:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-26  7:43 [Bug modula2/106443] New: " ro at gcc dot gnu.org
2022-08-07 23:08 ` gaius at gcc dot gnu.org [this message]
2022-08-09 14:25 ` [Bug modula2/106443] " ro at CeBiTec dot Uni-Bielefeld.DE
2022-08-10 11:24 ` gaius at gcc dot gnu.org
2022-09-13  8:14 ` gaius at gcc dot gnu.org
2022-09-14 11:39 ` ro 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-106443-4-g9pPVBjkPL@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).