Path: utzoo!attcan!uunet!mcsun!sunic!dkuug!iesd!iesd!fischer From: fischer@iesd.auc.dk (Lars P. Fischer) Newsgroups: comp.unix.questions Subject: Re: 'cc' versus 'gcc' Message-ID: Date: 7 Oct 89 20:10:12 GMT References: <506@shuldig.Huji.Ac.IL> <7158@asterix.UUCP> <631@crdos1.crd.ge.COM> Sender: news@iesd.auc.dk (UseNet News) Organization: Mathematics and Computer Science, University of Aalborg Lines: 26 In-reply-to: davidsen@crdos1.crd.ge.COM's message of 29 Sep 89 13:54:45 GMT In article <631@crdos1.crd.ge.COM> davidsen@crdos1.crd.ge.COM (Wm E Davidsen Jr) writes: > Before using gcc your should read the license. If you compile and link >using their library you must make the source of your program available >to the public for three years. Not so. Read the GNU Public License. Note that 'gnulib.c' (the runtime system) is *not* copyrighted. If you compile with gcc, and link with your systems 'ld' (the default) there is no problem. When the GNU version of libc.a becomes available, all programs linked with it will have to distributed as GNUware, *if* they are distributed at all. You can of course still use your own version of libc.a if you like. > gcc is not bug free, but it is about as clean as most commercial >compilers. It has *deferent* bugs, not *more* bugs. Actually, it has *fewer* bugs that most commercial compilers. /Lars -- Copyright 1989 Lars Fischer; you can redistribute only if your recipients can. Lars Fischer, fischer@iesd.auc.dk, {...}!mcvax!iesd!fischer Department of Computer Science, University of Aalborg, DENMARK. "That makes 100 errors; please try again" --TeX