public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/28554] New: Undefined generate-md5 Date: Sat, 06 Nov 2021 03:22:00 +0000 [thread overview] Message-ID: <bug-28554-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28554 Bug ID: 28554 Summary: Undefined generate-md5 Product: glibc Version: 2.35 Status: NEW Severity: normal Priority: P2 Component: build Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: carlos at redhat dot com Target Milestone: --- Makerules has define +make-deps $(make-target-directory) $(+mkdep) $< $(if $(filter %.c,$<),$(CFLAGS)) \ $(CPPFLAGS) $($(patsubst .%,%,$(suffix $(<F)))-CPPFLAGS) | sed -e\ 's,$(subst .,\.,$(@F:.d=.o)),$(foreach o,$(all-object-suffixes),$(@:.d=$o)) $@,' \ $(sed-remove-objpfx) $(sed-remove-dotdot) > $(@:.d=.T) mv -f $(@:.d=.T) $@ $(generate-md5) endef But generate-md5 is undefined and removed by commit 362f5ae2c1641904ccf489742a4a3440e7e10814 Author: Roland McGrath <roland@gnu.org> Date: Fri May 2 02:21:25 2003 +0000 * sysdeps/generic/bp-thunks.h: Protect includes with [!__ASSEMBLER__]. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-11-06 3:22 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-06 3:22 hjl.tools at gmail dot com [this message] 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 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@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).