|
From: Vibhu M. <vi...@ho...> - 2022-10-01 07:41:01
|
This is a fix to some configure files to deal with Windows line endings. Processor: Intel Xeon X5647, x64-based processor System: Windows 10 64-bit, 6 GB RAM (I haven't yet gotten access to Windows 32-bit, but plan to) Cygwin (both 64-bit and 32-bit) targetting mingw 32-bit I've got lisp.exe and lispinit.mem and am seeing what it'll take to get to having a base/ directory. I'll discuss the failing make targets i18n, syscalls. Notice the extraneous carriage returns in lines 9, 11 of the attached extract of build/syscalls/config.log . They come from modules/syscalls/configure near "cl_cv_clisp_version=...". Sed's second expression does nothing because sed's stdin has a carriage return between the double quote and line feed. Changing the expression to allow an optional carriage return like this: 's/"\r\?$//' solves the problem. There are some other similar places in that same configure script, which I also changed in exactly the same way. See attached diff. Moreover, I believe all the scripts named modules/*/configure will need the same lines fixed. If these scripts are generated, then perhaps the generator can change instead. Note: This problem doesn't occur when building a Cygwin binary, only a mingw binary. That makes sense. The Cygwin binary presumably prints Unix line-endings, for which the original sed expression works just fine. |