Message-Id: <3.0.6.32.19990214203010.008345c0@pop.netaddress.com> X-Sender: pderbysh AT pop DOT netaddress DOT com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 14 Feb 1999 20:30:10 -0500 To: djgpp AT delorie DOT com From: Paul Derbyshire Subject: Re: Re[2]: Problem with djgpp using Rhide 1.4 In-Reply-To: <8923.990214@gmx.net> References: <004a01be5858$4739f6e0$3a01e8d4 AT default> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Reply-To: djgpp AT delorie DOT com At 10:10 PM 2/14/99 +0100, you wrote: >Thanks, i searched and found NO lib named in that way, exept for one >that was called libstdcxx.a ... i renamed it to libstdcx.a and now it seems >to work ... well ... at least i hope so... or was that libstdcxx.a >something complete different, that i had better not touched ??? That's the right library. It must have had an SFN like libstd~1.a instead of libstdcx.a. Windows shouldn't by default use the damn ~1's unless there's an SFN name clash. Instead to make it get this behavior you need to muck with the registry and change a key that isn't documented by Microsoft, and then it has the bug that sometimes if you have a file with an LFN and a particular SFN, and then you go to create a new file with a name that's the first file's SFN, it will go to overwrite instead of give the new file an LFN of the name you chose and an SFN with the ~1 ending like it should. If you unzip the JDK from Sun for example, a foobarbz_small.gif extracts, then a foobarbz.gif extracts and overwrites the first instead of coming out with the SFN foobar~1.gif... and this happens several times. -- .*. "Clouds are not spheres, mountains are not cones, coastlines are not -() < circles, and bark is not smooth, nor does lightning travel in a `*' straight line." ------------------------------------------------- -- B. Mandelbrot |http://surf.to/pgd.net _____________________ ____|________ Paul Derbyshire pderbysh AT usa DOT net Programmer & Humanist|ICQ: 10423848|