[MacPorts] #60283: octave: automake-1.15: command not found

MacPorts noreply at macports.org
Sun Apr 5 09:51:50 UTC 2020


#60283: octave: automake-1.15: command not found
-------------------------+---------------------------------
  Reporter:  ryandesign  |      Owner:  MarcusCalhoun-Lopez
      Type:  defect      |     Status:  assigned
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.6.2
Resolution:              |   Keywords:
      Port:  octave      |
-------------------------+---------------------------------

Comment (by ryandesign):

 I think the problem was introduced in
 [17b7c5e10202901bdd9382ed62b5b22b7b7e38bf/macports-ports]. That added this
 command:

 {{{
     reinplace \
         "s|__MACPORTS_JAVA_VERSION__|${java_version}|g" \
         ${worksrcpath}/Makefile.in \
         ${worksrcpath}/scripts/java/module.mk
 }}}

 The problem is that scripts/java/module.mk is one of the prerequisites of
 Makefile.in (along with all of the other .mk files). So if the `reinplace`
 modifies Makefile.in at 12:00:00 and scripts/java/module.mk gets modified
 at 12:00:01, then `make` sees Makefile.in's dependency module.mk as newer
 than Makefile.in and wants to run `automake` to rebuild Makefile.in. But
 if they both happen to get modified before the clock advances to the next
 second (more likely the faster the disk is), then the build succeeds.

 As I said [comment:8 above], a Portfile developer must either modify the
 original files and autoreconf to regenerate the generated files, or must
 modify the generated files. Not both! The fix is not to modify module.mk.

-- 
Ticket URL: <https://trac.macports.org/ticket/60283#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list