public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "piotr.oniszczuk at gmail 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: Sat, 09 May 2020 17:30:04 +0000 [thread overview]
Message-ID: <bug-25920-131-v3fIwucnlo@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 #13 from Piotr Oniszczuk <piotr.oniszczuk at gmail dot com> ---
@joseph
May thx for hinting me about valid subset of GCC multi-libs for GNU/Linux.
I was missing this information.
I looked a bit inside of glibc building infra and in my case following patch
allows to successfully cross-compile for armv7-a targets:
[https://github.com/warpme/minimyth2/blob/master/script/devel/glibc/files/glibc-2.31-fix-building-arm-thumb.patch][1].
With above patch I tested cross-compilation for following list of targets where
glibc cross-compiles with success:
-marm -march=armv5te+fp -mfloat-abi=softfp
-mthumb -march=armv7-a -mfloat-abi=soft
-mthumb -march=armv7-a+fp -mfloat-abi=softfp
-mthumb -march=armv7-a+simd -mfloat-abi=softfp
-mthumb -march=armv7ve+simd -mfloat-abi=softfp
Will above prove-of-concept be enough to develop proper fix?
(probably it should go also to configure.ac)...
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-09 17:30 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 [this message]
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-v3fIwucnlo@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).