From: Maxime Devos <maximedevos@telenet.be>
To: 49113@debbugs.gnu.org
Subject: bug#49113: aarch64-linux-gnu cross-compiler fails to build [core-updates]
Date: Sun, 20 Jun 2021 14:17:14 +0200 [thread overview]
Message-ID: <b538bb6490774706396b9931bff6630e48814162.camel@telenet.be> (raw)
In-Reply-To: <f108d7df9cede373d38868c384fa1c6bdf69d09f.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
About 0x00000150 vs 0x00000011:
0x00000150 means D_PAGED | DYNAMIC | HAS_SYM
and 0x00000011 means HAS_SYMS | HAS_RELOC
Here, (from bfd/bfd-in2.h in binutils sources)
/* BFD is dynamically paged (this is like an a.out ZMAGIC file) (the
linker sets this by default, but clears it for -r or -n or -N). */
#define D_PAGED
/* BFD contains relocation entries. */
#define HAS_RELOC 0x1
/* BFD is a dynamic object. */
#define DYNAMIC 0x40
I believe this is a dead end.
Writing "int r(void){return 0;}" to a.c
and running "gcc -c -shared -fpic a.c" on my x86_64
and "objdump -x a.o", I see
architecture: i386:x86-64, flags 0x00000011:
HAS_RELOC, HAS_SYMS
start address 0x0000000000000000
(The flags are identical)
Greetings,
Maxime.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2021-06-20 12:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 8:41 bug#48913: i686-linux-gnu cross-compiler cannot find libgcc_s [core-updates] Maxime Devos
2021-06-08 14:23 ` Maxime Devos
2021-06-08 15:25 ` Maxime Devos
2021-06-18 9:33 ` Ludovic Courtès
2021-06-19 7:37 ` Maxime Devos
2021-06-19 10:05 ` bug#49113: aarch64-linux-gnu cross-compiler fails to build [core-updates] Maxime Devos
2021-06-20 12:17 ` Maxime Devos [this message]
2021-07-03 16:12 ` Ludovic Courtès
2021-07-04 20:33 ` Ludovic Courtès
2021-06-19 11:05 ` bug#48913: i686-linux-gnu cross-compiler cannot find libgcc_s [core-updates] Maxime Devos
2021-06-19 11:59 ` Maxime Devos
2021-06-18 9:32 ` Ludovic Courtès
2021-07-03 13:40 ` Maxime Devos
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b538bb6490774706396b9931bff6630e48814162.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=49113@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).