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: Tue, 03 Jan 2023 15:13:55 +0000 [thread overview]
Message-ID: <bug-29938-131-3Bk6RYT22w@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29938-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29938
--- Comment #11 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to john.frankish from comment #10)
> If you're referring to commit 4f4d7a13edfd2fdc57c9d76e1fd6d017fb47550c this
> patch is already present in glibc-2.36.tar.xz
>
> If you're referring to the entire branch [1], please excuse my ignorance,
> but how do I clone branch [1] from glibc git?
I mean the git branch for 2.36, since glibc usually does not release minor
versions for the source packages release. And the process is described in the
'get started' pane [1]:
$ git clone https://sourceware.org/git/glibc.git
$ cd glibc
$ git checkout release/2.36/master
You can also accomplish the same with one command:
$ git clone -b release/2.36/master https://sourceware.org/git/glibc.git
[1] https://www.gnu.org/software/libc/started.html
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-03 15:13 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
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 [this message]
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-3Bk6RYT22w@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).