Yes, this is the case. It seems there is no solution for this problem, besides making these packages not to rely on the affected links when used on Windows. In OpenSSL this is handled by the perl Configure script. (I've just tried it on an OpenSSL .tgz unpacked on Windows).
Brgds, Viktor On Wed, Jan 21, 2009 at 9:58 AM, Przemyslaw Czerpak <dru...@acn.waw.pl>wrote: > On Wed, 21 Jan 2009, Szak�ts Viktor wrote: > > Hi Viktor, > > > Thanks for your suggestion. It seems it also doesn't create > > those files, but I've just retried, and the whole issue seems > > to be worked around by the OpenSSL build process, so this > > specific problem is now solved. 7z is a good choice for > > this job as I use it anyway (but I have to keep in mind it's > > also good for tar :). > > Maybe I'm wrong but isn't the file creating problems for you > softlinks which does not exists in MS-Windows file systems > so they simply cannot be created on this architecture and > your results with different tar decompressors are only > workarounds for it? > > best regards, > Przemek > _______________________________________________ > Harbour mailing list > Harbour@harbour-project.org > http://lists.harbour-project.org/mailman/listinfo/harbour >
_______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
