On Wed, Feb 06, 2019 at 06:44:27PM +0100, G?tz Hoffart wrote: Lattice was the thing, back when I had Amiga. Too bad I could not afford a harddisk :-). BTW, I just recalled the Aminet is still there and seems to be quite active, although I guess activity nowadays mostly revolves around PPC-based models with Workbench 4(++).x(++), but they have /dev section and quite a few compilers in there: http://aminet.net/tree?path=dev After all, who said it was a C compiler? Most probably, it was C compiler, yes. -- Regards, Tomasz Rola -- ** A C programmer asked whether computer had Buddha's nature. ** ** As the answer, master did "rm -rif" on the programmer's home ** ** directory. And then the C programmer became enlightened... ** ** ** ** Tomasz Rola mailto:tomasz_rola at bigfoot.com **

On 2/6/19 1:23 PM, Tomasz Rola via cctalk wrote: I used Mark WIlliams C on the Atari ST. --Chuck

On Thu, Feb 07, 2019 at 09:06:03AM -0600, John Foust via cctalk wrote: [...] I guess you could have a revenge now and publish it on a web? tl;dr: Is there a software repository for AtariST comparable to Aminet? Yeah... It was a bit less painful if one had Amiga 2000 or higher (I had 2000c... or b?) since there was a lot of place inside. I had two floppy stations and second half of my ownership was blessed with ram extension (giving me total of 3 megabytes). I used Aztec C (it had proper linker (ln), make for makefiles and ar for *.a archive management, IIRC). Managed to squeeze full dev environment into ramdisk (I remember I had to delete some unused files to make place, and probably used some small AmigaDOS batch file to automate things). And the ramdisk was rebootable, and could be booted from, which was so cool (because Guru Meditation plagued me a bit)! On the other hand, later on I witnessed coming of relatively cheap PC-compatible harddrives for Amiga 500, which were unusable in my case (there were too few Amiga 2/3/4xxx users to care, and I believe around this time the inept C= managers decided to eject everything and /-I guess-/ pay themselves a bonus, so the ice under users' feet was definitely shrinking). I have also learnt to hate MS-made Basic (included on Workbench floppies) while trying to use it. Overally, it was a good experience. It helped me to grasp and appreciate modern aspects of computing, and so I swallowed the Unix bug in a second, while it took fellow students weeks or infinity (especially if they started with MS DOS, as I observed). OTOH, in retrospect, I wonder if I would spent the money wiser by choosing AtariST or going straight to 286 (not the same experience, I know, but cheap and easier to sell away). Or, if I wanted it really cheap, C128 was able to give me 80x24 terminal in one gfx mode, but I could not find any floppy drive for it capable of r/w PC floppies, so that option is probably out. I have a kind of very-very low priority project to investigate AtariST side of things, especially that nowadays I can run a very nice community-written TOS on emulator, but it seems there is no software repository similar to Aminet, am I right? I am interested in utility software, mostly compilers and editors and other such things. Multimedia and games, not so much. Actually, the project is spelled somewhat like "assume that buying Amiga 2000 was bad idea, was there something that could have prepared me for embracing Unix (and later, Linux), while giving me PC compatible floppy, good text terminal (i.e. 80x24) and maybe even hard drive? (gaming not required, as I really had almost no time for this)". So that John Titor could drop me a postcard (also, assume he is subscribed here). So far, one of AtariST or Amiga 500. But I cannot get price listings from old Polish computer press - my own papers lay buried deep below new papers, no access, and I am yet to find proper incantation for goog. So the "project" is on temporary hold. -- Regards, Tomasz Rola -- ** A C programmer asked whether computer had Buddha's nature. ** ** As the answer, master did "rm -rif" on the programmer's home ** ** directory. And then the C programmer became enlightened... ** ** ** ** Tomasz Rola mailto:tomasz_rola at bigfoot.com **

I don't follow it much, so I can't really say for sure what systems or software are in the archive. But there was an effort for collecting "all" games and software for many systems called TOSEC. Unfortunately, it's not an authorized collection so copyright folks may frown on obtaining those files.

On Wed, 6 Feb 2019, Tomasz Rola wrote: Hi Tomasz, Thanks for the link to Aztec -- I'm well aware of it, and it's on my list of compilers to examine more closely :) It certainly meets the criteria of time, platform and so on. Thanks, -- Phil. philpem at philpem.me.uk http://www.philpem.me.uk/

On Thu, Feb 7, 2019 at 3:50 AM Phil Pemberton via cctalk <cctalk at classiccmp.org> wrote: I've been working on a project this month and I'm using FS-UAE to emulate the Amiga and running SAS/C 6.58. One distinct advantage is it writes Amiga files to the underlying UNIX filesystem so getting data in and out of the emulated environment is utterly trivial (making it easy to get and install tools and to export the results. The same technique would work with Aztec C. Local Makefiles running under AmigaDOS, your choice of editing files inside or outside the emulator... My target environment is actually AmigaDOS so it was an obvious choice, but if your target is binary objects, there they are on your platform's filesystem, ready to burn into ROMs or do whatever with. Of course, I spent a lot of time on the Amiga so I have no problems with that being my working environment. YMMV. -ethan

On Wed, Feb 6, 2019 at 10:27 AM Ethan Dicks <ethan.dicks at gmail.com> wrote: I'm also remembering that the cost of a C compiler that ran on VMS but emitted m68k code was insanely expensive in the late 1980s (many thousands of dollars) so for one project, we purchased a Perkin Elmer 7350 workstation and it was both the software development environment for the team _and_ we used its C compiler to generate m68k assembler, which we then fed to our home-grown cross-assembler because we needed our binary format, not a.out. It really was the cheapest way to do that 30 years ago. OTOH, at home, I'd had an Amiga since 1986 and used a variety of native tools (Lattice C later SAS/C, and various assemblers either commercial or from a Fish Disk). -ethan

On 2/6/19 11:45 AM, Tom Uban via cctalk wrote: I dug up my copy of the Stanford V System, which also used a version of the Trix compiler (as did many others). http://bitsavers.org/bits/Stanford/VSystem_6.0 This was also the starting point for the Stanford SUMACC Macintosh compiler. I've just found the binaries so far, I thought I had the sources somewhere. There is also an MIT compiler tape around with a bunch of different PCC ports including the Brooklyn Poly x86 compiler.

On Tue, Feb 12, 2019 at 2:55 PM Ethan Dicks via cctalk < cctalk at classiccmp.org> wrote: Cool beans. Is it copy protected? Sometimes I think it would be cool to have an archive of early commercial s/w for the Rainbow somewhere... Warner

On Feb 12, 2019, at 14:16, Warner Losh via cctalk <cctalk at classiccmp.org> wrote: I remember moving Lattice C v2 from IBM PC diskettes to an HP 150. It was MS-DOS applications and compiler and linker worked on the 150. No copy protection. -Frank McConnell

On 2/12/19 4:06 PM, Frank McConnell via cctalk wrote: Lattice C was recommended by Microsoft to OEMs in the DOS 1.-2. days. Two-step compilation process LC1, LC2, then link for executable. Microsoft didn't yet have their own C. --Chuck