Subj : GCC confusion .. To : Mike Luther From : Bob Jones Date : Wed Jul 30 2003 10:14 pm ... ML> Well here cometh a complete packaged update install of ML> GCC .. as GCC321 and, obviously, it's a newer and ML> whatever version. Yep, in reading the docs for it ML> here, it PLAINLY states one should not second guess the ML> path for the automated EMX install of whatever ... or ML> .. it will get put in #:\emx\emx directory .. which is *NOT* what we want. ... Yup.... ML> Since this is whole GCC deal is an unopened treasure ML> box in addition to Watcom C++ V11 updated from paid for ML> play, and in addition to VAC++ here, what is the best ML> course of action? Good question. I've got the beta of Open Watcom installed (right before they released 1.0), and need to upgrade that to the 1.0 version. 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.... ML> The PATH statement to EMX is not the #:\emx\emx at all. ML> It is of the, I think, correct form #:\emx with all ML> the \bin and so on under it. All of the GCC parameters ML> for EMX, I think (THINK?), came in a block of stuff in ML> the CONFIG.SYS after it was installed as PJGCC work? ML> Thus, one would suppose that the applications which ML> depend on it are all flat dumb and happy with what was there, no? 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.... ML> So is the smart thing to do is to whomp out the entire ML> #:\emx\emx directory setup, whomp out the entire ML> CONFIG.SYS line segment which has to do with what the ML> compiler put there? Then next go whomp out the entire ML> #:\PJGCC directory which is there? We then run ML> UNIMAINT and maybe CHECKINI and so on and watch for ML> fireworks? Then .. start all over with the new GCC321 install routine? Good question.... ML> Ever seen a puppy going round and round a turtle ML> contemplating something? Ever notice the difference in ML> the puppy's demeanor if the turkle is a SNAPPING turkle? ML> Advice? Reload OS and start from sratch?!?!?!? 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.... Take care.... Bob Jones, 1:343/41 --- Maximus/2 3.01 * Origin: Top Hat 2 BBS (1:343/41) .