public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "h0tc0d3 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/28881] Glibc 32-bit build randomly fails with gcc: error: unrecognized command-line option ‘-static-libgcc’
Date: Wed, 16 Feb 2022 14:20:17 +0000	[thread overview]
Message-ID: <bug-28881-131-rI2t2j9Y0D@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28881-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=28881

--- Comment #3 from Grigory <h0tc0d3 at gmail dot com> ---
(In reply to Adhemerval Zanella from comment #1)
> This really seems to be an issue with toolchain you are using to build
> glibc, we do require the gcc to support -static-libgcc (which should be the
> default).

gcc was build with static libgcc support. This problem occurs intermittently,
and I have to rollback to old versions of glibc, gcc, binutils, libtool and
build everything from the beginning. It is also not clear from what and when it
begins to appear. The only thing is that this only occurs with 32 bit versions
of glibc. Also gcc remained the same, but at one moment this error occurs.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-02-16 14:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-11  8:00 [Bug build/28881] New: " h0tc0d3 at gmail dot com
2022-02-16 13:12 ` [Bug build/28881] " adhemerval.zanella at linaro dot org
2022-02-16 14:17 ` schwab@linux-m68k.org
2022-02-16 14:20 ` h0tc0d3 at gmail dot com [this message]
2022-02-22  3:49 ` sam at gentoo dot org
2022-02-22 15:47 ` adhemerval.zanella at linaro dot org
2022-02-22 18:55 ` h0tc0d3 at gmail dot com
2022-02-22 19:11 ` adhemerval.zanella at linaro dot org
2022-02-22 19:27 ` h0tc0d3 at gmail dot com
2022-02-22 20:08 ` adhemerval.zanella at linaro dot org
2024-05-07 17:39 ` adhemerval.zanella at linaro 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=bug-28881-131-rI2t2j9Y0D@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).