public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29938] glibc-2.36 fails to build with Os with undefined reference to strcpy
Date: Thu, 29 Dec 2022 12:59:23 +0000 [thread overview]
Message-ID: <bug-29938-131-UV0Wmk1hOu@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29938-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29938
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adhemerval.zanella at linaro dot o
| |rg
--- Comment #6 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
I back(In reply to john.frankish from comment #5)
> Thanks - that appears to have solved the problem of compiling for i486 with
> -Os.
>
> Note that the glibc-2.36 tarball already contains the file added by commit
> 9dc4e29f630c6ef8299120b275e503321dc0c8c7
>
> I'll check building for x86_64 with -Os in a day or two.
I just backported the required patch to build glibc with -Os for x86 on 2.36
and I also send some fixes for upstream to build for -Os/-O1 on all targets
[1].
[1] https://patchwork.sourceware.org/project/glibc/list/?series=15572
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-12-29 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 12:52 [Bug build/29938] New: " john.frankish at outlook dot com
2022-12-24 1:09 ` [Bug build/29938] " goldstein.w.n at gmail dot com
2022-12-25 9:26 ` john.frankish at outlook dot com
2022-12-26 20:23 ` goldstein.w.n at gmail dot com
2022-12-27 14:17 ` john.frankish at outlook dot com
2022-12-27 14:18 ` john.frankish at outlook dot com
2022-12-29 12:59 ` adhemerval.zanella at linaro dot org [this message]
2022-12-29 13:00 ` adhemerval.zanella at linaro dot org
2022-12-31 11:35 ` john.frankish at outlook dot com
2022-12-31 13:32 ` adhemerval.zanella at linaro dot org
2022-12-31 15:50 ` john.frankish at outlook dot com
2023-01-03 15:13 ` adhemerval.zanella at linaro dot org
2023-01-03 16:28 ` john.frankish at outlook 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-29938-131-UV0Wmk1hOu@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).