All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 26 Jun 2018 08:40:37 -0700	[thread overview]
Message-ID: <CA+55aFwZ1+HEYjo52OmX-aXEJ5iaGMakhJEZq1uY=CVKGdBSgg@mail.gmail.com> (raw)
In-Reply-To: <20180625163147.GA7112@roeck-us.net>

On Mon, Jun 25, 2018 at 9:31 AM Guenter Roeck <linux@roeck-us.net> wrote:
>
> Yes, looks like they tried again with c24fb5e68ebf ("bpfilter: fix user
> mode helper cross compilation"), but it still doesn't work.

That was a different issue - an actual cross-build environment.

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. The problem is that the current Makefile
infrastructure doesn't have any support for building a stand-alone
binary for the target, which is why the code plays games with HOSTCC
(to use the infrastructure that does binaries for the host, but using
the target compiler).

So it's all a bit hacky right now, and the hacks come back and bite us
for the x86-64/i386 case.

               Linus

  reply	other threads:[~2018-06-26 15:40 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 [this message]
2018-06-27 15:27       ` Linus Torvalds
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+55aFwZ1+HEYjo52OmX-aXEJ5iaGMakhJEZq1uY=CVKGdBSgg@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.