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: Tue, 05 May 2020 21:16:57 +0000	[thread overview]
Message-ID: <bug-25920-131-FHg2Mrb3Gq@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 #10 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 5 May 2020, piotr.oniszczuk at gmail dot com via Glibc-bugs wrote:

> https://sourceware.org/bugzilla/show_bug.cgi?id=25920
> 
> --- Comment #9 from Piotr Oniszczuk <piotr.oniszczuk at gmail dot com> ---
> (In reply to joseph@codesourcery.com from comment #8)
> > On Tue, 5 May 2020, piotr.oniszczuk at gmail dot com via Glibc-bugs wrote:
> > 
> > > Ok. So when you are writing: "Options wanted for all languages should go in CC"
> > > - what exactly do you mean in terms of configure supplied params?
> > 
> > CC="<target>-gcc -mthumb -march=armv7 -mfloat-abi=soft", for example.
> 
> Ah yes! I already tries exactly this and this makes glibc build failing quite
> early at assembling with assembler :-(

So look at that failure, because putting the options in CC is the right 
way to build glibc with custom compiler options.

One other thing to note: you have to use armv7-a, not armv7; v7-R and v7-M 
aren't supported for normal GNU/Linux (with MMU) userspace.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-05-05 21:16 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 [this message]
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

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-FHg2Mrb3Gq@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: link
Be 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).