Date: Sun, 17 Jun 2001 11:30:02 -0700 (PDT) From: Dima Dorfman <dima@unixfreak.org> To: freebsd-ports@FreeBSD.org Subject: Re: ports/28222: New port of error: analyze compiler error messages Message-ID: <200106171830.f5HIU2f53109@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/28222; it has been noted by GNATS.
From: Dima Dorfman <dima@unixfreak.org>
To: Peter Pentchev <roam@orbitel.bg>
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: ports/28222: New port of error: analyze compiler error messages
Date: Sun, 17 Jun 2001 11:20:29 -0700
Peter Pentchev <roam@orbitel.bg> writes:
> On Sat, Jun 16, 2001 at 11:48:55PM -0700, Dima Dorfman wrote:
> >
> > >Number: 28222
> > >Category: ports
> > >Synopsis: New port of error: analyze compiler error messages
> > >Originator: Dima Dorfman
> >
> > >Description:
> >
> > Error analyzes and optionally disperses the diagnostic error messages
> > produced by a number of compilers and language processors to the
> > source file and line where the errors occurred. It can replace the
> > painful, traditional methods of scribbling abbreviations of errors on
> > paper, and permits error messages and source code to be viewed
> > simultaneously without machinations of multiple windows in a screen
> > editor.
> >
> > Error knows about the error messages produced by: make(1), cc(1),
> > cpp(1), ccom(1), as(1), ld(1), lint(1), pi(1), pc(1), f77(1), and DEC
> > Western Research Modula-2. However, please note that error hasn't
> > been taught about the toolchain currently in use on FreeBSD, so the
> > aforementioned programs may not necessarily be the ones installed on
> > your system!
>
> I think error(1) was in the base system, but it was disconnected
> from the build at some point. There was even a PR in GNATS about
> it, though I can't really remember the details now.. oh wait,
It was removed because it doesn't work "well" with the current
toolchain. This is true to some extent, but it's still useful; some
of the programs it supports haven't changed all that much since 4.4BSD
(e.g., pc(1)).
> there are even two of those: 19404 and 23233 :) In a followup
> to the second one, Chris Faulhaber has suggested that this be made
> a port; however, you might still want to contact Kris for details
> about just why did he consider it non-working enough to be removed,
> or David O'Brien for information if it would be easy to re-add it
> to the base system.
Personally, I'd rather see it as a port than in the base system. I
think the less unnecessary things we have in the base system the
better. Some things obviously have to be there, like *control (or
anything else that's tightly coupled with the kernel or other aspects
of the system), all the programs for interactive use, etc. This isn't
one of those things; not everyone is a developer, and those that are
can afford to install the port (and, of course, as you say later, many
common-place editors already have this functionality built in).
> And one more comment :)
>
> > X# This isn't very scalable, but I'm lazy..
> > X.if defined(NOMANCOMPRESS)
> > XMANNAME= error.1
> > X.else
> > XMANNAME= error.1.gz
> > X.endif
>
> How about:
>
> .if !defined(NOMANCOMPRESS)
> .for i in 1
> .ifdef MAN${i}
> MAN$i:= ${MAN$i:C/$/.gz/}
> .endif
> .endfor
> .endif
>
> The ".for i in 1" is somewhat stupid :) But it scales well.. :)
> If there really are no other sections to be added in the future:
As the comment says, I was too lazy to do this myself, but now that
you did half the work I'll certainly put it in with the required
modifications to do-install :-).
Thanks!
Dima Dorfman
dima@unixfreak.org
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106171830.f5HIU2f53109>