Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 9 May 2004 21:07:46 -0400
From:      Michael Edenfield <kutulu@kutulu.org>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        obrien@FreeBSD.org
Subject:   Re: FreeBSD Port: vim-6.2.531
Message-ID:  <20040510010746.GA15827@wombat.localnet>
In-Reply-To: <20040509232255.GB54086@xor.obsecurity.org>
References:  <200405091234.43684.dmk@ncf.ca> <20040509232255.GB54086@xor.obsecurity.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--VbJkn9YxBvnuCH5J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Kris Kennaway <kris@obsecurity.org> [040509 20:00]:
> On Sun, May 09, 2004 at 12:34:43PM -0400, Dwayne MacKinnon wrote:
> > Hi,
> >=20
> > 	I just wanted to let you know about a problem I've been having for a w=
hile=20
> > now with the vim port. If I use the WITH_TCL flag, the build breaks. I'=
ve=20
> > included the output from the build.
> >=20
> > 	Thought I'd take the opportunity to say "thanks" for maintaining the v=
im=20
> > port. Definitely my favorite editor out there.
>=20
> Thanks for this bug report.  I have been seeing this error on bento
> for some time, but David hadn't been able to figure out what caused
> it.  Hopefully this bug report should allow him to fix it now.

The bug here is that, when vim reads the TCL_DEFS flags from
tclConfig.sh, it splits the TCL_DEFS variable on each space and throws
away the ones it doesn't need.  But the TCL_WIDE_INT_TYPE is usually
listed as "long\ long", which tr splits into:

-DTCL_WIDE_INT_TYPE=3Dlong\
long

and then leaves that second 'long' along, ultimately putting it into
CFLAGS.  That's why gcc thinks there's an extra file on the command
line.

Oddly enough, I have 3 machines running -CURRENT with identical Tcl
builds, and only two of them show this problem.  All three of them,
however, have the 'long\ long' definition.  I'm still puzzling that one
out.  In the mean time, I have submitted a PR with a patch that lets me
build on the two that break.

--Mike


--VbJkn9YxBvnuCH5J
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAntXiCczNhKRsh48RAvsGAKDSG8o/zyCrW+GPcV/9MArM5CqHugCfd5ax
WBgsbN+74itmLnXhWBdgrno=
=FXjP
-----END PGP SIGNATURE-----

--VbJkn9YxBvnuCH5J--



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