Date:	Wed, 15 Jul 1998 10:11:37 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Robyn Fry <rfry AT omnisig DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: building gcc-2.8.0 source file????
In-Reply-To:	<35AB806A.BDE27A64@omnisig.com>
Message-ID:	<Pine.SUN.3.91.980715101119.10743H-100000@is>
MIME-Version:	1.0

On Tue, 14 Jul 1998, Robyn Fry wrote:

> gcc280s.zip

I suggest to get gcc281s.zip, since v2.8.1 is the latest one.

> I have printed out all of the readme files but it seems with each file there
> is another product which I have to unzip to build it properly.  Anyway I am
> stuck on sh-util which claims; to build it I need to merely type config and
> then make neither of which do anything.

First, you need to decide whether you really need to build everything
from sources.  The *b.zip are pre-compiled binaries which you should
be able to use without any need to recompile them.  Somebody already
did all that work for you and provided ready executables which you can
run.  So first, make up your mind about which packages do you need to
rebuild, and which ones you can use as provided in the *b.zip files.

Next, for those packages which you *need* to build from sources, you
will have to download the source distributions from the DJGPP ftp
sites.  Source distributions have names which end with `s', like
gcc281s.zip, shl112s.zip, etc.  If you download a binary distribution
like shl112b.zip, you won't be able to rebuild it because it does NOT
include all the sources and configuration scripts (such as config.bat
which the README mentions) necessary to rebuild them.

After you download and unzip the source distribution, *then* you can
build it as the README says.  Please look for a DJGPP-specific README
file, usually called README.dos or README.djgpp, or djgpp/README; the
usual Unix README file doesn't include the information that you need.

> I received some messages regarding not using the source files completely,
> therefore let me explain a little further.  I need to build the sources in a
> y2k environment such that I can run a few quick programs which will probably
> take only 10 minutes total, such that I can test the libraries under all the
> different operating systems to determine whether gcc is year 2000 compliant.
> (I realize I'll probably receive some mail testifying that the gnu shareware
> is all compliant and created that way, but without a specific vendor
> which can be held accountable it must all be tested.)

I really don't understand what you are trying to accomplish.  You say
that you need to ``test the libraries under all the different
operating systems to determine whether gcc is year 2000 compliant''.
Where does DJGPP fits into this scheme?  DJGPP only produces programs
that can run on MS-DOS and MS-Windows; if your list of ``different
operating systems'' includes other OSes, DJGPP is not good for this
job.

Also, DJGPP's library pulls some tricks to make DOS/Windows look more
Posix-like, and some of these tricks might affect your testing.  You
will need to make sure that the features you are testing indeed
characterize gcc and the target OS and not the DJGPP library
internals.

- Raw text -