From: Jesper Nilsson <Jesper.Nilsson@axis.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: linux-next: cris build failure
Date: Tue, 21 Apr 2009 08:06:23 +0200 [thread overview]
Message-ID: <20090421060623.GP21811@axis.com> (raw)
In-Reply-To: <20090421135843.0993cb89.sfr@canb.auug.org.au>
On Tue, Apr 21, 2009 at 05:58:43AM +0200, Stephen Rothwell wrote:
> Hi Jesper,
>
> Having figured out that I needed a crisv32 compiler (not a cris one) to
> build the kernel, I now get this error:
>
> LD arch/cris/arch-v32/boot/rescue/rescue.o
> /bin/sh: gcc-cris: command not found
> make[3]: *** [arch/cris/arch-v32/boot/rescue/rescue.o] Error 127
>
> arch/cris/arch-v32/boot/rescue/Makefile has an explicit reference to
> gcc-cris. Surely there is some better way specify this. I created a
> symlink for gcc-cris to my crisv32 cross compiler and that allowed the
> kernel to finish building, but that is not a very nice solution.
Yes, you are quite correct. I have been working (albeit slowly)
at removing all non-standard commands and port specific symlinks,
and I have a patch that folds the boot code for both v32 and v10
into the same directory. That patch also removes the gcc-cris usage.
I'll push that out to my for-next branch asap.
/^JN - Jesper Nilsson
--
Jesper Nilsson -- jesper.nilsson@axis.com
next prev parent reply other threads:[~2009-04-21 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-21 3:58 linux-next: cris build failure Stephen Rothwell
2009-04-21 6:06 ` Jesper Nilsson [this message]
2009-04-21 6:22 ` Stephen Rothwell
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=20090421060623.GP21811@axis.com \
--to=jesper.nilsson@axis.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.