From: Segher Boessenkool <segher@kernel.crashing.org>
To: Mathieu Malaterre <malat@debian.org>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: powerpc-linux-gnu-ld: cannot open linker script file arch/powerpc/boot/zImage.coff.lds: No such file or directory
Date: Fri, 9 Feb 2018 14:56:58 -0600 [thread overview]
Message-ID: <20180209205658.GW21977@gate.crashing.org> (raw)
In-Reply-To: <CA+7wUsybiroxTP8tuvANuAKYKQjNQ8ayNtQDL=1jBV3uZJe-ow@mail.gmail.com>
On Fri, Feb 09, 2018 at 04:55:20PM +0100, Mathieu Malaterre wrote:
> >> $ make O=ppc6xx ARCH=powerpc ppc6xx_defconfig
> >> $ make O=ppc6xx ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- zImage
> >
> > Works fine for me (exact same arch and defconfig). Two differences:
> > 1) I also set CROSS_COMPILE during the config step;
> > 2) I don't build zImage, just the default (but manual "make zImage"
> > afterwards works fine).
>
> Could you run command (2) a second time on your system.
That works fine, also with -j$BIG .
> $ make O=ppc6xx ARCH=powerpc ppc6xx_defconfig
> $ make O=ppc6xx ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu- zImage
> -> ok so far
> $ make O=ppc6xx -j4 ARCH=powerpc CROSS_COMPILE=powerpc-linux-gnu-
Ah. I configure with O=, but then cd to that dir and build without O= .
Also not in a subdir of the kernel source tree.
make ARCH=$ARCH CROSS_COMPILE=$TARGET- -C $KERNEL_SRC O=$PWD $DEFCONFIG
make ARCH=$ARCH CROSS_COMPILE=$TARGET- $MAKEOPTS
(everything run in the build dir).
Segher
prev parent reply other threads:[~2018-02-09 20:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 11:52 powerpc-linux-gnu-ld: cannot open linker script file arch/powerpc/boot/zImage.coff.lds: No such file or directory Mathieu Malaterre
2018-02-09 14:48 ` Segher Boessenkool
2018-02-09 15:55 ` Mathieu Malaterre
2018-02-09 16:23 ` Mathieu Malaterre
2018-02-09 20:56 ` Segher Boessenkool [this message]
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=20180209205658.GW21977@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=malat@debian.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.