search

auriocus / VecTcl

Numeric array and linear algebra extension for Tcl
http://auriocus.github.io/VecTcl
Other
34 stars 9 forks source link

Weird build error on macOS 10.8–10.9: /bin/sh: i686-w64-mingw32-gcc: command not found #11

Open barracuda156 opened 1 year ago

barracuda156 commented 1 year ago

On these two systems wrong choice of compiler happens: i686-w64-mingw32-gcc is invoked, which is obviously wrong, and the build fails.

Logs: 10.9: https://build.macports.org/builders/ports-10.9_x86_64-builder/builds/214741/steps/install-port/logs/stdio 10.8: https://build.macports.org/builders/ports-10.8_x86_64-builder/builds/117791/steps/install-port/logs/stdio

auriocus commented 1 year ago

Probably an issue with tcl.m4. It has not been updated since some time. Does the same problem arise with the newest sampleextension? https://wiki.tcl-lang.org/page/SampleExtension

auriocus commented 1 year ago

Also, the log indicates that the compiler flags request compilation for 64 bit (-arch x86_64), while the OS runs on 32 bit. Are you intentionally cross-compiling?

barracuda156 commented 1 year ago

Also, the log indicates that the compiler flags request compilation for 64 bit (-arch x86_64), while the OS runs on 32 bit. Are you intentionally cross-compiling?

Those are on build bots, I cannot verify locally. But no, Macports never cross-compiles, and I believe, all OS on build bots are run as x86_64, with an exception of 10.6.8, which exists in two varians, i386 and x86_64.

Something is wrong with configure scripts of VecTcl, it seems. This error is not something we ever see, AFAICT.

auriocus commented 1 year ago

Can you access the config.log from the configure run? That might give an indication. The configure scripts are derived from the TEA build system. Specifically, they were copied at some time in the past from these two repositories: https://core.tcl.tk/sampleextension/ and https://core.tcl-lang.org/tclconfig/. Hence, my suggestion to update the tclconfig folder with the most recent version of tclconfig and check if the problem persists.

auriocus commented 1 year ago

I becane sceptical about the 64 bit issue, because in your log file it says "OS darwin/13.4.0 (macOS 10.9.5) arch i386", but the CFLAGS that are passed in contain "-arch x86_64". Where does this flag come from? Does it look like this also for other builds?

barracuda156 commented 1 year ago

I becane sceptical about the 64 bit issue, because in your log file it says "OS darwin/13.4.0 (macOS 10.9.5) arch i386", but the CFLAGS that are passed in contain "-arch x86_64". Where does this flag come from? Does it look like this also for other builds?

In that case it simply stands for Intel. You will see the same on 64-bit-only macOS, example: https://build.macports.org/builders/ports-12_x86_64-builder/builds/54661/steps/install-port/logs/stdio