Hello Don,
I always install mingw at "C:\mingw{32,64}" so I don't remember seeing
this problem before.
Regarding your comment about "make" being baked into the build process,
we try to always use MAKE as a variable defined in Makedefs under the top
level directory for the reason you mentioned; to make it easy to switch to
any "make". If there are places were make is hard-coded then we should fix
that.
Cheers,
Jafar
On Thu, Nov 5, 2015 at 11:38 AM, Don Ward <[email protected]> wrote:
> The problem is at line 2 of …/unicon/config/unix/Config/ipllib.mak,
> which says
> if grep LoadFunc ../../src/h/define.h >/dev/null; then $(MAKE) Cfun; fi
> In my case $(MAKE) expanded to /c/Program Files
> (x86)/mingw-w64/i686-5.2.0-posix-dwarf-rt_v4-rev0/mingw32/bin/make
> and make complained about an illegal ‘(‘ when it executed the makefile. As
> far as I can tell this is the only instance of the problem, but there may
> be others.
>
> When I installed mingw I used the default path, which is /c/Program Files
> (x86)/mingw-w64/… .
> The workaround is to install mingw to a path with no spaces and no
> parentheses. Then it works fine.
>
> On another topic, the name “make” is rather baked in to the build process:
> i.e. if your make executable happens to be called mingw-make.exe (as mine
> was) then things don’t work so well
>
> Don
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Unicon-group mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/unicon-group
>
>
------------------------------------------------------------------------------
_______________________________________________
Unicon-group mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/unicon-group
