Date: Mon, 30 Mar 1998 15:29:27 -0500 From: Benjamin Greenwald <beng@lcs.mit.edu> To: "Pedro F. Giffuni" <giffunip@asme.org> Cc: hackers@FreeBSD.ORG Subject: Re: Navigating in NIST + clustering Message-ID: <199803302029.PAA02270@methi.lcs.mit.edu> In-Reply-To: Your message of "Sun, 29 Mar 1998 12:59:05 EST." <351E8BE9.41C67EA6@asme.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> There should be a parallel-FreeBSD list to coordinate with PVM and MPICH > users possible ports of Stanford's SUIF and UIUC's Pablo projects... > > SUIF: > http://www-suif.stanford.edu/suif/NCI/suif.html SUIF? I've been running SUIF1 out-of-the-box on my RELENG_2_2 system for quite some time now. Granted, you don't get shared libraries, but that should be a simple Makefile hack. Since SUIF1 is no longer supported in any way, there's no point in trying to get an official patch for FreeBSD shared libraries into the distribution. SUIF2 on the other hand is a horse of a completely different color simply because it is so expensive in time and space to compile using g++. We run it here, but if we didn't have the SunPro compiler it would take over a week to compile SUIF2 w/ g++-2.8.1 (that's on an 170Mhz Ultra Sparc w/ 512Megs of RAM). Even with SunPro it takes half a day. Supposedly, the current SUIF2 alpha release can be compiled w/ the egcs project version of g++ which has slightly better template handling than stock g++, but the last time I tried compiling SUIF code w/ egcs, the compiler constantly crashed. Anyone willing to give a try can check out http://suif.stanford.edu for the SUIF source. egcs is of course in the ports tree. -Ben > > cheers, > Pedro. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199803302029.PAA02270>