Date:	Mon, 9 Nov 92 09:03:18 EST
From:	DJ Delorie <dj AT athena DOT ctron DOT com>
To:	pynq AT midway DOT uchicago DOT edu
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	The "GNUish-DOS method of passing arguments ... "

>  Also supported is the GNUish-DOS method of passing arguments in
>  environment variables.

This means you can use the "LONGARGS" option in GNU-ish make.  It's
not intended for direct use.

>	1) I assume that if I create A.OUT files with gcc (not C++),
>	   I am free to distribute them (at no charge) to my heart's
>	   content, with no further restriction.  Correct?

If you use GPL code, you must comply with the GPL.  In 1.09, all GPL
code is in libgcc.a.  See source files for actual copyright
information.  The mere act of compiling causes no restrictions.
Nothing in libc.a or libm.a incur any restrictions either - everything
is mine or BSD.

>	2) In fact, since I am not distributing GO32 (or even STUB), I
>	   am also free to charge for them, right?  (Tell the user to
>	   find his own GO32...)

Correct.  You may also prepend stub.exe without incurring any
restrictions.  You may also ship emu387 without (preferably with,
though) sources.

>	3) It sounds like if you use C++, then you are almost certainly
>	   going to be using FSF written code.  This means that you have to
>	   distribute full sources with every tiny thing you release.
>	   Is this correct?

Incorrect.  If you use the C++ classes in libgcc.a, *then* you must
comply with the LGPL, which requires you to ship at least object
modules and libgcc.a sources, so that the end user may rebuild
libgcc.a and relink your application.

>	   (By the way, I support the FSF idea; but distributing full
>	   sources with each tiny little thing you write ends up being
>	   more of a nuisance than anything else...)

Hence the LGPL.  I don't recall if I included a copy with libgcc.a,
but if you can't ftp prep.ai.mit.edu then I'll send you a copy.

DJ
dj AT ctron DOT com
Life is a banana.

- Raw text -