Date: Wed, 10 Jul 2013 10:08:45 +0100 (BST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: freebsd-fortran@freebsd.org, thierry@FreeBSD.org Subject: Re: why fortran mailing list? Message-ID: <201307100908.r6A98jOM001342@mech-cluster241.men.bris.ac.uk> In-Reply-To: <20130710084713.GA73590@graf.pompo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Date: Wed, 10 Jul 2013 10:47:13 +0200 From: Thierry Thomas <thierry@FreeBSD.org> To: freebsd-fortran@freebsd.org Subject: Re: why fortran mailing list? > That's not my experience. > For example french/aster, a major FE suite, > fails on both amd64 and ia64: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/176326 > > As far as I know it fails on places other than fortran, > but it is largely "a fortran port". Yes Code_Aster has problems, but PR ports/176328 is caused by another problem located in metis-edf (a patch has been provided, and we are Regarding this patch, is it ok to just put it unde files, as: # ls files/ medis-patch-Lib_Makefile.txt patch-Lib::proto.h patch-Test::Makefile patch-CONFIG::configure patch-Lib_Makefile patch-onmetis patch-CONFIG_onmetis.in patch-Programs::Makefile # How does the ports framework know that medis-patch-Lib_Makefile.txt must be applied *after* patch-Lib_Makefile, i.e. on top of it? Anton P.S. Please ignore my reply to ports/176328. I understand now what to do.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201307100908.r6A98jOM001342>