@@ -32,15 +32,15 @@ PREREQUISITES
3232
3333 Using Watcom C:
3434 Required
35- * Open Watcom : http ://www. openwatcom.org /
36- * Open Watcom V2 : http ://open-watcom. github.io /open-watcom/ (git repo)
37- http ://sourceforge.net/projects/openwatcom/ (binaries download)
35+ * Open Watcom : https ://sourceforge.net/projects/ openwatcom/
36+ : https ://github.com /open-watcom/open-watcom-1.9
37+ * Open Watcom V2 : https ://github.com/open-watcom/open-watcom-v2
3838
3939
4040 Using Microsoft Visual C++:
4141 Required
4242 * Visual C++ : You can get a free community version via this web page:
43- https://www. visualstudio.com/vs/community/
43+ https://visualstudio.microsoft .com/vs/community/
4444 Download Visual Studio for Windows Desktop. Visual C++ is part
4545 of Visual Studio. Out of the box compilation for 64-bit
4646 applications is supported since version 2012.
@@ -184,8 +184,8 @@ LARGE FILE SUPPORT
184184 Disable LFS:
185185 make clean install LFS=
186186
187- The gcc compiler from the mingw.org project does not support LFS.
188- It is advised to use the mingw -w64 compiler tool chain for LFS on
187+ The gcc compiler from the MinGW project does not support LFS.
188+ It is advised to use the MinGW -w64 compiler tool chain for LFS on
189189 32 bit Windows.
190190
191191
@@ -240,28 +240,28 @@ DOCUMENTATION
240240
241241WINDOWS 32 BIT PORT
242242
243- Using Mingw <http ://www. mingw.org>, or MinGW-w64
244- <http ://mingw-w64.sourceforge.net >.
243+ Using Mingw <https ://osdn.net/projects/ mingw/>,
244+ or MinGW-w64 <https ://www. mingw-w64.org/ >.
245245
246- I advise to use mingw -w64, because mingw -w64 has support for
247- Large File Support (LFS), and mingw doesn't. LFS is the ability to
246+ I advise to use MinGW -w64, because MinGW -w64 has support for
247+ Large File Support (LFS), and MinGW doesn't. LFS is the ability to
248248 read/write files larger than 2GB or 4GB on a 32 bit operation system.
249249 LFS also makes processing files on network drives more reliable. I have
250250 had a problem report that output files were not always written when files
251251 on a network drive were concurrently processed. By switching from
252- mingw to mingw -w64 the problem was solved.
252+ MinGW to MinGW -w64 the problem was solved.
253253 Earlier I got a problem report of accessing small files on a Windows
254254 network drive from Debian Linux. Here also the solution was LFS.
255255 Since dos2unix 6.0.4 (2013-12-30) I build the binary win32 packages
256- with mingw -w64.
256+ with MinGW -w64.
257257
258- I am using the MSYS2 project <http ://sourceforge.net/projects/ msys2/>
258+ I am using the MSYS2 project <https ://www. msys2.org />
259259 which includes the MinGW-w64 compiler.
260260
261261 The MSYS(2) environment is required for building dos2unix with MinGW(-w64).
262262
263263
264- Type these commands to build with mingw (-w64):
264+ Type these commands to build with MinGW (-w64):
265265
266266 make clean
267267 make
@@ -283,16 +283,16 @@ WINDOWS 32 BIT PORT
283283
284284 The win32 binaries built with MinGW32 are packed with a patched version of
285285 MinGW's libintl-8.dll that has builtin support for relocation. See also
286- http ://waterlan.home.xs4all.nl/libintl.html and
287- http ://sourceforge.net/p/mingw/bugs/1808/
286+ https ://waterlan.home.xs4all.nl/libintl.html and
287+ https ://sourceforge.net/p/mingw/bugs/1808/
288288 The MSYS2 project has the relocation patch already included.
289289
290290
291291WINDOWS 64 BIT PORT
292292
293293 To compile a version for 64 bit Windows, get the Mingw-w64 compiler
294- <http ://mingw-w64.sourceforge.net >.
295- I am using the MSYS2 project <http ://sourceforge.net/projects/ msys2/>
294+ <https ://www. mingw-w64.org/ >.
295+ I am using the MSYS2 project <https ://www. msys2.org />
296296 which includes the MinGW-w64 compiler.
297297
298298 The MSYS2 environment is required for building dos2unix with MinGW-w64.
@@ -315,7 +315,7 @@ WINDOWS 64 BIT PORT
315315DOS PORT, 32 BIT
316316
317317 To compile a version for DOS, get the DJGPP compiler
318- <http ://www.delorie.com/djgpp/>, and use makefile djgpp.mak.
318+ <https ://www.delorie.com/djgpp/>, and use makefile djgpp.mak.
319319 DJGPP 2.03 gcc >= 4.6 seems to cause problems. Crashes of gcc itself,
320320 or crashing dos2unix binaries (seen in DOSBox and DOSEMU).
321321 Use DJGPP 2.03 gcc <= 4.5.3.
0 commit comments