Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > openwatcom.users.c_cpp > #3489
| From | Paul S. Person <psperson@ix.netscom.com.invalid> |
|---|---|
| Newsgroups | openwatcom.users.c_cpp |
| Subject | Re: install version 2? |
| Date | 2017-04-06 09:33 -0700 |
| Organization | OpenWatcom |
| Message-ID | <36rcec50dq9lclnba3ef8ua9bcd0t6s3dc@4ax.com> (permalink) |
| References | <oc4od7$15d$1@www.openwatcom.org> |
On Wed, 5 Apr 2017 17:51:03 -0700, "David" <nope@dont.invalid> wrote: >So using 1.9 getting crash on a build, wanting to try V2, is there an >installer for that, (see uninstall), or do I just move all the folders over >to where 1.9 is now (of course saving 1.9 before replacing it). I have doubts about that. V2 is done by a different group of people, so it is possible that that will not work. Then again, it might. On the gripping hand, there was at least one version of Watcom (11, IIRC) which, when simply installed /over/ the prior version, did not update the libraries. This became apparent when using C++: the internal model had changed and all sorts of otherwise-invisible items popped up in linker errors. So I would uninstall 1.9 completely, and then install v2 completely over it. Or just install v2 side-by-side. But I wouldn't expect this to fix a crash on a build. Although you /might/ have found a new problem, chances are much better that your code is the problem. That has always been my experience. -- "Nature must be explained in her own terms through the experience of our senses."
Back to openwatcom.users.c_cpp | Previous | Next — Previous in thread | Next in thread | Find similar
install version 2? "David" <nope@dont.invalid> - 2017-04-05 17:51 -0700 Re: install version 2? Paul S. Person <psperson@ix.netscom.com.invalid> - 2017-04-06 09:33 -0700 Re: install version 2? Hans-Bernhard Bröker <broeker@physik.rwth-aachen.de> - 2017-04-06 19:02 +0200 Re: install version 2? "Mat Nieuwenhoven" <mnieuw@dontincludethis.zap.a2000.nl> - 2017-04-07 13:43 +0200
csiph-web