public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Fangrui Song <maskray@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/google/grte/v5-2.27/master] Makeconfig: Update clang_rt.crtbegin.o filename Date: Tue, 3 May 2022 04:01:52 +0000 (GMT) [thread overview] Message-ID: <20220503040152.904773857418@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=20f6c924222f2677d9a53fa3b6c1ea76a1341840 commit 20f6c924222f2677d9a53fa3b6c1ea76a1341840 Author: Fangrui Song <maskray@google.com> Date: Mon May 2 21:01:43 2022 -0700 Makeconfig: Update clang_rt.crtbegin.o filename Diff: --- Makeconfig | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/Makeconfig b/Makeconfig index c1a395a105..fea770fec4 100644 --- a/Makeconfig +++ b/Makeconfig @@ -662,11 +662,10 @@ endif +preinit = $(addprefix $(csu-objpfx),crti.o) +postinit = $(addprefix $(csu-objpfx),crtn.o) ifeq ($(with-clang),yes) -# With clang, use the crt*.o files from llvm's compiler-rt package. -# The files normally have an architecture name appended, in case of -# variants (32/64, le/be etc) installed in the same directory. -+prector = `$(CC) $(sysdep-LDFLAGS) --print-file-name=clang_rt.crtbegin-$(config-machine).o` -+postctor = `$(CC) $(sysdep-LDFLAGS) --print-file-name=clang_rt.crtend-$(config-machine).o` +# With clang, use the clang_rt.crt*.o files from the compiler-rt package +# in a LLVM_ENABLE_RUNTIMES build. ++prector = `$(CC) $(sysdep-LDFLAGS) --print-file-name=clang_rt.crtbegin.o` ++postctor = `$(CC) $(sysdep-LDFLAGS) --print-file-name=clang_rt.crtend.o` else +prector = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtbegin.o` +postctor = `$(CC) $(sysdep-LDFLAGS) --print-file-name=crtend.o`
reply other threads:[~2022-05-03 4:01 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220503040152.904773857418@sourceware.org \ --to=maskray@sourceware.org \ --cc=glibc-cvs@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).