public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/28554] Undefined generate-md5 Date: Wed, 10 Nov 2021 12:55:27 +0000 [thread overview] Message-ID: <bug-28554-131-BUCOeph25w@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28554-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28554 --- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=0bd356df1afb0591470499813d4ebae9bcedd6a6 commit 0bd356df1afb0591470499813d4ebae9bcedd6a6 Author: H.J. Lu <hjl.tools@gmail.com> Date: Sat Nov 6 06:46:43 2021 -0700 Remove the unused +mkdep/+make-deps/s-proto.S/s-proto-cancel.S Since commit d73f5331ce5370ca5a879229e3842f5de98689cd Author: Roland McGrath <roland@gnu.org> Date: Fri May 2 02:20:45 2003 +0000 2003-05-01 Roland McGrath <roland@redhat.com> dependency is generated by passing -MD -MF to compiler. Remove the unused +mkdep, +make-deps, s-proto.S and s-proto-cancel.S. This fixes BZ #28554. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-11-10 12:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-06 3:22 [Bug build/28554] New: " hjl.tools at gmail dot com 2021-11-06 8:04 ` [Bug build/28554] " schwab@linux-m68k.org 2021-11-06 8:11 ` schwab@linux-m68k.org 2021-11-06 13:22 ` cvs-commit at gcc dot gnu.org 2021-11-06 13:23 ` hjl.tools at gmail dot com 2021-11-06 13:36 ` schwab@linux-m68k.org 2021-11-10 12:55 ` cvs-commit at gcc dot gnu.org [this message] 2021-11-10 13:31 ` hjl.tools at gmail 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-28554-131-BUCOeph25w@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: linkBe 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).