public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Nacho de los Ríos Tormo <irios@proin.es>
To: "Lista Source Navigator" <sourcenav@sources.redhat.com>
Subject: Unable to build in SuSE 7.0
Date: Fri, 20 Apr 2001 07:30:00 -0000	[thread overview]
Message-ID: <01042016325500.28678@irios> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]

After my lack of success in executing snav5 binaries in SuSE Linux 7.0, I 
have found some time to try to build the sources.

My builds failed when reaching the fortran parser, as there seems to be at 
least one missing file (snavigator/parsers/fortran/fortran.c). I could only 
get the build working by removing references to "snavigator/parsers/fortran" 
from "snavigator/configure" and "snavigator/configure.in", as well as 
references to "fortran" from "snavigator/parsers/Makefile.in" and 
"snavigator/parsers/Makefile.am".

With this changes, I was able to build and run snav5. I have lost the 
integration with fortran, which I'm sure I wont miss ... I don't see, 
however, how could these sources compile without changes for other people; 
maybe SuSE sets up gcc or make with options that make it more finicky with 
missing files ....

By the way, are there any plans to make snav more friendly to truetype fonts? 
The visual quality of the fonts that Source Navigator uses leaves A LOT to be 
desired, while my X server offers a few great quality truetype fonts.

Thanks for a great product,

Nacho de los Ríos Tormo
Procedimientos Integrados S.L.
SPAIN

                 reply	other threads:[~2001-04-20  7:30 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=01042016325500.28678@irios \
    --to=irios@proin.es \
    --cc=sourcenav@sources.redhat.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).