December 2012 - macports-tickets - lists.macosforge.org

[MacPorts] #37402: phantomjs: cc1plus: error: unrecognized command line option "-mavx"
by MacPorts 03 Jan '13

03 Jan '13

#37402: phantomjs: cc1plus: error: unrecognized command line option "-mavx" --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: snowleopard | Port: phantomjs --------------------------+-------------------------------- While phantomjs 1.8.0 builds on the Lion and Mountain Lion buildbots, it fails to build on the Snow Leopard buildbot: https://build.macports.org/builders/buildports-snowleopard- x86_64/builds/13259/steps/compile/logs/stdio {{{ g++ -c -pipe -mavx -O2 -Wall -W -I../../../mkspecs/macx-g++ -I. -o avx.o avx.cpp cc1plus: error: unrecognized command line option "-mavx" }}} This was [comment:ticket:34479:5 observed with 1.7.0] as well. -- Ticket URL: <https://trac.macports.org/ticket/37402> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #37463: llvm-3.2 does not build / universal variants semantics should be changed
by MacPorts 03 Jan '13

03 Jan '13

#37463: llvm-3.2 does not build / universal variants semantics should be changed -----------------------+---------------------- Reporter: vince@… | Owner: jeremyhu Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: universal | Port: llvm-3.2 -----------------------+---------------------- When building llvm-3.2 I get this error: {{{ lvm[1]: Compiling llvm-config.cpp for Release+Debug+Asserts build if /usr/bin/clang++ -I/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/include -I/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config -D_DEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -I/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts -O3 -g -fvisibility-inlines-hidden -fno-exceptions -fno-rtti -fno-common -Woverloaded-virtual -Wcast-qual -m64 -pedantic -Wno-long-long -Wall -W -Wno-unused-parameter -Wwrite- strings -Wcovered-switch-default -c -MMD -MP -MF "/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.d.tmp" -MT "/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.o" -MT "/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.d" llvm-config.cpp -o /opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.o ; \ then /bin/mv -f "/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.d.tmp" "/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.d"; else /bin/rm "/opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.d.tmp"; exit 1; fi llvm-config.cpp:45:10: fatal error: 'LibraryDependencies.inc' file not found #include "LibraryDependencies.inc" ^ 1 error generated. rm: /opt/local/var/macports/build/_Users_vincent_Developpement_Macports_trunk_dports_lang_llvm-3.2/llvm-3.2/work/llvm-3.2.src/tools /llvm-config/Release+Debug+Asserts/llvm-config.d.tmp: No such file or directory }}} Besides, the ‘universal’ variant should not mean building a universal compiler, but building a compiler than can compile for both i386/x86-64, which is the default case. The classical meaning of ‘universal’ should be transferred to some other variant. -- Ticket URL: <https://trac.macports.org/ticket/37463> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 8

[MacPorts] #37103: ImageMagick 6.8.0 does not correctly display SVG files on PPC (here Leopard 10.5.8)
by MacPorts 02 Jan '13

02 Jan '13

#37103: ImageMagick 6.8.0 does not correctly display SVG files on PPC (here Leopard 10.5.8) -----------------------------+-------------------------------- Reporter: Peter_Dyballa@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: off-colour | Port: ImageMagick -----------------------------+-------------------------------- Having a problem with the display of SVG files in GNU Emacs 24.3.50 I built this version of GNU Emacs with Fink's ImageMagick and MacPorts' ImageMagick. On intel Snow Leopard both packages (display utility) and GNU Emacs work correctly, so it's likely that the PPC hardware platform with its number format causes the false colours to be displayed. I am attaching a screen-shot with two windows of ImageMagick's display utility on Leopard, one showing the PNG version (with transparency, obviously) and the other the SVG version. Both files can be found in the sources in emacs/etc/images, but I'll try to attach them as well. A final test would be to not use ImageMagick but all the many graphics libraries – the MacPorts GNU Emacs 24.2 does not offer a variant built with librsvg2… -- Ticket URL: <https://trac.macports.org/ticket/37103> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #31926: digikam @2.1.1 unknown protocol 'digikamalbums'
by MacPorts 02 Jan '13

