From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 557D23858D37; Tue, 3 Jan 2023 15:13:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 557D23858D37 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1672758836; bh=fYB4EF3jj7Vi3MVQ28bfjfWiSQOLS0a4WH2tKQlyNFs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=f5qs4k96oeVxj0d28UtIcM+6bhjN9Hx6yO4edpv6Y6D2Zi+rp+O57i1s/HnzcyuBR gmRmpAe4LX/j1+fJkaANXg3doL2+kSMwQpWLV1Pis9toYdU6UKFFfU+7+m+LAHKV0h OYxieofInb0V+vb9FCBpFk2retzswzgw/V7qOeqI= From: "adhemerval.zanella at linaro dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: build X-Bugzilla-Version: 2.36 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: adhemerval.zanella at linaro dot org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: DUPLICATE X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D29938 --- Comment #11 from Adhemerval Zanella --- (In reply to john.frankish from comment #10) > If you're referring to commit 4f4d7a13edfd2fdc57c9d76e1fd6d017fb47550c th= is > patch is already present in glibc-2.36.tar.xz >=20 > 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 t= he '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 --=20 You are receiving this mail because: You are on the CC list for the bug.=