public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/25920] cross-compiling for ARM target fails at linking ld.so.new if THUMB used Date: Mon, 11 May 2020 16:54:08 +0000 [thread overview] Message-ID: <bug-25920-131-DnOgQAeq4x@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25920-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25920 --- Comment #14 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- If you wish to argue for all CFLAGS going in ASFLAGS (or e.g. all -m options), the right place to change would be the code in Makeconfig that instead just puts -g and -fdebug-prefix-map options from CFLAGS in ASFLAGS. Note that at that point CFLAGS contains many options that are specific to C compilation (such as -std=gnu11, for example), so it might be necessary to save a copy of relevant flags earlier in Makeconfig / refactor how those variables are built up. Any such proposal would best be sent to libc-alpha rather than in the discussion of a bug report, and would need to include an analysis of the history of why ASFLAGS only includes certain CFLAGS settings at present. It's quite likely the reasons are historical and it would be safe for nearly all options in CFLAGS to be passed in ASFLAGS, but we need to try to understand what the reasons were and what might break first. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2020-05-11 16:54 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-04 18:05 [Bug libc/25920] New: " piotr.oniszczuk at gmail dot com 2020-05-04 18:21 ` [Bug libc/25920] " joseph at codesourcery dot com 2020-05-04 19:21 ` piotr.oniszczuk at gmail dot com 2020-05-04 19:37 ` joseph at codesourcery dot com 2020-05-04 20:31 ` piotr.oniszczuk at gmail dot com 2020-05-04 20:41 ` piotr.oniszczuk at gmail dot com 2020-05-05 0:10 ` joseph at codesourcery dot com 2020-05-05 6:44 ` piotr.oniszczuk at gmail dot com 2020-05-05 19:48 ` joseph at codesourcery dot com 2020-05-05 19:54 ` piotr.oniszczuk at gmail dot com 2020-05-05 21:16 ` joseph at codesourcery dot com 2020-05-07 11:20 ` piotr.oniszczuk at gmail dot com 2020-05-07 20:33 ` joseph at codesourcery dot com 2020-05-09 17:30 ` piotr.oniszczuk at gmail dot com 2020-05-11 16:54 ` joseph at codesourcery dot com [this message]
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-25920-131-DnOgQAeq4x@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).