Date: Wed, 7 Apr 2004 16:14:15 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Mike Hunter <mhunter@ack.Berkeley.EDU> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: vim port compile error (libc.h:33: error: syntax error before "Rune") Message-ID: <20040407231415.GA59261@xor.obsecurity.org> In-Reply-To: <20040407225054.GA29250@ack.Berkeley.EDU> References: <20040407003527.GA12508@ack.Berkeley.EDU> <20040407004107.GA58185@xor.obsecurity.org> <20040407175714.GA22837@ack.Berkeley.EDU> <20040407184250.GA75825@xor.obsecurity.org> <20040407225054.GA29250@ack.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
--y0ulUmNC+osPPQO6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Apr 07, 2004 at 03:50:54PM -0700, Mike Hunter wrote: > On Apr 07, "Kris Kennaway" wrote: >=20 > > On Wed, Apr 07, 2004 at 10:57:14AM -0700, Mike Hunter wrote: > > > > Looks like a conflict with that header - use pkg_which to find out > > > > which port installed it. > > >=20 > > > 9libs-1.0 > > >=20 > > > I'll try a portupgrade -rf on that I suppose... > >=20 > > Those two ports probably conflict. >=20 > Thanks. Is /usr/local/include/libc.h as important of a file as one might > expect, given it's named "libc.h"? If so, why would the 9libs port go and > replace it? Is that a problem, perhaps? What I meant was that the vim port is detecting that non-standard header and trying to use it, and choking. Perhaps vim can be fixed to not do that, but for now it seems broken. Kris --y0ulUmNC+osPPQO6 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAdItHWry0BWjoQKURApVXAJ4x7Jf3p+MFt7WpRu1y7dmQAqsH6gCglTv2 WocMQZM4n4kOnLWPZ8Gkl3E= =DdkC -----END PGP SIGNATURE----- --y0ulUmNC+osPPQO6--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040407231415.GA59261>