From owner-freebsd-questions  Fri Feb 26 14:43:11 1999
Delivered-To: freebsd-questions@freebsd.org
Received: from dorm-36314.rh.uh.edu (Dorm-36314.RH.UH.EDU [129.7.141.218])
	by hub.freebsd.org (Postfix) with ESMTP id 84DB015033
	for <questions@freebsd.org>; Fri, 26 Feb 1999 14:42:33 -0800 (PST)
	(envelope-from wotan@dorm-36314.rh.uh.edu)
Received: from localhost (wotan@localhost)
	by dorm-36314.rh.uh.edu (8.9.2/8.9.2) with ESMTP id QAA19511
	for <questions@freebsd.org>; Fri, 26 Feb 1999 16:42:16 -0600 (CST)
	(envelope-from wotan@dorm-36314.rh.uh.edu)
Date: Fri, 26 Feb 1999 16:42:16 -0600 (CST)
From: Jonathan Fosburgh <wotan@dorm-36314.rh.uh.edu>
Reply-To: jef53313@bayou.uh.edu
To: questions@freebsd.org
Subject: Making the lcc port actually work
Message-ID: <Pine.BSF.4.05.9902261637200.19350-100000@dorm-36314.rh.uh.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I decided I would try the lcc port and it compiled just fine.  The only
problem I have is that it dies whenever I use it.  The message is

/usr/include/machine/ansi.h <line number> invalid use of long

This is because the release of lcc in the ports does not support long
long.  The current release does support long long, but the port for it has
not been made yet.  So my questions are, is someone working on the port or
does anyone know how to get the port to work as it is now.  I would guess
that if this port simply did not work it would be marked as broken, but
that is not the case.  I'll attempt later to see what I can do about
getting the current release to build, but at this time I am unable to do
so.

Jonathan Fosburgh
Geotechnician
Snyder Oil Corporation
Houston, TX

Home Page:
http://www.geocities.com/vienna/1498
Manager, FreeBSD Webring: 
http://www.geocities.com/vienna/1498/computer/freebsdring.html



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