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/31385] New: sort-makefile-lines.py doesn't check variable with _ Date: Thu, 15 Feb 2024 11:13:55 +0000 [thread overview] Message-ID: <bug-31385-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31385 Bug ID: 31385 Summary: sort-makefile-lines.py doesn't check variable with _ Product: glibc Version: 2.40 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: --- There are many Makefile variable names with _: sysdeps/aarch64/Makefile:sysdep_headers += sys/ifunc.h sysdeps/aarch64/Makefile:sysdep_routines += \ sysdeps/aarch64/Makefile:sysdep_malloc_debug_routines = __mtag_tag_zero_region __mtag_tag_region ... But sort-makefile-lines.py doesn't include _ in # Build a list of all start markers (tuple includes name). startmarks = [] for i in range(len(lines)): # Look for things like "var = \", "var := \" or "var += \" # to start the sorted list. var = re.search(r'^([a-zA-Z0-9-]*) [\+:]?\= \\$', lines[i]) -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-02-15 11:13 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-15 11:13 hjl.tools at gmail dot com [this message] 2024-02-15 11:19 ` [Bug build/31385] " hjl.tools at gmail dot com 2024-02-15 11:20 ` [Bug build/31385] sort-makefile-lines.py doesn't check variable with _ nor with "^# variable" hjl.tools at gmail dot com 2024-02-15 18:43 ` cvs-commit at gcc dot gnu.org 2024-02-15 23:07 ` 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-31385-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).