From: Sam Ravnborg <sam@ravnborg.org>
To: Dan Kegel <dank@kegel.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: bringing back 'make symlinks'?
Date: Mon, 31 May 2004 22:16:23 +0200 [thread overview]
Message-ID: <20040531201623.GD8339@mars.ravnborg.org> (raw)
In-Reply-To: <40BB7C12.3040002@kegel.com>
On Mon, May 31, 2004 at 11:40:18AM -0700, Dan Kegel wrote:
> $ make ARCH=ppc prepare
> HOSTCC scripts/conmakehash
> HOSTCC scripts/kallsyms
> CC scripts/empty.o
> cc1: invalid option `multiple'
> cc1: invalid option `string'
> cc1: warning: unknown register name: r2
> make[1]: *** [scripts/empty.o] Error 1
>
> Whoops, bad luck. Let's try another:
OK - now I got the picture.
For 2.6 I'm not prepared to make a change that would allow what you need.
I know for 2.7 we will start to take a new approach with the kernel headers,
so I hope we do do it right there.
For 2.6 you have to live with the ugly workaround.
Sam
prev parent reply other threads:[~2004-05-31 20:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 15:45 bringing back 'make symlinks'? Dan Kegel
2004-05-25 21:43 ` Sam Ravnborg
2004-05-26 3:47 ` Dan Kegel
2004-05-30 10:55 ` Sam Ravnborg
2004-05-31 18:40 ` Dan Kegel
2004-05-31 20:16 ` Sam Ravnborg [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=20040531201623.GD8339@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=dank@kegel.com \
--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