opencv3: Applying patches forever

[andrewhw (Andrew Wright)]

Having run "port upgrade outdated", opencv3 requires an update.

It got as far as "Applying patches to opencv3" and stayed there for more then 24 hours.

I interrupted, cleaned, and tried again -- same deal.

Looking at running processes (using ps) returns nothing using CPU.

Seems to be blocked waiting on some event that never happens (rather than being in an infinite loop, as there is no CPU time being consumed).

Is anyone else seeing this?

Any ideas how to debug this problem?

[andrewhw (Andrew Wright)]

I just realized that there is a "verbose mode" that will issue the command lines being run.

The problem is a malformed patch.

Once in directory:

"/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_opencv3/opencv3/work/opencv3-3.4.16"

the command

/usr/bin/patch -p0 < '/opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports/graphics/opencv3/files/patch-find-openexr.diff'

is being run.

When run at the command line, patch print a prompt "File to patch:" and is waiting (forever) for standard input.

[andrewhw (Andrew Wright)]

The "opencv3-3.4.16" directory where patch is being run from is empty.

[andrewhw (Andrew Wright)]

I am guessing that the directory "opencv3-3.4.16" is actually supposed to be a symlink to the companion "opencv-3.4.16" directory?

[kencu (Ken)]

there was a change in base recently.

a few ports need to have their "worksrcdir" specified, if the extracted distfile doesn't match ${name}-${version}. This one doesn't match, so will need to be fixed.

Something like this in the Portfile will likely fix it

worksrcdir opencv-${version}

[jmroot (Joshua Root)]

Same problem as #66861.

[kencu (Ken)]

In d967da4c27ad30e0588feaae8a394fc1cc5af814/macports-ports (master):

opencv3: fix worksrcdir

closes: #66941