[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOFdcFP=z4Tn-Zt6cuujGABWPDQrCy4=LzXHndB5rzFnEdyvXw@mail.gmail.com>
Date: Wed, 8 Oct 2014 15:44:37 -0400
From: Peter Foley <pefoley2@...oley.com>
To: Andy Lutomirski <luto@...capital.net>
Cc: Josh Boyer <jwboyer@...oraproject.org>,
Randy Dunlap <rdunlap@...radead.org>,
Jiri Kosina <jkosina@...e.cz>,
"H. Peter Anvin" <hpa@...or.com>,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: vdso_standalone_test_x86.c build failure on Linus' tree
On Wed, Oct 8, 2014 at 3:16 PM, Andy Lutomirski <luto@...capital.net> wrote:
> It should build and work on 32-bit.
>
> Except that the makefile is totally bogus. vdso_standalone_test isn't
> a hostprog at all. It's a target prog. But kbuild doesn't understand
> that, so I have no idea what, if anything, that makefile is supposed
> to do.
The idea is to increase build testing for targets in Documentation,
but I didn't really consider cross-compiling those targets.
>
> I would argue that the whole documentation build system should be
> fixed to cross-compile or should just be disabled for cross-builds if
> glibc isn't available.
It might make sense to just completely disable CONFIG_BUILD_DOCSRC if
we're cross-compiling.
>
> FWIW, the comment at the top of vdso_standalone_test_x86.c documents
> *exactly* how to build it, and it works if you build it like that.
So, it looks like 32bit needs -lgcc_s
I'll whip up a patch to add that.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists