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: Tue, 22 Feb 2022 18:55:20 +0000	[thread overview]
Message-ID: <bug-28881-131-Q88sQN7Cyl@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 #5 from Grigory <h0tc0d3 at gmail dot com> ---
(In reply to Adhemerval Zanella from comment #4)
> Are you still seeing build failures after the fix for bug 28895?

Yep, I use patch for this bug. Thank you! He apparently decided performance
degradation after glibc 2.34. But not solved -static-libgcc bug in 32-bit
glibc. I found if I got -static-libgcc bug then this can be solved with
compilation and installation 64-bit version glibc, and then will compile 32-bit
version. My build script build 64-bit and 32-bit version at once and some times
compilation of 32-bit version fails with -static-libgcc error.

My build script:
https://github.com/h0tc0d3/arch-packages/blob/master/glibc/PKGBUILD

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

  parent reply	other threads:[~2022-02-22 18:55 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
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 [this message]
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-Q88sQN7Cyl@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).