Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cunixf.cc.columbia.edu!cunixa.cc.columbia.edu!das15 From: das15@cunixa.cc.columbia.edu (Douglas A Scott) Newsgroups: comp.windows.interviews Subject: Re: porting IV to other systems Message-ID: <1991May25.204812.13300@cunixf.cc.columbia.edu> Date: 25 May 91 20:48:12 GMT References: <9105231425.AA00690@mongo.uswest.com> <9105250439.AA01683@milo.mit.edu> Sender: usenet@cunixf.cc.columbia.edu (The Network News) Reply-To: das15@cunixa.cc.columbia.edu (Douglas A Scott) Organization: Columbia University Lines: 21 Nntp-Posting-Host: cunixa.cc.columbia.edu In article <9105250439.AA01683@milo.mit.edu> eichin@MIT.EDU ("Mark W. Eichin") writes: >Steve Fogel writes: >>>. But how well has the file system been isolated? IV seems to be >>> quite dependent on UNIX. > I've tried building 3.0beta on a few systems with a few >compilers (current score: 0 for 2 - CC2.0 over VAX BSD pcc: pcc blows >up on a few files, some internal table blows out; gcc-1.93 (early 2.0) >on the NeXT - only about 1/4 of libg++ works, so I'm not even trying [remainder of article deleted] Has anyone successfully ported 2.6 to the NeXT (running 2.0 or 2.1)? I am extremely interested in hearing from you if you have. I had no trouble building libg++ under NeXT OS 2.1, by the way--at least so it seems. Thanks!! <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Douglas Scott Columbia University Computer Music Studio Internet: UUCP: ...!columbia!woof!zardoz!doug Phone: (703)765-4771