January 2016 - macports-tickets - lists.macosforge.org

[MacPorts] #49846: git @2.6.3: gitk can not be invoked with command line parameters like gitk --all
by MacPorts 05 Jan '16

05 Jan '16

#49846: git @2.6.3: gitk can not be invoked with command line parameters like gitk --all ----------------------------------+-------------------------------- Reporter: friedrich.beckmann@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: gitk | Port: git ----------------------------------+-------------------------------- gitk works fine when it is invoked without parameters. If I start gitk with a parameter it looks like this: {{{ friedrismacbook:pspp fritz$ gitk --all Error in startup script: bad menu entry index "Ansicht bearbeiten ..." while executing ".bar.view entryconf [mca "Edit view..."] -state normal" invoked from within "if {$cmdline_files ne {} || $revtreeargs ne {} || $revtreeargscmd ne {}} { # create a view for the files/dirs specified on the command line se..." (file "/opt/local/bin/gitk" line 12442) friedrismacbook:pspp fritz$ }}} The gui opens shortly and then closes immediately. -- Ticket URL: <https://trac.macports.org/ticket/49846> MacPorts <https://www.macports.org/> Ports system for OS X

1 4

[MacPorts] #49516: py27-scipy build failure on PowerBookG4 running Leopard 10.5.8; fortran compiler called with bizarre arguments
by MacPorts 05 Jan '16

05 Jan '16

#49516: py27-scipy build failure on PowerBookG4 running Leopard 10.5.8; fortran compiler called with bizarre arguments -------------------------------------------------+------------------------- Reporter: zanderpower@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Keywords: Leopard PPC G4, fortran called | Version: 2.3.4 incorrectly | Port: py-scipy -------------------------------------------------+------------------------- While upgrading py27-scipy on a PowerBook G4 (1.67 Ghz) running Leopard 10.5.8, the build calls the fortran compiler from (macports) gcc47 with completely wrong arguments: {{{ building 'dfftpack' library compiling Fortran sources Fortran f77 compiler: /mp2/local/bin/gfortran-mp-4.7 -Os -fno-second- underscore -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2 Fortran f90 compiler: /mp2/local/bin/gfortran-mp-4.7 -Os -fno-second- underscore -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2 Fortran fix compiler: /mp2/local/bin/gfortran-mp-4.7 -Wall -g -ffixed-form -fno-second-underscore -Os -fno-second-underscore -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2 creating build/temp.macosx-10.5-ppc-2.7 creating build/temp.macosx-10.5-ppc-2.7/scipy creating build/temp.macosx-10.5-ppc-2.7/scipy/fftpack creating build/temp.macosx-10.5-ppc-2.7/scipy/fftpack/src creating build/temp.macosx-10.5-ppc-2.7/scipy/fftpack/src/dfftpack compile options: '-I/mp2/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/numpy/core/include -c' gfortran-mp-4.7:f77: scipy/fftpack/src/dfftpack/dcosqb.f gfortran-mp-4.7: error: unrecognized command line option '-march=x86-64' gfortran-mp-4.7: error: unrecognized argument in option '-mtune=generic' gfortran-mp-4.7: note: valid arguments to '-mtune=' are: 401 403 405 405fp 440 440fp 464 464fp 476 476fp 505 601 602 603 603e 604 604e 620 630 740 7400 7450 750 801 821 823 8540 8548 860 970 G3 G4 G5 a2 cell common e300c2 e300c3 e500mc e500mc64 ec603e native power power2 power3 power4 power5 power5+ power6 power6x power7 powerpc powerpc64 rios rios1 rios2 rs64 rsc rsc1 titan gfortran-mp-4.7: error: unrecognized command line option '-msse2' gfortran-mp-4.7: error: unrecognized command line option '-march=x86-64' gfortran-mp-4.7: error: unrecognized argument in option '-mtune=generic' gfortran-mp-4.7: note: valid arguments to '-mtune=' are: 401 403 405 405fp 440 440fp 464 464fp 476 476fp 505 601 602 603 603e 604 604e 620 630 740 7400 7450 750 801 821 823 8540 8548 860 970 G3 G4 G5 a2 cell common e300c2 e300c3 e500mc e500mc64 ec603e native power power2 power3 power4 power5 power5+ power6 power6x power7 powerpc powerpc64 rios rios1 rios2 rs64 rsc rsc1 titan gfortran-mp-4.7: error: unrecognized command line option '-msse2' error: Command "/mp2/local/bin/gfortran-mp-4.7 -Os -fno-second-underscore -fPIC -O2 -march=x86-64 -DMS_WIN64 -mtune=generic -msse2 -I/mp2/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/numpy/core/include -c -c scipy/fftpack/src/dfftpack/dcosqb.f -o build/temp.macosx-10.5-ppc-2.7/scipy/fftpack/src/dfftpack/dcosqb.o" failed with exit status 1 Command failed: cd "/mp2/local/var/macports/build/_mp2_local_var_macports_sources_rsync.macports .org_release_tarballs_ports_python_py-scipy/py27-scipy/work/scipy-0.16.1" && /mp2/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7 setup.py --no-user-cfg config_fc --fcompiler gnu95 --f77exec /mp2/local/bin/gfortran-mp-4.7 --f77flags=' -Os -fno-second-underscore' --f90exec /mp2/local/bin/gfortran-mp-4.7 --f90flags=' -Os -fno-second- underscore' config --cc /mp2/local/bin/gcc-mp-4.7 --include-dirs /mp2/local/include --library-dirs /mp2/local/lib build Exit code: 1 }}} The last time I upgraded py27-scipy (as well as py34-scipy) was in August (for a rev-bump from @0.16.0_0 to @0.16.0_1) which built with no problem. The last "true" version upgrade was a few days before the rev-bump when py-scipy went from @0.15.1_0 to @0.16.0_0--again, no problem. I haven't upgraded gcc47 since the end of May, so I don't believe gcc47 is the source of the error (unless scipy now requires a more recent gcc). Any ideas? -- Ticket URL: <https://trac.macports.org/ticket/49516> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

