From: Helge Deller <deller@gmx.de>
To: Kyle McMartin <kyle@infradead.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: define SRCARCH=parisc for parisc64 builds
Date: Sat, 14 Mar 2009 21:47:06 +0100 [thread overview]
Message-ID: <49BC17CA.9020004@gmx.de> (raw)
In-Reply-To: <20090313045537.GC3907@bombadil.infradead.org>
Kyle McMartin wrote:
> On Mon, Feb 02, 2009 at 12:24:01AM +0100, Helge Deller wrote:
>> The parisc64 target (HP PARISC, 64bit kernel) is similar to the spar=
c64 or=20
>> m68knommu targets, as it shares all sources for 32- and 64-bit in on=
e single
>> source path which is arch/parisc/.
>> This patch now allows one to use ARCH=3Dparisc64 and just directly b=
uild the
>> 64bit kernel without creating symlinks in arch/ and include/asm-* ma=
nually
>> the same way as it's done for sparc64 and m68knommu.
>>
>=20
> I'm going to drop this patch, powerpc and mips don't do it,=20
they maybe don't need it ?
> and 'parisc64' hasn't been valid as $ARCH since v2.3 or something equ=
ally
> ancient, so I can't see any point in it.
=C4h ?
And how do you build a 64bit parisc kernel then ?
Helge
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-03-14 20:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-01 23:24 [PATCH] parisc: define SRCARCH=parisc for parisc64 builds Helge Deller
2009-03-13 4:55 ` Kyle McMartin
2009-03-14 20:47 ` Helge Deller [this message]
2009-03-14 20:49 ` Kyle McMartin
2009-03-14 20:56 ` Helge Deller
2009-03-14 21:06 ` Kyle McMartin
2009-03-14 21:25 ` Helge Deller
2009-03-14 21:27 ` Kyle McMartin
2009-03-14 21:27 ` Kyle McMartin
2009-03-15 10:08 ` Helge Deller
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=49BC17CA.9020004@gmx.de \
--to=deller@gmx.de \
--cc=kyle@infradead.org \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@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