ABI isn't compatible, so bump PORTREVISION in consumers.
No ACC report for this version. Current one for Git is 341 commits ahead -> unreliable.
Changes: https://chromium.googlesource.com/webm/libvpx/+/v1.4.0
Differential D2570
multimedia/libvpx: update to 1.4.0 jbeich on May 16 2015, 11:53 PM. Authored by Tags None Referenced Files
Details ABI isn't compatible, so bump PORTREVISION in consumers. IMPORTANT: It requires more care than the actual update.
No ACC report for this version. Current one for Git is 341 commits ahead -> unreliable. Changes: https://chromium.googlesource.com/webm/libvpx/+/v1.4.0 libvpx build on 8.4R amd64, 9.3R i386, 10.1R amd64, 10.1R i386, 11.0C i386. Not much else i.e., the following risks are ignored for being [hard to test]:
Diff Detail
Event TimelineThis comment was removed by bapt. Comment Actions There was no exp-run as I'm not sure it's even required. The number of consumers isn't that big compared to, say, graphics/png. portmgr is supposed to know better when to weigh risks against the cost of exp-run. Also, exp-run may not catch all cases of ABI breakage e.g., in leaf ports. Comment Actions
No, lack of resources and it'd be close to local exp-run. Comment Actions graphics/*gd VPX=on failure went unnoticed. Anyway, those're a fallout from Can you re-try with updated diff + OPTIONS_SET=VPX in make.conf ? Comment Actions Unrelated to the libvpx update, but some ports do not respect DISABLE_MAKE_JOBS / MAKE_JOBS_NUMBER : root 35699 0.0 0.0 14648 3700 2 I+J 15:00 0:00.05 gmake -j32 -C /wrkdirs/usr/ports/www/libxul/work/mozilla-esr31/obj-x86_64-portbld-freebsd10.1 Comment Actions Thanks. Green now. Back to waiting for approval(s) now. gecko bugs are indeed unrelated. I remember this one being tricky and it may not have been completely fixed due to configure/client.mk/mach chaining involved. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=184630
MAKE_JOBS_NUMBER=1 should work. Undefined -jN build leads to undefined behavior. I'm not sure about adding a workaround for bsd.port.mk bug like USES=waf and USES=ninja did. Also,... # Automatically add -jN to make flags if not defined. N defaults to number of cores. ifeq (,$(findstring -j,$(MOZ_MAKE_FLAGS))) cores=$(shell $(PYTHON) -c 'import multiprocessing; print(multiprocessing.cpu_count())') MOZ_MAKE_FLAGS += -j$(cores) endif cpu_count() should probably return the number of available cores after subtracting user overrides via cpuset(1). As the python function prefers sysconf(3) one could divorce _SC_NPROCESSORS_ONLN from _SC_NPROCESSORS_CONF like Linux did. Comment Actions @ashish granted approval. Do I need to wait for portmgr, use the blanket or ask maintainers of the patched ports separately?
Comment Actions Rebase after rP387082 to make sure keywords/props in patches are gone: multimedia/libvpx/files/patch-nestegg_halloc_src:2:$FreeBSD$ multimedia/libvpx/files/patch-nestegg_halloc_src:19:$FreeBSD$ multimedia/libvpx/files/patch-build_make_configure.sh:11:$FreeBSD$ |