From: Bill Munday <bmunday@3glab.com>
To: sourcenav@sourceware.cygnus.com
Subject: Re: Installing sourcenav
Date: Thu, 08 Feb 2001 08:54:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0102081645130.32680-100000@bmunday> (raw)
In-Reply-To: <Pine.LNX.4.21.0102061010250.1417-100000@bmunday>
Hi SNers,
I wanted to know if there is any way that the errors generated by the
compiling program in the Build Make window could be highlighted.
Furthermore are there any keystrokes that jump you to the first error,
then a return jumps you to the file and line
I suppose I have seen it work in emacs about three years ago but can't
remember the exact details. And I am not using emacs as my external editor
- apologies to emacs users nor do I want to.
Thanks in advance
Bill Munday
Example of an error in a c file with in the Build make window.
make[1]: Leaving directory
`/home/bmunday/projects/ecos/build/infra/current'
make -r -C redboot/current build
make[1]: Entering directory
`/home/bmunday/projects/ecos/build/redboot/current'
arm-elf-gcc -c -I/home/bmunday/projects/ecos/build/install/include
-I/home/bmunday/projects/ecos/packages/redboot/current
-I/home/bmunday/projects/ecos/packages/redboot/current/src
-I/home/bmunday/projects/ecos/packages/redboot/current/tests
-I. -I/home/bmunday/projects/ecos/packages/redboot/current/src/net/
-mcpu=strongarm1100 -Wall -Wpointer-arith -Wstrict-prototypes -Winline
-Wundef -Woverloaded-virtual -g -O2 -ffunction-sections -fdata-sections
-fno-rtti -fno-exceptions -fvtable-gc -finit-priority
-Wp,-MD,src/net/bootp.tmp -o src/net/redboot_bootp.o
/home/bmunday/projects/ecos/packages/redboot/current/src/net/bootp.c
/home/bmunday/projects/ecos/packages/redboot/current/src/net/bootp.c: In
function `bootp_handler':
/home/bmunday/projects/ecos/packages/redboot/current/src/net/bootp.c:73: `i'
undeclared (first use in this function)
/home/bmunday/projects/ecos/packages/redboot/current/src/net/bootp.c:73: (Each
undeclared identifier is reported only once
/home/bmunday/projects/ecos/packages/redboot/current/src/net/bootp.c:73: for
each function it appears in.)
make[1]: *** [src/net/bootp.o.d] Error 1
make[1]: Leaving directory
`/home/bmunday/projects/ecos/build/redboot/current'
make: *** [build] Error 2
+++ End +++
next prev parent reply other threads:[~2001-02-08 8:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <981386286.22393.ezmlm@sources.redhat.com>
2001-02-05 8:47 ` Bill Munday
2001-02-05 9:01 ` Ian Roxborough
2001-02-05 9:03 ` Bruce Stephens
2001-02-06 2:23 ` Bill Munday
2001-02-06 4:22 ` Bruce Stephens
2001-02-08 8:54 ` Bill Munday [this message]
2001-02-08 9:54 ` Window Names Bill Munday
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=Pine.LNX.4.21.0102081645130.32680-100000@bmunday \
--to=bmunday@3glab.com \
--cc=sourcenav@sourceware.cygnus.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).