[Bug 235314] [patch] Fix python build dependency for emulators/open-vm-tools

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Jan 30 11:29:54 UTC 2019


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235314

            Bug ID: 235314
           Summary: [patch] Fix python build dependency for
                    emulators/open-vm-tools
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Individual Port(s)
          Assignee: jpaetzel at FreeBSD.org
          Reporter: bugzilla.freebsd at omnilan.de
             Flags: maintainer-feedback?(jpaetzel at FreeBSD.org)
          Assignee: jpaetzel at FreeBSD.org

Created attachment 201526
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=201526&action=edit
Fix Python build dependency for emulators/open-vm-tools

Currently, running 'make' in emulators/open-vm-tools-nox11 fails:
make
===>   open-vm-tools-nox11-10.3.0_1,2 depends on package: autoconf>=2.69 -
found                                                 
===>   open-vm-tools-nox11-10.3.0_1,2 depends on package: automake>=1.16.1 -
found
===>   open-vm-tools-nox11-10.3.0_1,2 depends on executable: libtoolize - found
===>   open-vm-tools-nox11-10.3.0_1,2 depends on package: pkgconf>=1.3.0_1 -
found
===>   open-vm-tools-nox11-10.3.0_1,2 depends on shared library: libmspack.so -
found (/usr/local/lib/libmspack.so)
===>   open-vm-tools-nox11-10.3.0_1,2 depends on shared library: libdnet.so -
found (/usr/local/lib/libdnet.so)
===>   open-vm-tools-nox11-10.3.0_1,2 depends on shared library: libfuse.so -
found (/usr/local/lib/libfuse.so)
===>   open-vm-tools-nox11-10.3.0_1,2 depends on shared library: libintl.so -
found (/usr/local/lib/libintl.so)
===>   open-vm-tools-nox11-10.3.0_1,2 depends on shared library: libglib-2.0.so
- found (/usr/local/lib/libglib-2.0.so)
===>   open-vm-tools-nox11-10.3.0_1,2 depends on shared library: libintl.so -
found (/usr/local/lib/libintl.so)
===>  Configuring for open-vm-tools-nox11-10.3.0_1,2
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'config'.
libtoolize: copying file 'config/ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: copying file 'm4/libtool.m4'
libtoolize: copying file 'm4/ltoptions.m4'
libtoolize: copying file 'm4/ltsugar.m4'
libtoolize: copying file 'm4/ltversion.m4'
libtoolize: copying file 'm4/lt~obsolete.m4'
configure.ac:198: installing 'config/compile'
:
--- vmware_namespace_cmd-namespacetool.o ---
cc -DPACKAGE_NAME=\"open-vm-tools\" -DPACKAGE_TARNAME=\"open-vm-tools\"
:
mv -f .deps/vmware_namespace_cmd-namespacetool.Tpo
.deps/vmware_namespace_cmd-namespacetool.Po
--- vmware-namespace-cmd ---
/bin/sh ../libtool  --tag=CC    --mode=link cc  -O2 -pipe -march=ivybridge
:
m -lcrypt -lthr -lglib-2.0 -lintl -Wl,-rpath -Wl,/usr/local/lib
Making all in scripts
--- poweroff-vm-default ---
:
cp ../scripts/common/statechange.sh poweron-vm-default
Making all in services                                                          
--- all-recursive ---
Making all in vmtoolsd                                                          
--- svcSignals.h ---
--- svcSignals.c ---
--- svcSignals.h ---
glib-genmarshal --header ../../services/vmtoolsd/svcSignals.gm >  svcSignals.h
|| (rm -f svcSignals.h && exit 1)
--- svcSignals.c ---
glib-genmarshal --body ../../services/vmtoolsd/svcSignals.gm >  svcSignals.c ||
(rm -f svcSignals.c && exit 1)
--- svcSignals.h ---
env: /usr/local/bin/python2.7: No such file or directory
--- svcSignals.c ---
env: /usr/local/bin/python2.7: No such file or directory
--- svcSignals.h ---
*** [svcSignals.h] Error code 1

make[4]: stopped in
/usr/local/ports-wrktree/emulators/open-vm-tools-nox11/work/open-vm-tools-stable-10.3.0/open-vm-tools/service$
/vmtoolsd

The attached diff adds python as build dependency, which makes building this
port sucessful on clean/fresh hosts.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list