Date: Thu, 12 Nov 2009 16:52:08 +0000 From: Anton Shterenlikht <mexas@bristol.ac.uk> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: maho@freebsd.org, freebsd-current@freebsd.org, Anton Shterenlikht <mexas@bristol.ac.uk>, freebsd-ia64@freebsd.org Subject: Re: compiler discussion Message-ID: <20091112165208.GC1283@mech-cluster241.men.bris.ac.uk> In-Reply-To: <20091112153407.GA62396@troutmask.apl.washington.edu> References: <20091112141519.GA66229@mech-cluster241.men.bris.ac.uk> <20091112153407.GA62396@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Nov 12, 2009 at 07:34:07AM -0800, Steve Kargl wrote: > On Thu, Nov 12, 2009 at 02:15:19PM +0000, Anton Shterenlikht wrote: > > Following from the discussion on the system compiler for ia64, > > I tried to list few major ports which I'd love to have on ia64, > > but can't, because of GCC problems: > > > > - math/blas, lapack, lapack95, arpack, scalapack, atlas, etc. > > - science/hdf5-18 (fortran APIs can't be built) > > - french/aster (industial quality FEA code) > > - cad/calculix (another good FEA code) > > > > All these depend on lang/gcc44, which doesn't build. > > Doesn't build is not a very good description if you're > looking for help. Post the build log somewhere. > Have you submitted bug reports to gcc.gnu.org? Bugs > that are unreported are unlikely to be fixed. sorry, I thought it was a known issue. Here's my bug report: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40959 I admit, I haven't checked the suggested patch yet.. > Have you checked the Open64 project? will do many thanks anton -- Anton Shterenlikht Room 2.6, Queen's Building Mech Eng Dept Bristol University University Walk, Bristol BS8 1TR, UK Tel: +44 (0)117 331 5944 Fax: +44 (0)117 929 4423
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091112165208.GC1283>