| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | GCC confusion .. |
A while ago and far away I sought out the PJGCC site and checked all the
options I thought I ought to have. I made the source archive directory for
what would come and downloaded all of what it 'put together' for me into
that directory. With it came the needed EMX files, but ..
1.) I'd already installed EMX and run the 'update' for it for the 4.5
or whatever the needed revision was for other things ...
2.) I read (at) the docs and didn't catch something about EMX until ..
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.
You betcha .. Mikey puppy goes looking in the #\emx directory and LO! There
it is from the old install; #:\emx\emx.. gloom. So puppy goes and sniffs
in the CONFIG.SYS file and sure enough, here we are all over the place in
it #:\emx\emx there too in re what the install for the compiler put
there... sigh.
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?
;)
--> Sleep well; OS/2's still awake! ;)
Mike {at} 1:117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)SEEN-BY: 633/267 270 @PATH: 117/3001 100 106/1 2000 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.