From owner-freebsd-alpha Wed Jun 6 11:32:51 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 49DC737B401; Wed, 6 Jun 2001 11:32:49 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA10583; Wed, 6 Jun 2001 14:32:48 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.3/8.9.1) id f56IWIh35245; Wed, 6 Jun 2001 14:32:18 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15134.30514.551414.300471@grasshopper.cs.duke.edu> Date: Wed, 6 Jun 2001 14:32:18 -0400 (EDT) To: Chris Casey Cc: "David O'Brien" , alpha@FreeBSD.ORG Subject: Re: ccc In-Reply-To: References: <20010606092327.C96129@dragon.nuxi.com> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Chris Casey writes: > > Here is what I get with devtools in: > > /usr/bin/ccc -c -O3 -I. -I../src/headers -I../src/language -I/usr/include > -o gp.o ../src/gp/gp.c > cc: Error: /usr/include/libio.h, line 363: Ill-formed parameter type list. > (parmtyplist) > extern int _IO_vfscanf __P ((_IO_FILE * __restrict, const char * > __restrict, > -----------------------^ > cc: Error: /usr/include/libio.h, line 365: Ill-formed parameter type list. > (parmtyplist) > extern int _IO_vfprintf __P ((_IO_FILE *__restrict, const char > *__restrict, > ------------------------^ > *snip* > > All the errors are from *.h files in /compat/linux/usr/include Naturally. Since the compiler is running in linux mode, its going to find the linux headers first. And they won't work in FreeBSD, so you loose. You cannot have linux_devtools installed & still be able to generate native binaries. I think the compaq compilers are statically linked. I could conceive of a cheesy kernel hack to not search the /compat/linux hierarchy for static binaries of a certain brand, but it would be far better to just freebsd-ify fortran. Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message