From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Makefile: add check of binaries architecture
Date: Tue, 30 May 2017 23:44:22 +0200 [thread overview]
Message-ID: <20170530234422.23923aef@free-electrons.com> (raw)
In-Reply-To: <CABLXdK_3=64R13wD+_WN7DceLiLtwEy2Hg8Rtqdd_p6Xu4tXEg@mail.gmail.com>
Hello,
On Tue, 30 May 2017 23:35:35 +0200, Ricardo Herrero wrote:
> I have been compiling some packages both ARM and linux-x86_64 archs
> together until I have tested with Buildroot 2017.05_rc2. It adds a check
> for proper binaries during build stage. But I need to build both archs. So
> I need to know if there is a way to bypass this check or if I can do
> something else. My problem is that I need a package to compile both x86_64
> and arm in order to compile another package both in x86_64. So I cannot
> remove x86_64 folders right after build, I need all of them until install
> phase.
Can you explain your use case in more detail? I don't understand why
you are mixing ARM and x86-64 binaries in the target folder. So before
proposing a solution to workaround the architecture check, I'd like to
make sure that there isn't a deeper problem in the approach you're
using to build those packages.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-05-30 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 21:35 [Buildroot] Makefile: add check of binaries architecture Ricardo Herrero
2017-05-30 21:44 ` Thomas Petazzoni [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=20170530234422.23923aef@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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