SCOUG-HELP Mailing List Archives
Return to [ 26 |
October |
2007 ]
<< Previous Message <<
>> Next Message >>
Content Type: text/plain
Hi Steven,
I'm about to upgrade SM from 111 to 115 (the
Weilbacher build). For quite some time, probably even
going back a ways into Moz versions, I just dropped
LIBC05 and GCC322 in there for the install, and
everything was seemingly just fine. It is quite
possible I could continue doing that for awhile, and
have it work. But I found these in my d/l directory
-- not sure exactly when I picked them up or why, but
probably for good reason and likely intended for SM.
6-11-07 10:35p 32,801 0 a--- gcc335.dll
6-11-07 10:53p 48,142 0 a--- libc06.dll
6-11-07 10:53p 48,142 0 a--- libc061.dll
6-11-07 10:53p 157,124 0 a--- libc062.dll
6-11-07 10:53p 1,349,060 0 a--- libc063.dll
So I thought I'd ask what is most appropriate for
current issue SM ? Should I change over to GCC335 +
LIBC063 . . . or are the presence of more than one of
these indicated ?
I think I may have already figured out a related
question. One or the other of these (probably GCC,
but I don't recall) is distributed in a pkg. of 1.5M
size or larger, and an elaborate directory structure,
but we don't need to install the whole dang mess (?),
just take out the solitary DLL and drop it where it's
needed ?
Jordan
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 26 |
October |
2007 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
|