Re: [MacPorts] #18849: inkscape : build an application
by MacPorts 05 Jan '16

05 Jan '16

#18849: inkscape : build an application -----------------------------+---------------------- Reporter: neric27@… | Owner: devans@… Type: defect | Status: closed Priority: High | Milestone: Component: server/hosting | Version: Resolution: | Keywords: quartz Port: inkscape | -----------------------------+---------------------- Comment (by devans@…): Inkscape upstream uses a MacPorts based build system with a private set of ports that are not the same as the current official ones. So if you want to try this you are on your own. We provide inkscape and inkscape-devel which can both be built either +x11 or +quartz as well as a separate inkscape-app port that provides an Inkscape.app application bundle. -- Ticket URL: <https://trac.macports.org/ticket/18849#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #49490: Installation problem openmpi into Yosemite 10.10.4
by MacPorts 05 Jan '16

05 Jan '16

#49490: Installation problem openmpi into Yosemite 10.10.4 --------------------------+-------------------------------- Reporter: shipman035@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: --------------------------+-------------------------------- Since almost 10 days I am fighting with the installation problem of openmpi into version of Yosemite 10.10.4 I tried several ways however finally all of of the ways gave following error: {{{Error: org.macports.build for port openmpi-gcc49 returned: command execution failed}}} When I looked at the .log file also saw following error: {{{ /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_sc ience_openmpi/openmpi- gcc49/work/openmpi-1.10.0/opal/mca/hwloc/base/hwloc_base_util.c:1482:13: error: 'HWLOC_OBJ_OSDEV_COPROC' undeclared (first use in this function)}}} If someone can help to me I will be appreciated. Thank you -- Ticket URL: <https://trac.macports.org/ticket/49490> MacPorts <https://www.macports.org/> Ports system for OS X

1 9

[MacPorts] #49830: Unable to upgrade arpack due to fetch error: invalid command name "fortran_compiler_name"
by MacPorts 05 Jan '16

05 Jan '16

#49830: Unable to upgrade arpack due to fetch error: invalid command name "fortran_compiler_name" ------------------------------------------+-------------------------------- Reporter: todmorrison@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: fetch, fortran_compiler_name | Port: arpack ------------------------------------------+-------------------------------- Trying: port -v upgrade arpack I get: ---> Fetching distfiles for arpack Error: org.macports.fetch for port arpack returned: invalid command name "fortran_compiler_name" Warning: targets not executed for arpack: org.macports.destroot org.macports.fetch org.macports.checksum org.macports.extract org.macports.patch org.macports.configure org.macports.build Please see the log file for port arpack for details: Attaching: /opt/local/var/macports/logs/_opt_local_var_macports_sources_svn.macports.org_trunk_dports_math_arpack/arpack/main.log -- Ticket URL: <https://trac.macports.org/ticket/49830> MacPorts <https://www.macports.org/> Ports system for OS X

1 5

Re: [MacPorts] #32706: py-pyodbc: can't find MacPorts ODBC drivers
by MacPorts 05 Jan '16

05 Jan '16

#32706: py-pyodbc: can't find MacPorts ODBC drivers -------------------------+-------------------------------- Reporter: bpanulla@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.0.3 Resolution: | Keywords: haspatch Port: py-pyodbc | -------------------------+-------------------------------- Comment (by khindenburg@…): IF anyone is interested I have a patch on https://trac.macports.org/ticket/29185 that updates to the recent version and adds that ticket's variants. If you do try it out, let us know the results. -- Ticket URL: <https://trac.macports.org/ticket/32706#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #29185: py-pyodbc: Add iODBC variant
by MacPorts 05 Jan '16

05 Jan '16

#29185: py-pyodbc: Add iODBC variant --------------------------+-------------------------------- Reporter: stevemcc@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch Port: py-pyodbc | --------------------------+-------------------------------- Comment (by khindenburg@…): I tried to update this and include your variants but I can't really test the actual code -- Ticket URL: <https://trac.macports.org/ticket/29185#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #50199: gnuplot: opportunistically uses gtk2 when building with wxwidgets enabled
by MacPorts 05 Jan '16

