Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Aug 2001 09:20:16 -0500
From:      Steve Ames <steve@virtual-voodoo.com>
To:        "David O'Brien" <obrien@FreeBSD.ORG>
Cc:        Jim Bryant <kc5vdj@yahoo.com>, Charlie & <root@virtual-voodoo.com>, FreeBSD-hackers@FreeBSD.ORG
Subject:   Re: TCSH bug...
Message-ID:  <20010828092016.B21396@virtual-voodoo.com>
In-Reply-To: <20010827200243.A8113@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Aug 27, 2001 at 08:02:43PM -0700
References:  <3B8AC157.5000203@yahoo.com> <020701c12f43$8e0e2310$28d90c42@eservoffice.com> <3B8AC8DB.5090603@yahoo.com> <004801c12f49$66cccb20$28d90c42@eservoffice.com> <20010827201407.A32152@virtual-voodoo.com> <3B8B05AF.9070004@yahoo.com> <20010827200243.A8113@dragon.nuxi.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 27, 2001 at 08:02:43PM -0700, David O'Brien wrote:
> On Mon, Aug 27, 2001 at 09:45:03PM -0500, Jim Bryant wrote:
> > Someone recently commented in the tcsh/csh thread concerning the fact
> > that the FreeBSD tcsh is maintained separately from the port,
> 
> As is all 3rd party contributed software.
> 
> > and nobody is really sure who is responsible for keeping the FreeBSD
> > version both in sync, AND, csh compatable when called with the
> > executable name "csh".
> 
> We *do* know who that is.  This however is a more tcsh-specific issue,
> and raising it with the tcsh author would probably lead you to faster
> happiness.  Is there some reason you wont email him about this?

Except it isn't tcsh specific really. 

Our config.h in /usr/src/bin/csh defines SYSMALLOC. The port does not.
The port works, the system version doesn't. If you comment out SYSMALLOC
in /usr/src/bin/csh/config.h and recompile then the TCSH bug goes away.

Now you could argue that perhaps the definition of SYSMALLOC just exposes
a bug in tcsh? OTOH, since the system version in -STABLE also defines
SYSMALLOC and still manages to work... you could also argue that this points
to some other bug in -CURRENT... lastly it could be argued that I'm barking
up completely the wrong tree. *shrug*

-Steve

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010828092016.B21396>