From: "Shahbaz Khan" <shaz.linux@gmail.com>
To: linux-c-programming@vger.kernel.org
Subject: lxr problem - newbie needs help
Date: Mon, 7 May 2007 00:06:11 +0500 [thread overview]
Message-ID: <20cbb9450705061206h767285f6n339dd4e0d7ce9658@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
I am using Fedora core 6. I have configured lxr 0.3 with the latest
glimpse but I get the following in the browser:
-> Parent Directory
- fileidx
- xref
when i click the files it gives me some wierd source code with lots of
funny faces like ones in the ascii command line screens (if that makes
sense at all!).
lxr installprefix is /var/www/lxr/
My document root for apache is /var/www/
attached is my lxr configuration.
[-- Attachment #2: lxr.conf --]
[-- Type: application/octet-stream, Size: 1121 bytes --]
# Configuration file.
# Define typed variable "v", read valueset from file.
variable: v, Version, [/var/www/lxr/source/versions], [/var/www/lxr/source/defversion]
# Define typed variable "a". First value is default.
variable: a, Architecture, (i386, alpha, m68k, mips, ppc, sparc, sparc64)
# Define the base url for the LXR files.
baseurl: http://127.0.0.1/lxr/http/
# These are the templates for the HTML heading, directory listing and
# footer, respectively.
htmlhead: /var/www/lxr/http/template-head
htmltail: /var/www/lxr/http/template-tail
htmldir: /var/www/lxr/http/template-dir
# The source is here.
sourceroot: /var/www/lxr/source/$v/linux/
srcrootname: Linux
# "#include <foo.h>" is mapped to this directory (in the LXR source
# tree)
incprefix: /include
# The database files go here.
dbdir: /var/www/lxr/source/$v/
# Glimpse can be found here.
glimpsebin: /usr/local/bin/glimpse
# The power of regexps. This is pretty Linux-specific, but quite
# useful. Tinker with it and see what it does. (How's that for
# documentation?)
map: /include/asm[^\/]*/ /include/asm-$a/
map: /arch/[^\/]+/ /arch/$a/
reply other threads:[~2007-05-06 19:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20cbb9450705061206h767285f6n339dd4e0d7ce9658@mail.gmail.com \
--to=shaz.linux@gmail.com \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).