mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: torvalds@osdl.org, geert@linux-m68k.org,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cross-sparse
Date: Fri, 18 Jun 2004 14:48:12 -0700	[thread overview]
Message-ID: <20040618144812.2fe5ec3d.rddunlap@osdl.org> (raw)
In-Reply-To: <20040618213338.GA4975@MAIL.13thfloor.at>

On Fri, 18 Jun 2004 23:33:38 +0200 Herbert Poetzl wrote:

| On Fri, Jun 18, 2004 at 09:27:22AM -0700, Linus Torvalds wrote:
| > On Thu, 17 Jun 2004, Geert Uytterhoeven wrote:
| > > 
| > > I wanted to give sparse a try on m68k, and noticed the current 
| > > infrastructure doesn't handle cross-compilation (no sane m68k 
| > > people compile kernels natively anymore, unless they run a 
| > > Debian autobuilder ;-).
| > > 
| > > After hacking the include paths in the sparse sources, installing 
| > > the resulting binary as m68k-linux-sparse, and applying the 
| > > following patch, it seems to work fine!
| > 
| > Hmm.. It does make sense, but at the same time, sparse isn't even really 
| > supposed to _care_ about the architecture. Especially not for a kernel 
| > build.
| 
| apologies for assasinating this thread ...
| 
| I did an 'extensive' search with google (you do not want 
| to know how many hits you get with 'sparse') and read 
| most postings on the sparse mailinglist (linux-sparse),
| found the freshmeat project pointing me to the 'new url'
| http://www.codemonkey.org.uk/projects/sparse/ where I can
| download 'sparse-2003-11-27.tar.gz', then found out that
| there should be a maintained (up to date) version of it at 
| 
|    http://www.kernel.org/pub/software/devel/sparse/
| 
| but what I find there, seems of no use to me ...
| (I'm no bitkeeper person) so I'm still looking for an url
| where I can get a recent .tar to install that beast.
| 
| can anybody point me in the right direction, please?

sure, get a tarball from here:
  http://www.codemonkey.org.uk/projects/bitkeeper/sparse/

--
~Randy

  reply	other threads:[~2004-06-18 21:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 21:13 Geert Uytterhoeven
2004-06-18 16:27 ` Linus Torvalds
2004-06-18 20:49   ` Geert Uytterhoeven
2004-06-18 20:58     ` Linus Torvalds
2004-06-19  0:33     ` viro
2004-06-18 21:33   ` Herbert Poetzl
2004-06-18 21:48     ` Randy.Dunlap [this message]
2004-06-18 21:57     ` Chris Wedgwood
2004-06-18 23:30     ` Dave Jones

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=20040618144812.2fe5ec3d.rddunlap@osdl.org \
    --to=rddunlap@osdl.org \
    --cc=geert@linux-m68k.org \
    --cc=herbert@13thfloor.at \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®