Sleep well; OS/2's still awake! ;)
Well here cometh a complete packaged update install of...
GCC .. as GCC321 and, obviously, it's a newer and
whatever version. Yep, in reading the docs for it
here, it PLAINLY states one should not second guess the
path for the automated EMX install of whatever ... or
.. it will get put in #:\emx\emx directory .. which is *NOT* what we want.
Since this is whole GCC deal is an unopened treasure
box in addition to Watcom C++ V11 updated from paid for
play, and in addition to VAC++ here, what is the best
course of action?
The PATH statement to EMX is not the #:\emx\emx at all.
It is of the, I think, correct form #:\emx with all
the \bin and so on under it. All of the GCC parameters
for EMX, I think (THINK?), came in a block of stuff in
the CONFIG.SYS after it was installed as PJGCC work?
Thus, one would suppose that the applications which
depend on it are all flat dumb and happy with what was there, no?
So is the smart thing to do is to whomp out the entire
#:\emx\emx directory setup, whomp out the entire
CONFIG.SYS line segment which has to do with what the
compiler put there? Then next go whomp out the entire
#:\PJGCC directory which is there? We then run
UNIMAINT and maybe CHECKINI and so on and watch for
fireworks? Then .. start all over with the new GCC321 install routine?
Ever seen a puppy going round and round a turtle
contemplating something? Ever notice the difference in
the puppy's demeanor if the turkle is a SNAPPING turkle?
Advice?
Also, I'm now trying to get the GCC 3.2.1 package fixed
up and running here.... I noticed the install script
didn't give me the environment setup the way I need it....
I have fun, cause I have EMX loaded on my boot partion (normally C:),
and I do *not* want the compiler on that partition due
to space issues (although it would probably work
out....
Yes, I need to re-install the GCC 3.2.1 because I was
"testing" and need to place it else where....
When you figure it out, let me know.... Then maybe I
can try to get the Maximus / Squish / SqaFix ports
that we're (attempting to) compiling using GCC on
Linux to see if I can get that version to also compile
(and run) under OS/2 using GCC 3.2.1.... That would
be nice.... But it could get interesting....
We're close to being able to compile SqaFix under Linux....
Still working out code clean up so that SqaFix can be
GPL'ed. Able to run test compiles of that code using
GCC under OS/2 would be nice....
Sleep well; OS/2's still awake! ;)
So is the smart thing to do is to whomp out the entire #:\emx\emx
directory setup, whomp out the entire CONFIG.SYS line segment which
has to do with what the compiler put there? Then next go whomp out
the entire #:\PJGCC directory which is there? We then run UNIMAINT
and maybe CHECKINI and so on and watch for fireworks? Then .. start
all over with the new GCC321 install routine?
Ever seen a puppy going round and round a turtle contemplating
something? Ever notice the difference in the puppy's demeanor if the
turkle is a SNAPPING turkle?
Advice?
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,040 |
Nodes: | 17 (0 / 17) |
Uptime: | 32:17:26 |
Calls: | 501,924 |
Calls today: | 13 |
Files: | 104,428 |
D/L today: |
31,733 files (4,799M bytes) |
Messages: | 299,124 |
Posted today: | 3 |