AppVeyor mingw builds broken (claiming missing epicsTempFile.obj)
Bug #1827225 reported by
Ralph Lange
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | ||
---|---|---|---|---|---|---|
EPICS Base | Status tracked in 7.0 | |||||
3.15 |
Fix Released
|
Medium
|
Ralph Lange | |||
7.0 |
Fix Released
|
Medium
|
Ralph Lange |
Bug Description
It looks like the epicsTempName() commit (6201d37 * 3.15) broke the mingw builds.
E.g. on AppVeyor
mingw32-make[4]: Leaving directory 'C:/projects/
mingw32-make[4]: *** No rule to make target 'epicsTempFile.
Changed in epics-base: | |
status: | Incomplete → In Progress |
Changed in epics-base: | |
assignee: | nobody → Ralph Lange (ralph-lange) |
importance: | Undecided → Medium |
To post a comment you must log in.
Both my native MinGW builds (windows-x64-mingw with gcc 7.1.0 from Strawberry Perl 5.26.2) and cross-builds from RHEL-7.6 still work fine. Have you seen any error messages from when epicsTempFile.cpp is being built? This looks similar to my Solaris build failure on Jenkins, neither compiler appears to be printing an error when compiling that file, they just don't generate any output.
Hmm, there are actually no object files at all in the src/libCom/O.<host> directory, is this perhaps a compiler problem instead? IIRC the epicsTempFile.cpp source just happens to be the first one that gets compiled, so it just *looks* like that may be the cause. I suspect my Solaris compilers may have died (see the issue with the procServ build recently), and I get the exact same symptoms on Windows if I try to do a native windows-x64 build without having configured the shell window properly for MSVC.