From: Linus Torvalds <torvalds@linux-foundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Will Deacon <will.deacon@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
mcroce@redhat.com, sbrivio@redhat.com,
David Miller <davem@davemloft.net>
Subject: Re: Build/qemu test results for v4.18-rc2
Date: Wed, 27 Jun 2018 08:27:47 -0700 [thread overview]
Message-ID: <CA+55aFx=UFQQi3c6MoA1jWaMf+-9vXC4pU56H_9dG3S8tbJdHA@mail.gmail.com> (raw)
In-Reply-To: <CA+55aFwZ1+HEYjo52OmX-aXEJ5iaGMakhJEZq1uY=CVKGdBSgg@mail.gmail.com>
On Tue, Jun 26, 2018 at 8:40 AM Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
> The problem on x86-64 cross-building to i386 is that the *compiler* is
> the same, but the flags are not, and the games the Makefile plays
> aren't sufficient. It plays with changing HOSTCC to CC in order to get
> he right target compiler, but since the difference between i386 and
> x86-64 is not the compiler but the "-m64" in the cflags, it doesn't
> actually do what it intended to do.
>
> We'll get it sorted, I think.
So right now the build fix is likely to be this:
https://patchwork.ozlabs.org/patch/935246/
but note that it's literally just a build fix, and for a i386
cross-compile it embeds the wrong binary so it won't actually run
correctly. For this whole "test the concept" stage that's fine.
Linus
next prev parent reply other threads:[~2018-06-27 15:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-24 16:25 Build/qemu test results for v4.18-rc2 Guenter Roeck
2018-06-25 7:17 ` Linus Torvalds
2018-06-25 8:40 ` Thomas Gleixner
2018-06-25 16:31 ` Guenter Roeck
2018-06-26 15:40 ` Linus Torvalds
2018-06-27 15:27 ` Linus Torvalds [this message]
2018-06-27 16:30 ` Guenter Roeck
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='CA+55aFx=UFQQi3c6MoA1jWaMf+-9vXC4pU56H_9dG3S8tbJdHA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mcroce@redhat.com \
--cc=sbrivio@redhat.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.