05 Jan '16

#50199: gnuplot: opportunistically uses gtk2 when building with wxwidgets enabled ----------------------+--------------------- Reporter: devans@… | Owner: mojca@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: gnuplot ----------------------+--------------------- I ran into this issue when testing p5-graphics-gnuplotif. When building using the +wxwidgets variant (default), gnuplot will use gtk2 if available and enable "gdk/gtk tweaks" to the configuration. This could be fixed by adding a dependency on gtk2 but that may not what you want here. The alternative seems to be patching or otherwise overriding configure.in to disable this behavior -- there's no configuration option to do this for you. Here's the relevant section of configure.in: {{{ if test "${enable_wxwidgets_ok}" = yes ; then WX_CXXFLAGS="`$WX_CONFIG --cxxflags | sed 's/-fno-exceptions//'` $CAIROPANGO_CFLAGS" WX_LIBS="`$WX_CONFIG --libs` $CAIROPANGO_LIBS" dnl Check for fork(), used for the 'persist' effect AC_FUNC_FORK dnl Check for gtk (raise/lower tweaks) PKG_CHECK_MODULES(GTK, [gtk+-2.0], have_gtk=yes, have_gtk=no) if test "${have_gtk}" = yes ; then AC_DEFINE(HAVE_GTK, 1, [Define to use gtk/gdk tweaks]) WX_CXXFLAGS="$WX_CXXFLAGS $GTK_CFLAGS" WX_LIBS="$WX_LIBS $GTK_LIBS" fi }}} -- Ticket URL: <https://trac.macports.org/ticket/50199> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

Re: [MacPorts] #28907: gforth 0.7.0 universal variant fails
by MacPorts 05 Jan '16

05 Jan '16

#28907: gforth 0.7.0 universal variant fails ---------------------------+-------------------------------- Reporter: ryandesign@… | Owner: macports-tickets@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 1.9.2 Resolution: fixed | Keywords: haspatch Port: gforth | ---------------------------+-------------------------------- Changes (by ctreleaven@…): * status: new => closed * resolution: => fixed Comment: Tried a bunch of things and I'm unable to successfully build universal. I've 'fixed' the issue by eliminating universal builds, r144228. -- Ticket URL: <https://trac.macports.org/ticket/28907#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #49495: py-hggit broken with mercurial @3.5.99_0
by MacPorts 05 Jan '16

05 Jan '16

#49495: py-hggit broken with mercurial @3.5.99_0 --------------------------------+---------------------- Reporter: easieste@… | Owner: sean@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: py-hggit mercurial | Port: py-hggit --------------------------------+---------------------- hg push to github repository is failing for me with the following error. An "hg outgoing" successfully shows that a commit is outstanding. Downgrading to mercurial @3.5.1_0 allows hg-git to function again. Most likely upgrading to mercurial-3.6 should allow this to work again as few others are testing the exact version of mercurial that corresponds to @3.5.99_0. Issue filed upstream as well at <https://bitbucket.org/durin42/hg- git/issues/169/hg-push-to-github-fails>. {{{ quoth:~/work/slime$ hg push pushing to git+ssh://git@github.com:easye/slime.git ** Unknown exception encountered with possibly-broken third-party extension hggit ** which supports versions 3.4 of Mercurial. ** Please disable hggit and try your action again. ** If that fixes the bug please report it to https://bitbucket.org/durin42 /hg-git/issues ** Python 2.7.10 (default, Aug 18 2015, 20:14:59) [GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.54)] ** Mercurial Distributed SCM (version 3.6-rc+2-b57e5bfaad7c) ** Extensions loaded: strip, mq, hggit Traceback (most recent call last): File "/opt/local/bin/hg", line 43, in <module> mercurial.dispatch.run() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 54, in run sys.exit((dispatch(request(sys.argv[1:])) or 0) & 255) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 116, in dispatch ret = _runcatch(req) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 187, in _runcatch return _dispatch(req) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 920, in _dispatch cmdpats, cmdoptions) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 679, in runcommand ret = _runcommand(ui, options, cmd, d) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 1051, in _runcommand return checkargs() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 1011, in checkargs return cmdfunc() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/dispatch.py", line 917, in <lambda> d = lambda: util.checksignature(func)(ui, *args, **cmdoptions) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/util.py", line 801, in check return func(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/extensions.py", line 183, in closure return func(*(args + a), **kw) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/util.py", line 801, in check return func(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/hgext/mq.py", line 3526, in mqcommand return orig(ui, repo, *args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/util.py", line 801, in check return func(*args, **kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/commands.py", line 5421, in push opargs=opts.get('opargs')) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/mercurial/extensions.py", line 183, in closure return func(*(args + a), **kw) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7 /site-packages/hggit/util.py", line 48, in inner return f(*args, **kwargs) TypeError: exchangepush() got an unexpected keyword argument 'opargs' }}} -- Ticket URL: <https://trac.macports.org/ticket/49495> MacPorts <https://www.macports.org/> Ports system for OS X

1 3