From: Adrian Bunk <bunk@stusta.de>
To: sam@ravnborg.org
Cc: starvik@axis.com, dev-etrax@axis.com, linux-kernel@vger.kernel.org
Subject: cris: asm-offsets related build failure
Date: Thu, 19 Jan 2006 01:18:52 +0100 [thread overview]
Message-ID: <20060119001852.GO19398@stusta.de> (raw)
Hi Sam,
the following build failure is present on the cris architecture:
<-- snip -->
...
make[1]: *** No rule to make target `arch/cris/kernel/asm-offsets.c',
needed by `arch/cris/kernel/asm-offsets.s'. Stop.
make: *** [prepare0] Error 2
<-- snip -->
The problem seems to be that the cris port has two different files for
this purpose:
arch/cris/arch-v10/kernel/asm-offsets.c
arch/cris/arch-v32/kernel/asm-offsets.c
What is the best way to handle this?
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2006-01-19 0:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 0:18 Adrian Bunk [this message]
2006-01-19 8:57 ` cris: asm-offsets related build failure Al Viro
2006-01-19 16:34 ` Sam Ravnborg
2006-01-19 19:03 ` Al Viro
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=20060119001852.GO19398@stusta.de \
--to=bunk@stusta.de \
--cc=dev-etrax@axis.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=starvik@axis.com \
/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