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

[MacPorts] #51280: rust does not build on os X El Capitan (10.11.4)
by MacPorts 02 Jun '16

02 Jun '16

#51280: rust does not build on os X El Capitan (10.11.4) -------------------------+-------------------------------- Reporter: davidriod@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: rust -------------------------+-------------------------------- It seems that the clang version is incorrectly detected as too old by the configure script on rust-stage0. Here an extract on output when running manually the configure script: {{{ configure: configure: on OS X >=10.9, forcing use of clang configure: configure: CFG_ENABLE_CLANG := 1 configure: CFG_USING_CLANG := 1 configure: error: bad APPLE CLANG version: 7.3.0, need >=7.0 }}} -- Ticket URL: <https://trac.macports.org/ticket/51280> MacPorts <https://www.macports.org/> Ports system for OS X

1 10

[MacPorts] #51539: qrupdate requires destroot.target commands
by MacPorts 02 Jun '16

02 Jun '16

#51539: qrupdate requires destroot.target commands -------------------------------------------------+------------------------- Reporter: chrisgorman@… | Owner: macports- Type: defect | tickets@… Priority: Normal | Status: new Component: ports | Milestone: Keywords: qrupdate install-shlib install- | Version: 2.3.4 staticlib | Port: qrupdate -------------------------------------------------+------------------------- qrupdate builds but doesn't install on my machine. It fails to call install-shlib and install-staticlib after making the libraries. Adding destroot.target install install-shlib install-staticlib allows the build to install. -- Ticket URL: <https://trac.macports.org/ticket/51539> MacPorts <https://www.macports.org/> Ports system for OS X

1 9

Re: [MacPorts] #43054: py-graph-tool stuck at building stage
by MacPorts 02 Jun '16

02 Jun '16

#43054: py-graph-tool stuck at building stage ----------------------------+--------------------- Reporter: absima@… | Owner: tiago@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: duplicate | Keywords: Port: py-graph-tool | ----------------------------+--------------------- Comment (by elebv2005@…): After I posted this it got out!! :) Thanks. -- Ticket URL: <https://trac.macports.org/ticket/43054#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #43054: py-graph-tool stuck at building stage
by MacPorts 02 Jun '16

02 Jun '16

#43054: py-graph-tool stuck at building stage ----------------------------+--------------------- Reporter: absima@… | Owner: tiago@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: duplicate | Keywords: Port: py-graph-tool | ----------------------------+--------------------- Comment (by elebv2005@…): I have a very similar problem. It is now 1hr 25 mins since the installation began. Current status looks like: ---> Cleaning sparsehash ---> Fetching archive for py27-graph-tool ---> Attempting to fetch py27-graph- tool-2.16_0+clang38+openmp.darwin_14.x86_64.tbz2 from http://jog.id.packages.macports.org/macports/packages/py27-graph-tool ---> Attempting to fetch py27-graph- tool-2.16_0+clang38+openmp.darwin_14.x86_64.tbz2 from https://packages.macports.org/py27-graph-tool ---> Attempting to fetch py27-graph- tool-2.16_0+clang38+openmp.darwin_14.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/py27-graph-tool ---> Fetching distfiles for py27-graph-tool ---> Attempting to fetch graph-tool-2.16.tar.bz2 from http://jog.id.distfiles.macports.org/macports/distfiles/py-graph-tool ---> Verifying checksums for py27-graph-tool ---> Extracting py27-graph-tool ---> Configuring py27-graph-tool ---> Building py27-graph-tool after doing several other stuff above. Should I break and come out? What is the graceful way to roll back with no damage? Thanks. -- Ticket URL: <https://trac.macports.org/ticket/43054#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #51545: ola @0.10.1_0: update to 0.10.2
by MacPorts 02 Jun '16

02 Jun '16

#51545: ola @0.10.1_0: update to 0.10.2 ---------------------------------+-------------------------------- Reporter: bugs@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: haspatch maintainer | Port: ola ---------------------------------+-------------------------------- Update to reflect the new upstream release. -- Ticket URL: <https://trac.macports.org/ticket/51545> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

[MacPorts] #51536: Request s3cmd update
by MacPorts 02 Jun '16

02 Jun '16

#51536: Request s3cmd update -------------------------------+-------------------------------- Reporter: murrayeisenberg@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: update | Port: s3cmd -------------------------------+-------------------------------- Current version from s3tools.org is 1.6.1 but current port is for 1.5.2. Request update. -- Ticket URL: <https://trac.macports.org/ticket/51536> MacPorts <https://www.macports.org/> Ports system for OS X

1 2

Re: [MacPorts] #15939: port install : in need of a progressbar
by MacPorts 01 Jun '16

01 Jun '16

#15939: port install : in need of a progressbar --------------------------+-------------------------------- Reporter: pc@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Low | Milestone: MacPorts Future Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by cal@…): Even then, the number of lines breaks (i.e. `\n`s) stays the same, just the order changes. -- Ticket URL: <https://trac.macports.org/ticket/15939#comment:15> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #15939: port install : in need of a progressbar
by MacPorts 01 Jun '16

01 Jun '16

#15939: port install : in need of a progressbar --------------------------+-------------------------------- Reporter: pc@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Low | Milestone: MacPorts Future Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by rjvbertin@…): That could work, as long as it doesn't happen too frequently that parallel builds start merging lines lllliiiikkkkeeee ssssoooo. -- Ticket URL: <https://trac.macports.org/ticket/15939#comment:14> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #15939: port install : in need of a progressbar
by MacPorts 01 Jun '16

01 Jun '16

#15939: port install : in need of a progressbar --------------------------+-------------------------------- Reporter: pc@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Low | Milestone: MacPorts Future Component: base | Version: 1.6.0 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by cal@…): Just so this is documented somewhere… I've had the idea in my head for a while that we could use the number of lines generated on stdout as an indicator of build progress. Since warnings go to stderr, this number of lines should be roughly the same on all installations for a given port at a given version. A webservice could be used to map a hash of (portname, version, variants, OS) to the median number of lines submitted for this tuple. We could encourage users to opt-in to provide this information if base only used the webservice if users also agree to submit this info. The hash would be used to prevent turning this into statistics, since we have other approaches for that. This approach would work for the configure, build and destroot phases of pretty much all ports, regardless of their build system. Progress for the operations involving (de-)activation and archiving could be handled per file because we know (or can easily determine) the number of files in a port. -- Ticket URL: <https://trac.macports.org/ticket/15939#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #48959: build fails
by MacPorts 01 Jun '16

01 Jun '16

#48959: build fails ---------------------------+-------------------------------- Reporter: elfprince13@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: | Port: opencv ---------------------------+-------------------------------- "use of undeclared identifier 'avcodec_free_frame'; did you mean 'avcodec_get_name'?" in the log file - is there a mismatched dependency version or something? -- Ticket URL: <https://trac.macports.org/ticket/48959> MacPorts <https://www.macports.org/> Ports system for OS X

1 3