[Bug 1827225] Re: AppVeyor mingw builds broken (claiming missing epicsTempFile.obj)

[Ralph Lange via Core-talk <core-talk@aps.anl.gov>]

I know. It's not make. (At least not alone.)

On the failing 8.1.0 choco MinGW install, using make 4.2.1 (from Andrew
/ old EPICS site) that is known to work with all kinds of compilers
(including cygwin on AppVeyor) does not change the failure. (@Andrew: I
tested this today in https://ci.appveyor.com/project/ralphlange/epics-
base-5e851/builds/24250315)

On my local Windows box the native MinGW-w64/MSYS install with gcc 8.3.0
and make 4.2.1 works fine.

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1827225

Title:
  AppVeyor mingw builds broken (claiming missing epicsTempFile.obj)

Status in EPICS Base:
  Fix Committed
Status in EPICS Base 3.15 series:
  Fix Committed
Status in EPICS Base 7.0 series:
  Fix Committed

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/epics-base/modules/libcom/src/O.win32-x86-mingw'
  mingw32-make[4]: *** No rule to make target 'epicsTempFile.obj', needed by 'e_flex.exe'.  Stop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1827225/+subscriptions