From: Mattias Schlenker <ms@mattiasschlenker.de>
To: linux-kernel@vger.kernel.org
Subject: Cross compile broken - 3.17.3 vs. 3.17.4?
Date: Tue, 25 Nov 2014 22:15:35 +0100 [thread overview]
Message-ID: <5474F177.9030404@mattiasschlenker.de> (raw)
Hello everyone,
when cross compiling with a rather generic x86_64-linux-gnu toolchain I
run into the problem that "make bzImage" fails. It seems vmlinux binary
gets run through the hosts objdump and not the $(CROSS_COMPILE)objdump
as it was in 3.17.3.
I am not accustomed enough to kernel build habits to immediately spot
the change that lead to this failed compile (178 files were changed
between 3.17.3 and 3.17.4). But if you want, I am gonna provide you with
a shell script that is able to set up the needed toolchain and succeed
with 3.17.3 and fail with 3.17.4. Given my current workload this will
take around 48 hours.
Regards,
Mattias
--
Mattias Schlenker - Freier IT-Fachredakteur und -autor
redaktion@mattiasschlenker.de
Mattias Schlenker - IT-Consulting, Softwareentwicklung
consulting@mattiasschlenker.de
Address__ August-Bebel-Str. 74 - D-04275 LEIPZIG - GERMANY
Call me! (VoIP)__________________________ +49 341 39290767
Call me! (PoTS + Faksimile)______________ +49 341 30393578
Call me if it's urgent! (Mobile)_________ +49 163 6953657
VATIN_________________________________________ DE240998538
Fork me!____________________ https://github.com/mschlenker
Website.__________________ http://www.mattiasschlenker.de/
My books!___________ http://www.arduino-hausautomation.de/
Google+_________ https://www.google.com/+MattiasSchlenker1
Xing_______ https://www.xing.com/profile/Mattias_Schlenker
next reply other threads:[~2014-11-25 21:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 21:15 Mattias Schlenker [this message]
2014-11-25 22:01 ` Cross compile broken - 3.17.3 vs. 3.17.4? Borislav Petkov
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=5474F177.9030404@mattiasschlenker.de \
--to=ms@mattiasschlenker.de \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox