home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.minix
- Path: sparky!uunet!mcsun!sun4nl!star.cs.vu.nl!kjb
- From: kjb@cs.vu.nl (Kees J. Bot)
- Subject: Re: ACK ANSI Compiler
- Message-ID: <C1GJ41.FDp@cs.vu.nl>
- Sender: news@cs.vu.nl
- Organization: Fac. Wiskunde & Informatica, VU, Amsterdam
- References: <1993Jan21.075806.29635@philce.ce.philips.nl> <93012418390@monty.apana.org.au>
- Date: Tue, 26 Jan 1993 10:43:13 GMT
- Lines: 65
-
- newton@monty.apana.org.au (Mark Newton) writes:
- >
- >(not to mention the lockups that bar = time() would cause when time()
- >would try to write its current timer value to a pointer argument that
- >hadn't been supplied - bar = time(NULL) was the simple fix for that.
- >bar = time() doesn't crash at all when c68 is used over the same source
- >code).
-
- How people can make the rest of their words null and void by saying
- things like this... "bar = time()", I want a core dump dammit!
- (No fault of c68, just pure luck that it worked.)
-
- Slight change of subject:
-
- _KJB's guide to installing software_.
-
- 1. Unpack the stuff in a fresh directory, usually
- /usr/local/src/cmd/<package-name>-<version-number>.
-
- 2. Look at the installation docs, if it needs more than a lib dir, more
- than one binary per user function, more than one environment variable
- or $HOME/.<package>rc: Remove package.
-
- 3. Set your compiler to maximum amount of checking, this is default for
- ACK. If you have gcc use 'gcc -ansi -pedantic -Wall', this will
- even check printf arguments to the format string. Enable separate
- I&D and null pointer dereference checking.
-
- 4. Decide how much of your time this package is worth and start your
- timer. If it runs out: Remove package.
-
- 5. Twiddle Makefile and/or a configuration include file to get the
- package to understand that its support files are in
- /usr/local/lib/<package>, and binaries go to /usr/local/bin. If it
- doesn't like it: Remove package.
-
- 6. Twiddle Makefile to make silent commands (those with @ in front) not
- silent. Remove echo's. No surprises please. Remove 'rm -f' of the
- target binaries, they break links. Study output of 'make -n'.
-
- 7. Run make. Look at the error messages and warnings. If it is about
- K&R style code then add '-wo' or remove '-ansi'. No problem with
- proper K&R style code. Check the warnings, if they indicate that the
- author doesn't have a clue about portable programming: Remove package.
- Make repairs and rerun make until the package compiles or the timer
- runs out.
-
- 8. Try to run the package, do some of step 9 first if necessary.
- If it craches then try to repair.
-
- 9. Look at the installation instructions and/or run 'make -n install'
- and study it's output carefully. Do the installation by hand.
-
- Yes I do have some third-party software on my system, I set the timer
- high sometimes. For Minix it will never expire.
-
- First release of Minicom did not survive its 30 minutes, I have
- forgotten why. I won't try again, kermit is good enough for the few
- KB that I move around.
-
- High time I tried c386. It sounds promising, so I'll give it a day.
- One can't have too many compilers.
- --
- Kees J. Bot (kjb@cs.vu.nl)
- Systems Programmer, Vrije Universiteit Amsterdam
-