Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Joel Soete <joel.soete@freebel.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Sources browsing tool?
Date: Sun, 18 Aug 2002 17:36:58 +0000	[thread overview]
Message-ID: <3D5FDB3A.4020708@freebel.net> (raw)
In-Reply-To: 1023475115.25523.47.camel@irongate.swansea.linux.org.uk

Just for reminder in this ml


Alan Cox wrote:
  > On Fri, 2002-06-07 at 18:23, joel.soete@freebel.net wrote:
  >
  >>Hi all,
  >>
  >>Can you advise me some browsing tools which would allowing me to find
quickly
  >>where a variable, a function is define; where is used,... in this big
amount
  >>source which represent kernel now (find is not always easy).
  >>
  >>I find well a work of reverse engineering (rigiedit) of the kernel
but not for 2.4.
  >>And unfortunately sources (tcl/tk iirc) do not seems to be available
to port on
  >>hppa.
  >
  >
  > Try the Linux cross reference - http://lxr.linux.no
  >


I try to install it (from src, from tarball, from cvs): no way of
success (install instruction not uptodate)
But on the same 'sf.net' I found my happyness: sourcenav (5.1.0).

An install of the Install:
./configure --prefix=/opt/sn
make
make install

(That is the first time that I had the opportunity to build a package
with so few warning. It is very beautifull and easy to use :)

And the last but not least: it works fine on my own i386 as well as on
my b2k :)
I am now impatient to test it on a big proj as linux-2.4.

Joel

  parent reply	other threads:[~2002-08-24 18:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 17:23 [parisc-linux] Sources browsing tool? joel.soete
2002-06-07 18:38 ` Alan Cox
2002-06-07 19:42   ` Carlos O'Donell Jr.
2002-08-18 17:36   ` Joel Soete [this message]
2002-06-07 19:29 ` Rafael E. Herrera

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=3D5FDB3A.4020708@freebel.net \
    --to=joel.soete@freebel.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=parisc-linux@lists.parisc-linux.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