02 Jan '13

#31926: digikam @2.1.1 unknown protocol 'digikamalbums' ------------------------------------+--------------------------------------- Reporter: johannes@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: digikam ------------------------------------+--------------------------------------- Hi, I installed macports and digikam. It starts alright but when I import a photo, I get the error message {{{ Could not start process Unable to create io-slave: klauncher said: Unknown protocol: digikamalbums }}} Running on OS X 10.7.2 -- Ticket URL: <https://trac.macports.org/ticket/31926> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #37294: Trac news links don't work
by MacPorts 02 Jan '13

02 Jan '13

#37294: Trac news links don't work ----------------------------+------------------------- Reporter: ryandesign@… | Owner: wsiegrist@… Type: defect | Status: new Priority: Normal | Milestone: Component: server/hosting | Version: Keywords: | Port: ----------------------------+------------------------- The [/news/ list of news posts] works but clicking any individual article gives e.g. "No handler matched request to /post/macports-212-now- available" -- Ticket URL: <https://trac.macports.org/ticket/37294> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #32714: policykit 103 fails to build on lion
by MacPorts 02 Jan '13

02 Jan '13

#32714: policykit 103 fails to build on lion -------------------------------------+-------------------------------------- Reporter: harald@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Keywords: | Port: -------------------------------------+-------------------------------------- hi, seems i found a build error in policykit under osx 10.7.2 / xcode 4.2. i tried clang/gcc in all three variations to no avail. see the following error message. I`m not very unix savvy, but does it mean that "glib-unix" i missing? there is no such package in port... n.b. long term goal is to build calligra on osx !-> main.c:26:23: error: glib-unix.h: No such file or directory mv -f .deps/polkitd-gposixsignal.Tpo .deps/polkitd-gposixsignal.Po main.c: In function 'main': main.c:133: warning: implicit declaration of function 'open' main.c:133: warning: nested extern declaration of 'open' main.c:133: error: 'O_RDWR' undeclared (first use in this function) main.c:133: error: (Each undeclared identifier is reported only once main.c:133: error: for each function it appears in.) make[3]: *** [polkitd-main.o] Error 1 -- Ticket URL: <https://trac.macports.org/ticket/32714> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #37460: openmotif @2.3.4_0 build fails due to automake 1.13
by MacPorts 02 Jan '13

02 Jan '13

#37460: openmotif @2.3.4_0 build fails due to automake 1.13 -----------------------------+-------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: openmotif -----------------------------+-------------------------------- The openmotif build broke due to changes in automake 1.13. {{{ $ sudo port -vs install openmotif ... ---> Configuring openmotif ... ./configure: line 3081: syntax error near unexpected token `include/config.h' ./configure: line 3081: `AM_CONFIG_HEADER(include/config.h lib/Xm/Xm.h)' Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/work/motif-2.3.4" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man --enable- xft --enable-jpeg --enable-png --x-includes=/opt/local/include --x-libraries=/opt/local/lib Exit code: 2 Error: org.macports.configure for port openmotif returned: configure failure: command execution failed Warning: targets not executed for openmotif: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port openmotif for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_x11_openmotif/openmotif/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port openmotif failed }}} The attached patch appears to fix the problem. -- Ticket URL: <https://trac.macports.org/ticket/37460> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #37459: opensp @1.5.2_1 build fails due to automake 1.13
by MacPorts 02 Jan '13

02 Jan '13

