From: Petr Ovtchenkov <ptr@void-ptr.info>
To: "Érico Nogueira" <ericonr@disroot.org>
Cc: <elfutils-devel@sourceware.org>
Subject: Re: [PATCH 1/1] support cross compilation
Date: Wed, 26 May 2021 16:58:50 +0300 [thread overview]
Message-ID: <20210526135850.1b967be8@void-ptr.info> (raw)
In-Reply-To: <CBN79N4GUAX1.W2S2DW4JUAJU@mussels>
On Wed, 26 May 2021 10:09:31 -0300
Érico Nogueira <ericonr@disroot.org> wrote:
> Hi! Are you sure this is necessary? In Void Linux, we cross compile
> elfutils for arm and aarch64 without any issue, and I have built it a
> few times for powerpc as well.
>
Hello!
Yes, I am sure. I do not know about you process (check, that you really
cross, not run via qemu or like). Build process _run_ i386_gendis to
generate headers:
<snip>
if MAINTAINER_MODE
noinst_HEADERS += memory-access.h i386_parse.h i386_data.h
noinst_PROGRAMS = i386_gendis$(EXEEXT)
$(srcdir)/%_dis.h: %_defs i386_gendis$(EXEEXT)
$(AM_V_GEN)./i386_gendis$(EXEEXT) $< > $@T <================
$(AM_V_at)mv -f $@T $@
else
$(srcdir)/%_dis.h:
@echo '*** missing $@; configure with --enable-maintainer-mode'
@false
endif
</snip>
> > +if CROSS
> > +i386_gendis_LINK = ${CC_FOR_BUILD} ${LDFLAGS} -o $@
> > +
> > +$(i386_gendis_OBJECTS): CC=${CC_FOR_BUILD}
> > +endif
>
> Isn't this hardcoding an assumption that the build machine is x86?
I think no. But this question is for original author:
commit 3cbdd387c752999255aea91600b5cfdefbeac7d0
Author: Ulrich Drepper <drepper@redhat.com>
Date: Wed Jan 2 17:44:39 2008 +0000
propagate from branch 'com.redhat.elfutils.disasm' (head
d15b4eb794e81e477f9896fe82a74cb5ecf4514c) to branch
'com.redhat.elfutils' (head
eaacbf01f8cc89d043ec6eca9b5e35cb5c4cde06)
;)
next prev parent reply other threads:[~2021-05-26 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210526073239.21270-1-ptr@void-ptr.info>
2021-05-26 7:32 ` Petr Ovtchenkov
2021-05-26 13:09 ` Érico Nogueira
2021-05-26 13:58 ` Petr Ovtchenkov [this message]
2021-05-26 15:41 ` Érico Nogueira
2021-05-26 16:34 ` Petr Ovtchenkov
2022-12-21 12:26 ` Mark Wielaard
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=20210526135850.1b967be8@void-ptr.info \
--to=ptr@void-ptr.info \
--cc=elfutils-devel@sourceware.org \
--cc=ericonr@disroot.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).