Date: Wed, 6 Jun 2001 11:45:45 -0700 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Chris Casey <chriss@phys.ksu.edu>, alpha@FreeBSD.ORG Subject: Re: ccc Message-ID: <20010606114545.A41541@dragon.nuxi.com> In-Reply-To: <15134.30514.551414.300471@grasshopper.cs.duke.edu>; from gallatin@cs.duke.edu on Wed, Jun 06, 2001 at 02:32:18PM -0400 References: <20010606092327.C96129@dragon.nuxi.com> <Pine.SOL.3.96L.1010606130539.537F-100000@schottky.phys.ksu.edu> <15134.30514.551414.300471@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 06, 2001 at 02:32:18PM -0400, Andrew Gallatin wrote: > > All the errors are from *.h files in /compat/linux/usr/include > > Naturally. Since the compiler is running in linux mode, its going to Oh! So the problem is the AlphaLinux compat bits searching not PATH but whether /foo is /compat/linux/foo or really /foo. Hum.. that is a hard one to work around in the port. > 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. True, but what if one wanted a super-duper devel box? They could easily install both ports (compaq-cc and linux_devel). What do you think about if we set a bit in the ELF header that the AlphaLinux code would use to determine path resolution? I have a feeling the Intel x86 Linux compilers will have the same problem. -- -- David (obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010606114545.A41541>