#37459: opensp @1.5.2_1 build fails due to automake 1.13 -----------------------------+-------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: opensp -----------------------------+-------------------------------- The opensp build broke due to changes in auotmake 1.13. {{{ $ sudo port -vs install opensp ---> Computing dependencies for opensp. ---> Fetching distfiles for opensp ---> Verifying checksum(s) for opensp ---> Checksumming OpenSP-1.5.2.tar.gz ---> Extracting opensp ---> Extracting OpenSP-1.5.2.tar.gz ---> Configuring opensp autoreconf: Entering directory `.' autoreconf: running: autopoint --force Copying file m4/isc-posix.m4 Copying file mkinstalldirs Copying file po/Makefile.in.in Copying file po/Makevars.template autoreconf: running: aclocal --force -I m4 aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:19: warning: macro 'AM_CONFIG_HEADER' not found in library autoreconf: configure.in: tracing autoreconf: running: glibtoolize --copy --force glibtoolize: putting auxiliary files in `.'. glibtoolize: copying file `./ltmain.sh' glibtoolize: putting macros in `m4'. glibtoolize: copying file `m4/libtool.m4' glibtoolize: copying file `m4/ltoptions.m4' glibtoolize: copying file `m4/ltsugar.m4' glibtoolize: copying file `m4/ltversion.m4' glibtoolize: copying file `m4/lt~obsolete.m4' glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in- tree. aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' configure.in:19: warning: macro 'AM_CONFIG_HEADER' not found in library autoreconf: running: /opt/local/bin/autoconf --force configure.in:19: error: possibly undefined macro: AM_CONFIG_HEADER If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /opt/local/bin/autoconf failed with exit status: 1 Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_opensp/opensp/work/OpenSP-1.5.2" && autoreconf --install -fvi Exit code: 1 Error: org.macports.configure for port opensp returned: autoreconf failure: command execution failed Warning: targets not executed for opensp: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port opensp for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_opensp/opensp/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port opensp failed }}} The attached patch appears to fix the problem. -- Ticket URL: <https://trac.macports.org/ticket/37459> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #37458: libdnet @1.12_1 build fails due to automake @1.13_0
by MacPorts 02 Jan '13

02 Jan '13

#37458: libdnet @1.12_1 build fails due to automake @1.13_0 -----------------------------+-------------------------------- Reporter: md14-macports@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.2 Keywords: haspatch | Port: libdnet -----------------------------+-------------------------------- The libdnet build broke due to changes in automake 1.13. {{{ $ sudo port -vs install libdnet ... ---> Configuring libdnet aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' config/acinclude.m4:7: warning: underquoted definition of AC_DNET_SOCKADDR_SA_LEN config/acinclude.m4:7: run info Automake 'Extending aclocal' config/acinclude.m4:7: or see http://www.gnu.org/software/automake/manual/automake.html#Extending- aclocal configure.in:13: warning: macro 'AM_CONFIG_HEADER' not found in library glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `config'. glibtoolize: copying file `config/ltmain.sh' glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and glibtoolize: rerunning glibtoolize, to keep the correct libtool macros in- tree. glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. aclocal: warning: autoconf input should be named 'configure.ac', not 'configure.in' config/acinclude.m4:7: warning: underquoted definition of AC_DNET_SOCKADDR_SA_LEN config/acinclude.m4:7: run info Automake 'Extending aclocal' config/acinclude.m4:7: or see http://www.gnu.org/software/automake/manual/automake.html#Extending- aclocal configure.in:13: warning: macro 'AM_CONFIG_HEADER' not found in library configure.in:13: error: possibly undefined macro: AM_CONFIG_HEADER If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf: /opt/local/bin/autoconf failed with exit status: 1 Command failed: cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_libdnet/libdnet/work/libdnet-1.12" && autoreconf --install -I config Exit code: 1 Error: org.macports.configure for port libdnet returned: autoreconf failure: command execution failed Warning: targets not executed for libdnet: org.macports.activate org.macports.configure org.macports.build org.macports.destroot org.macports.install Please see the log file for port libdnet for details: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_net_libdnet/libdnet/main.log To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port libdnet failed }}} I have attached a patch that appears to fix the problem. -- Ticket URL: <https://trac.macports.org/ticket/37458> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 2

[MacPorts] #26039: php5-5.3.3 Adding support to FPM
by MacPorts 01 Jan '13

01 Jan '13

#26039: php5-5.3.3 Adding support to FPM --------------------------------+------------------------------------------- Reporter: info@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: php5 fpm | Port: php5 --------------------------------+------------------------------------------- Hey This diff file adds support to FPM with the fpm variant. It also registers a startup script for FPM. One thing I couldn't manage to change is FPM default configuration file being installed to ${prefix}/etc/php-fpm.conf.default Thanks. :) -- Ticket URL: <http://trac.macports.org/ticket/26039> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 21