public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "svante.signell at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/98496] [11 Regression] bootstrap broken in libgo on i686-gnu
Date: Sun, 10 Jan 2021 16:34:34 +0000	[thread overview]
Message-ID: <bug-98496-4-LXdcZp4DwS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98496-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Svante Signell <svante.signell at gmail dot com> ---
Hello,

The 6 attached patches are improving the build and tests of gccgo for Hurd.
Attachment 49931 is needed for libgo to build, while the other are improving
the tests of libgo,go and gotools. Attachment 49934 if just a cosmetic change
of os_hurd.go.

Further changes are still needed to the Makefiles of libgo and gotools to
enable proper linking of libpthread and libdl. The dynamic linking of extra
libraries does not work automatically as it does on Linux systems.

Thanks!

  parent reply	other threads:[~2021-01-10 16:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01 18:33 [Bug go/98496] New: " doko at debian dot org
2021-01-01 23:16 ` [Bug go/98496] " ian at airs dot com
2021-01-02 17:49 ` doko at debian dot org
2021-01-02 18:09 ` svante.signell at gmail dot com
2021-01-05 10:55 ` rguenth at gcc dot gnu.org
2021-01-10 16:12 ` svante.signell at gmail dot com
2021-01-10 16:13 ` svante.signell at gmail dot com
2021-01-10 16:14 ` svante.signell at gmail dot com
2021-01-10 16:14 ` svante.signell at gmail dot com
2021-01-10 16:14 ` svante.signell at gmail dot com
2021-01-10 16:15 ` svante.signell at gmail dot com
2021-01-10 16:34 ` svante.signell at gmail dot com [this message]
2021-01-13 14:00 ` svante.signell at gmail dot com
2021-01-14 11:15 ` rguenth at gcc dot gnu.org
2021-01-14 17:22 ` ian at airs dot com
2021-01-14 17:57 ` cvs-commit at gcc dot gnu.org
2021-01-14 18:47 ` ian at airs dot com

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-98496-4-LXdcZp4DwS@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).