From: Chuck Ebbert <cebbert.lkml@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Josh Boyer <jwboyer@fedoraproject.org>,
Peter Foley <pefoley2@pefoley.com>,
Randy Dunlap <rdunlap@infradead.org>,
Jiri Kosina <jkosina@suse.cz>, "H. Peter Anvin" <hpa@zytor.com>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: vdso_standalone_test_x86.c build failure on Linus' tree
Date: Wed, 8 Oct 2014 15:46:59 -0500 [thread overview]
Message-ID: <20141008154659.31f46436@as> (raw)
In-Reply-To: <CALCETrUDkHH-FLwq9ZJ0wFeOkQVWUjTh-cJPL4Jq28sHCqhfFA@mail.gmail.com>
On Wed, 8 Oct 2014 12:16:11 -0700
Andy Lutomirski <luto@amacapital.net> wrote:
> On Wed, Oct 8, 2014 at 11:52 AM, Josh Boyer <jwboyer@fedoraproject.org> wrote:
> > I'm seeing the following build failure on a 32-bit x86 build in Fedora
> > based on Linux v3.17-2860-gef0625b70dac:
> >
> > Documentation/vDSO/vdso_standalone_test_x86.o: In function `to_base10':
> > vdso_standalone_test_x86.c:(.text+0xcc): undefined reference to `__umoddi3'
> > vdso_standalone_test_x86.c:(.text+0xea): undefined reference to `__udivdi3'
> > collect2: error: ld returned 1 exit status
> > scripts/Makefile.host:100: recipe for target
> > 'Documentation/vDSO/vdso_standalone_test_x86' failed
> > make[2]: *** [Documentation/vDSO/vdso_standalone_test_x86] Error 1
> > scripts/Makefile.build:404: recipe for target 'Documentation/vDSO' failed
> > make[1]: *** [Documentation/vDSO] Error 2
> > make[1]: *** Waiting for unfinished jobs....
> > Makefile:922: recipe for target 'vmlinux' failed
> > make: *** [vmlinux] Error 2
> >
> 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.
Heh, I was wondering why I got a 64-bit program with ARCH=i386
> 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.
>
Fedora doesn't cross-compile i686 builds because of problems like
this. It sets up an i386 chroot and runs all native tools inside of
it.
next prev parent reply other threads:[~2014-10-08 20:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 18:52 vdso_standalone_test_x86.c build failure on Linus' tree Josh Boyer
2014-10-08 19:16 ` Andy Lutomirski
2014-10-08 19:44 ` Peter Foley
2014-10-08 20:46 ` Chuck Ebbert [this message]
2014-10-08 20:50 ` Andy Lutomirski
2014-10-08 20:55 ` H. Peter Anvin
2014-10-08 21:09 ` Chuck Ebbert
2014-10-08 21:21 ` H. Peter Anvin
2014-10-08 23:08 ` Chuck Ebbert
2014-10-08 23:11 ` Peter Foley
2014-10-08 23:18 ` Andy Lutomirski
2014-10-09 0:18 ` Randy Dunlap
2014-10-08 21:21 ` Josh Boyer
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=20141008154659.31f46436@as \
--to=cebbert.lkml@gmail.com \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=pefoley2@pefoley.com \
--cc=rdunlap@infradead.org \
--cc=torvalds@linux-foundation.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 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.