public inbox for sourcenav@sourceware.org
 help / color / mirror / Atom feed
From: Bruce Korb <bkorb@pacbell.net>
To: Artem Khodush <kaa@comail.ru>
Cc: sourcenav@sources.redhat.com
Subject: Re: Miscompile on 5.0 released sources
Date: Sun, 22 Jul 2001 14:12:00 -0000	[thread overview]
Message-ID: <3B5B4256.80CEC0B5@pacbell.net> (raw)
In-Reply-To: <001101c112f2$7c288360$3737370a@artem>

Artem Khodush wrote:
> 
> make all-snavigator # instead of make

Thank you.  I finally found a binary RPM to install.
Meanwhile, the top level README:

> $ cat ../README
>                    README for GNU development tools
>  
> This directory contains various GNU compilers, assemblers, linkers,
> debuggers, etc., plus their support routines, definitions, and documentation.
>  
> Check the INSTALL directory for detailed configuration and installation
> instructions.
>  
> Much of the code and documentation enclosed is copyright by
> the Free Software Foundation, Inc.  See the file COPYING or
> COPYING.LIB in the various directories, for a description of the
> GNU General Public License terms under which you can copy the files.
>  
> REPORTING BUGS: Again, see gdb/README, binutils/README, etc., for info
> on where and how to report problems.

looks like a copy from GCC and is especially unhelpful
since there is no INSTALL directory.  Next, the snavigator
README is even less helpful:

> $ cat README
> README

If someone were to add the ``make all-snavigator'' comment
to either of these, ....  Again, thank you Artem.

Cheers, Bruce

  reply	other threads:[~2001-07-22 14:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-20 18:10 Bruce Korb
2001-07-22 14:01 ` Artem Khodush
2001-07-22 14:12   ` Bruce Korb [this message]
2001-07-22 14:15     ` Mo DeJong

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=3B5B4256.80CEC0B5@pacbell.net \
    --to=bkorb@pacbell.net \
    --cc=kaa@comail.ru \
    --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).