MacPorts 2.4.0 has been released

The MacPorts Project is happy to announce that the 2.4.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers for 10.12 [1], 10.11 [2], 10.10 [3], 10.9 [4], 10.8 [5], 10.7 [6], 10.6 [7] and 10.5 [8]

Re: MacPorts 2.4.0 has been released

On 2017-1-28 05:45 , Clemens Lang wrote: Hi, On Fri, Jan 27, 2017 at 01:10:57PM -0500, Adam Dershowitz wrote: I just tried port diagnose and I get the following: Checking for files installed by ports on disk... Warning: '/opt/local/libexec/cups/backend/cups-pdf' installed by port 'cups-pdf'

Re: Inkscape @0.92.0_3+x11 does not work under macOS Sierra 10.12.3!

The crash log contains the following chosen tidbits. Process: inkscape [21797] Path: /opt/local/bin/inkscape Identifier:inkscape Version: 0 Code Type: X86-64 (Native) Parent Process:bash [530] Responsible:

Re: Inkscape @0.92.0_3+x11 does not work under macOS Sierra 10.12.3!

CFLAGS etc that is used in the build? I found that if I build Inkscape outside of MacPorts port file but against MacPorts libs and headers Inkscape works. Barry On 12 Feb 2017, at 21:52, Joshua Root <j...@macports.org> wrote: The crash log contains the following chosen t

MacPorts 2.4.1 has been released

The MacPorts Project is pleased to announce the release of version 2.4.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: MP_EDITOR doesn't work

db wrote: On 6 Apr 2017, at 02:35, Ryan Schmidt wrote: export EDITOR=editor.sh And does it work with MP_EDITOR? I just tried setting it in a vanilla vm, no dice. I set -dv when editing a portfile, but no related information is being logged. Yes it works with MP_EDITOR, I just checked.

Re: port selfupdate fails

Tai Viinikka wrote: Based on previous discussion here, and ticket 53414, I tried two fixes: 1) Revert to default macports.conf: root at recluse:~$cd /opt/local/etc/macports root at recluse:~$cp macports.conf.default macports.conf My port -v self attempt ended (as it always does now) with:

Re: path to sources.conf?

Dave Horsfall wrote: On Tue, 28 Feb 2017, Ryan Williamson via macports-users wrote: Try "sudo find / -name sources.conf" Or better still, use the "locate" command (and run locate.updatedb every so often). As of 2.4.0 we have some shiny new documentation. You can now simply run 'man

Re: problem with pkg_resources in python 3

On 2017-7-13 00:48 , pagani laurent wrote: Is /opt/local/bin/python3.5 somehow a link to a different version? Does uninstalling and reinstalling python35 help? yes! And i also uninstalled and reinstalled setuptools and pip and now it finds pkg_resources… It looks like one should often

Re: problem with pkg_resources in python 3

I have Macports python 3.5 and 3.6 and I have installed setuptools and pip for each version, on Mac OS 10.12.5, XCode 8.3.3 However for python3.5 it says it does not find pkg_resources and for python3.6, it is even worse, python crashes : laurent>python3.5 Python 3.5.2 (default, Dec 17 2016,

Re: problem with pkg_resources in python 3

On 2017-7-13 00:15 , pagani laurent wrote: The following ports are currently installed: py27-pip @9.0.1_0 (active) py27-setuptools @36.0.1_0 (active) py35-pip @9.0.1_0 (active) py35-setuptools @36.0.1_0 (active) py36-pip @9.0.1_0 (active) py36-setuptools @36.0.1_0 (active)

Re: 'log2' is not a member of 'std'

This is MacOSX 10.6.8 running various compilers provided by MacPorts. Compiling the following C++ source #include int main(void) { double d = std::log2(2.3456789f); return 0; } results in 'log2' is not a member of 'std'.

Re: port install pear-TCPDF fails with checksum error

On 2017-6-28 09:29 , macpo...@parvis.nl wrote: On 27 Jun 2017, at 07:42, Joshua Root <j...@macports.org> wrote: Generally you should look at the contents of the HTML file to figure out what generated it instead of the correct file and why. In this case I would guess it's the

Re: Build Failure: akonadi, digikam, gdal, inkscape, inkscape-devel, libxmlxx2, opencv, openmotif, rb-rmagick, sox, and 3 more

Jan Stary wrote: On Aug 08 02:54:54, buildbot at macports.org wrote: Status: Failure Build slave: ports-10.7_x86_64_legacy Full logs: https://build.macports.org/builders/ports-10.7_x86_64_legacy-watcher/builds/8175 I want to look into this (being the maintainer of SoX), but I'm not

Re: port uninstall --follow-dependents python35 removed part of py27- and py36- packages

Alexey Luchko wrote: I've decided to switch python from 3.5 to 3.6 and after a time, run a command $ sudo port uninstall --no-exec --follow-dependents python35 To my surprise were removed not only py35- packages and explicit python35 dependents like httpie, but also a number of py27- and py36-

Re: port install pear-TCPDF fails with checksum error

Hi Ports, port install pear-TCPDF fails with checksum error i have read https://trac.macports.org/wiki/MisbehavingServers and i am sure my isp's dns server is not misbehaving. i have read https://trac.macports.org/wiki/FAQ#checksums. i have searched trac, no match found. so i tried again:

Re: On Snow Leopard, updating at-spi2-atk to @2.26.0_0+universal failed unless at-spi2-core updated first

Ryan Schmidt wrote: On Sep 12, 2017, at 13:58, Richard L. Hamilton wrote: Hardware Version: Mac mini (Mid 2007) Model Identifier: Macmini2,1 Mac OS X 10.6.8 10K549 (Snow Leopard) Xcode 3.2.6 DevToolsSupport-1806.0 MacPorts Version: 2.4.1 The error in the log file seems to say as much:

Re: Jasper failed on High Sierra

On 2017-9-30 03:32 , Giuseppe Di Matteo wrote: Hi, On High Sierra, MacPorts build from sources, I wanted to install wine which has dependencies as gstreamer1 and openal-soft with dependency on jasper. Configure failed. From the log: :warn:main The Xcode Command Line Tools don't appear to

Re: telnet and ftp missing in High Sierra - ideas/suggestions?

Richard L. Hamilton wrote: > I can see ditching the telnet server, but the client remains useful for > debugging various protocols For this purpose you're better off using ncat, which is included with nmap. > Likewise, there remain times a command-line ftp client is useful. > > I see some of

Re: error: can't read "result": no such variable

Gideon Simpson wrote: > Ok, this problem is weird. I get the original error if I perform any port > command, including stuff like port help. However, as soon as I do a sudo, > the commands work as expected. That suggests to me that you have some environment variable set that is a problem for

Re: Binary page

Ryan Schmidt wrote: > On Nov 6, 2017, at 10:00, dan d. wrote: > >> If I want an older binary in the available list installed, how do I do it >> using macports at the cli. > > Regardless of whether you get a binary or build from source, the procedure is > the same: > >

Re: uninstall Macport

Hezi Gildor wrote: > after upgrading from 10.11 to 10.13, and following the migration page, i > can't uninstall Macport: > > sudo port -f uninstall installed > Error: Current platform "darwin 17" does not match expected platform > "darwin 15" > > any idea or just use rm -rf? You need to follow

MacPorts 2.5.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.5.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There

Re: open question on python ...

Frederic Dubois wrote: > Hi, > > This is an open question concerning the "good" way to manage python > "modules". > As you probably know python proposes various builtin "module" managers (such > as pip). > > A first question : is it equivalent to use port to manage "python + module" > and

MacPorts 2.4.4 has been released

The MacPorts Project is pleased to announce the release of version 2.4.4. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: MacPorts 2.5.0-beta1 now available for testing

It's been a week with no new tickets filed against base. I'll give it one more week and then, if nothing comes up, tag a release candidate. - Josh

MacPorts 2.5.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.5.0-rc1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no

Re: 'can't read "os.subplatform": can't read "os_subplatform": no such variable'

Ryan Schmidt wrote: > os.subplatform was added to MacPorts in version 1.9.0, back in 2010. It > should always be set--to "macosx" if you are running MacPorts on macOS, or to > "puredarwin" on any other Darwin variant. It should not be possible for you > to encounter this error on macOS...

reclaim failed: can't read "isrequested(...)" (was: Doing my weekly "port -u uninstall", and...)

Ryan Schmidt wrote: > On Jun 17, 2018, at 11:52, Dave Horsfall wrote: > >> ---> Uninstalling sqlite3 @3.23.1_0+universal >> ---> Cleaning sqlite3 >> You haven't run 'sudo port reclaim' in two weeks. It's recommended you run >> this regularly to reclaim disk space. Would you like to run it now?

Re: 'can't read "os.subplatform": can't read "os_subplatform": no such variable'

On 2018-6-18 17:21 , Joshua Root wrote: > Ryan Schmidt wrote: >> os.subplatform was added to MacPorts in version 1.9.0, back in 2010. It >> should always be set--to "macosx" if you are running MacPorts on macOS, or >> to "puredarwin" on any other

MacPorts 2.5.0 has been released

The MacPorts Project is happy to announce that the 2.5.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers for 10.13 [1], 10.12 [2], 10.11 [3], 10.10 [4], 10.9 [5], 10.8 [6], 10.7 [7], 10.6 [8], 10.5

MacPorts 2.5.1 has been released

The MacPorts Project is pleased to announce the release of version 2.5.1. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

MacPorts 2.5.2 has been released

ase/releases/tag/v2.5.2> On 2018-6-4 14:48 , Joshua Root wrote: > The MacPorts Project is pleased to announce the release of version > 2.5.1. This is a bugfix release with small changes only. See the > ChangeLog [1] for the list of changes. > > If you already have MacPorts ins

Re: gcc49 fails to build

Dave Horsfall wrote: > On Tue, 5 Jun 2018, Ken Cunningham wrote: > >> You will still need to fix this >> >> >> , and who knows what else >> >> The real question is why? What do you need gcc49 for that

Re: Advice on distributing a project

On 2018-6-29 01:18 , Langer, Stephen A. (Fed) wrote: >   > I meant to add a link to our distutils source, if anyone's interested: > https://github.com/usnistgov/OOF3D/tree/macports-packaging/shlib > > The master branch doesn't yet have the latest modifications. Looks pretty reasonable. You could

Re: Advice on distributing a project

> I still have at least one problem. We had to extend distutils so that it > builds a few .dylib shared libraries that are linked to by the more > standardly built python extension modules, which are all .so bundles. All of > them are being installed in the correct location, but the .dylibs

Re: smartctl - Can't run select span range

Ubence Quevedo wrote: > However, when I boot the same system off of Ubuntu 18.04 Live USB with the > same version of smartmontools [6.6], this command works properly: Just a note that Ubuntu does not actually have the same version as MacPorts. As your output shows: MacPorts: > smartctl 6.6

Re: Advice on distributing a project

> I'm making some progress in writing a Portfile for my project, but I'm stuck > on one point. The project's build script uses python distutils (which I'd be > happy to get rid of but that's not likely to happen soon). The build > commands, outside of MacPorts, are > > python setup.py build

Re: reclaim failed: can't read "isrequested(...)" (was: Doing my weekly "port -u uninstall", and...)

Ryan Schmidt wrote: >>> Unfortunately I can't explain why you're encountering this error. >> >> And neither can I find a log file, otherwise I would've attached it... > > I don't know whether reclaim saves a log file. You can possibly produce more > information by using the debug flag: > >

Re: Preventing check of sharedlibs in rev-upgrade

On 2018-6-21 02:01 , Artur Szostak wrote: > Is the algorithm for the rev-upgrade stage documented anywhere so I can > understand exactly how it is trying to identify that a shared library is > broken? > > ____ > From: Joshua Root > Sen

Re: gnucash not finding dbus

Lenore Horner wrote: >> On Jun 20, 2018, at 04:26, Ryan Schmidt wrote: >> >> >> On Jun 19, 2018, at 21:05, Lenore Horner wrote: >> >>> On Jun 11, 2018, at 17:57, Lenore Horner wrote: >>> gnucash is saying Dynamic session lookup supported but failed: launchd did not provide a

Re: Advice on distributing a project

On 2018-6-27 01:07 , Langer, Stephen A. (Fed) wrote: > That's what I don't understand. When not using MacPorts, we use > install_name_tool to fix the libraries. They're built in > $HOME/project/build/{lib, include, etc} and moved to $PREFIX /{lib, include, > etc}, at which point

Re: trace mode by default

> I couldn't find this neither on port's manpage nor in macports.conf. > > Is there an option to set trace mode by default? 'porttrace yes' in macports.conf should do it. Note that then there's no way to turn it off from the command line. - Josh

Fwd: MacPorts has stopped running

Forwarding to the macports-users list. First check whether /opt/local/bin actually ends up being in your PATH by running 'echo $PATH' in your shell. --- Begin Message --- I sorry to send this question to you directly but my Macports question seems not to fit into the unusual cases so I’m not

Re: display issue when launching qalculate

Murray Davis wrote: > This morning, I installed qalculate on my MacOSX system. > > High Sierra, MacPorts up-to-date, version 2.4.2. > > When I try to launch qalculate, I get the following error... > > ~ $ qalculate-gtk > > (qalculate-gtk:1638): Gtk-WARNING **: cannot open display > > I played

Re: gdb fails to compile on Leopard - C++11 compiler

Riccardo Mottola wrote: > Build fails with: > > /opt/local/bin/g++-mp-6 -pipe -Os -D_GLIBCXX_USE_CXX11_ABI=0 -m32 > -I. -I. -I./common -I./config > -DLOCALEDIR="\"/opt/local/share/locale\"" -DHAVE_CONFIG_H > -I./../include/opcode -I./../opcodes/.. -I./../readline/.. -I./../zlib > -I../bfd

Re: gdb fails to compile on Leopard - C++11 compiler

On 2018-1-31 03:41 , Chris Jones wrote: > > It appears the port already has support for building against MPs python > versions, it just is not enabled by default. > > Titan ~/Projects/MacPorts/ports > port variants gdb > gdb has the variants: >    multiarch: Support all target architectures >   

Re: gdb fails to compile on Leopard - C++11 compiler

On 2018-1-31 11:36 , Joshua Root wrote: > On 2018-1-31 03:41 , Chris Jones wrote: >> >> It appears the port already has support for building against MPs python >> versions, it just is not enabled by default. >> >> Titan ~/Projects/MacPorts/ports > port

Re: issue upgrading libcxxabi

Ken Cunningham wrote: > On 2018-01-30, at 9:44 AM, Riccardo Mottola via macports-users wrote: >> before filing a bug, maybe this is expected and there is a stragey for >> updating it or replacing it with something? >> This is on 10.6 Snow Leopard, btw. > > The message is correct. This is

Re: Using MacPorts "Offline"

Jepeway, Chris wrote: > Ah, perfect, thanks (& to Ryan). > > This now works: > > nickel% sudo port version > [long delay while bsdtar runs] > Version: 2.4.2 > > This, however, is a bust: > > nickel% sudo port echo gawk\* > Warning: Can't open index file for source: >

Re: Problem with installing "ttk"

On 2017-12-30 00:53 , Mojca Miklavec wrote: > Joshua, you were the last one doing any content edits, are you willing > to look into it? I really only touched it as part of a license setting spree. I don't have a JDK installed so I wouldn't be able to test an update. - Josh

Re: Problem with installing "ttk"

Dave Horsfall wrote: > On Fri, 29 Dec 2017, Ryan Schmidt wrote: > >>> A third-party application (a radio scanner) >> >> What's it called? Is it open source? > > The scanner? A Uniden UBCD396XT trunking scanner (radio, not optical) > with a serial port. The software? A Tcl script contained in

Re: Unable to execute port: Could not open file

YW. This would be a good addition to 'port diagnose' by the way, if anyone wants to file an enhancement ticket. - Josh On 2018-8-14 05:26 , joel johnston wrote: > That did it! Thanks Joshua! > > On Mon, Aug 13, 2018 at 12:23 PM Joshua Root <mailto:j...@macports.org>> wrote:

Re: "Error mapping file into memory"?

Poor phrasing on my part sorry: I should have said that mmap sets errno, but macho_parse_file currently has no way of returning that extra information to its caller. It should be possible to insert a perror call or similar to get a more specific message (though it could end up being EINVAL which

Re: tcl-sqlite3

> currently, this port is at version > > tcl-sqlite3 @3.6.22_3 > > sqlite3, however, is already at 3.24. there have been relevant changes > to sqlite between versions 22 and 24, so I now see "malformed schema" > errors with the tcl package for databases generated with current sqlite3 >

Re: tcl-sqlite3

On 2018-8-26 01:22 , joerg van den hoff wrote: > > > On 25.08.18 06:21, Joshua Root wrote: >>> currently, this port is at version >>> >>>    tcl-sqlite3 @3.6.22_3 >>> >>> sqlite3, however, is already at 3.24. there have been relevant changes

Re: tcl-sqlite3

On 2018-8-27 10:37 , Ryan Schmidt wrote: > > > On Aug 26, 2018, at 07:54, Marius Schamschula wrote: > >> On Aug 26, 2018, at 7:34 AM, Marius Schamschula wrote: >> >>> I’ve added a sqlite3-tcl subport: >>> >>>

Re: Cannot uninstall local port with invalid version number

S P Arif Sahari Wibowo wrote: > On 2018-07-20, 13:32, Ryan Schmidt wrote:>> You're not meant to modify this > file manually, but the >> registry is an SQLite 3 database located at: >> >> /opt/local/var/macports/registry/registry.db >> >> If you wish to examine or manipulate the database, you will

Re: port listed to be upgraded but not upgraded

Riccardo Mottola wrote: > I finished "port upgrade outdated" successfully (on Lion) and in fact > I can re-run it and no action happens. > > Kaiserin:~ multix$ sudo port -v upgrade outdated > Password: > ---> Scanning binaries for linking errors > ---> No broken files found. > ---> No broken

Re: port listed to be upgraded but not upgraded

On 2018-9-10 13:23 , Ryan Schmidt wrote: > It is fine for ports to offer different versions to different platforms. Up > to now, a "platform" was the combination of an operating system name, major > version number, and architecture (PowerPC or Intel). It has been proposed > that the C++

Re: port listed to be upgraded but not upgraded

On 2018-9-10 14:23 , Ryan Schmidt wrote: > > > On Sep 9, 2018, at 23:21, Joshua Root wrote: > >> On 2018-9-10 13:23 , Ryan Schmidt wrote: >>> It is fine for ports to offer different versions to different platforms. Up >>> to now, a "platform" w

Re: MacPorts 2.4.3 has been released

On 2018-4-12 12:39 , Ryan Schmidt wrote: > > On Apr 11, 2018, at 10:23, Joshua Root wrote: > >> No, rsync just hasn't updated yet. The ports are also a bit out of date. >> Ryan should be able to take a look before too long. > > mprsyncup is failing with: > &g

MacPorts 2.4.3 has been released

The MacPorts Project is pleased to announce the release of version 2.4.3. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: Questions on port development

On 2018-3-26 01:19 , macpo...@parvis.nl wrote: > I'm working on a port for munin 2 as the current macports version 1.4.7 is of > 14 mar 2012. > The munin-node seems to work fine, the server part requires more testing. > > (1) > > I need a port install munin@2.0.35 buth without a destroot phase.

Re: Is there and "rdist" for Mac?

Dave Horsfall wrote: > On Fri, 16 Mar 2018, Ryan Schmidt wrote: > >>> What should I be using now? >> >> Possibly git. > > And... > > > On Fri, 16 Mar 2018, Chris Jones wrote: > >> Sounds to me like you are describing a git hosted software project, >> which you then clone and build where ever

Re: Preventing check of sharedlibs in rev-upgrade

Artur Szostak wrote: > Is there any way of telling MacPorts to not consider one, more or all shared > libraries when attempting its check for broken libraries in a Portfile? I > have some Java software which is precompiled and also delivering some > additional shared libraries. Unfortunately,

Re: Advice on distributing a project

On 2018-6-28 18:54 , Ryan Schmidt wrote: > > macOS has been around for over 17 years. It would be weird if in all that > time Python hasn't developed an easy way to create correct dylibs. My > assumption therefore is that such an easy method does exist, I just don't > know what it is since I'm

Re: fail do install dbus

Riccardo Mottola wrote: > Ryan Schmidt wrote: >>> the build directory is owned by root - could it be that macports user is >>> trying to use it? >> We are seeing a lot of reports of this type of problem since the release of >> MacPorts 2.5. I don't know why. >> > > that is very reassuring :) >

Re: Mojave and Migration

Michael Newman wrote: > I followed the migration instructions which are found here: > https://trac.macports.org/wiki/Migration > > > That sort of worked, except that some ports didn’t get reinstalled. For > example, neither ImageMagick nor MPlayer

MacPorts 2.5.4 has been released

The MacPorts Project is pleased to announce the release of version 2.5.4. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

Re: sunclock

> I recently upgraded a macbook air from 10.6 to 10.13 > and discovered that sunclock is no longer in macports. > > Does anyone know which was the last version of macos > whose corresponding macports included sunclock? That isn't how MacPorts releases work. There is one set of Portfiles that are

Re: port install tuntaposx fails - Mac OS MOJAVE

Unfortunately tuntaposx has not had an upstream release since 2015, and currently has no maintainer in MacPorts. - Josh

Re: conflicting variants while rebuilding a dependency

On 2019-1-14 09:59 , Riccardo Mottola wrote: > Hi Joshua, > > On 2019-01-13 02:04:30 +0100 Joshua Root wrote: > >> >>> The following ports are currently installed: >>>     gexiv2 @0.10.8_1+python27+python36 (active) >> >>> So, I suppose

Re: conflicting variants while rebuilding a dependency

Riccardo Mottola wrote: > I get this (Lion 10.7): > > --> Scanning binaries for linking errors > Could not open /opt/local/lib/libexiv2.26.dylib: Error opening or > reading file (referenced from /opt/local/lib/libgexiv2.2.dylib) > ---> Found 1 broken file, matching files to ports > ---> Found

Re: How To Troubleshoot MacPorts

Michael Newman wrote: >> On Apr 12, 2019, at 06:19, Ryan Schmidt wrote: >> >> It's difficult to answer a question this broad. But I can tell you a little >> about how I answer port build failure bug reports or posts on the list. > > Thank you for taking the time to write such an interesting

Re: "Fetching archive" fails for all ports on multiple systems, different networks

On 2019-4-14 15:17 , Lee Finn wrote: > Hi Joshua,  > > The curl is the MacPorts curl. The linking is the same as your reference.  OK, so do you get the same result with /usr/bin/curl? - Josh signature.asc Description: OpenPGP digital signature

no destroot found (was: help please)

> what does this mean … > > [haycorn] /Users/jam/DEVEL [580]% sudo port install qt511-qtwebkit > ---> Computing dependencies for qt511-qtwebkit > ---> Installing qt511-qtxmlpatterns @5.11.3_0 > Error: Failed to install qt511-qtxmlpatterns: no destroot found at: >

Re: OpenBLAS binary packages

> I am trying to understand why I am not able to get the OpenBLAS port to > install exclusively from binary packages, i.e. using something like: > sudo port -b install OpenBLAS > Even if I prepare a local repository with the prebuilt binary packages it > indicates that it is not able to find

Re: OpenBLAS binary packages

Chris Jones wrote: > Its not possible to get binary installs for OpenBLAS due to license > conflicts between it and one of its deps, openssl IIRC. Because of this > the buildbots flag the builds as non-distributable. That's often the reason why binary packages are not available, but not in this

Re: OpenBLAS binary packages

On 2019-5-15 19:01 , Artur Szostak wrote: > OK, I must be blind. Thanks for indicating archive_sites. I completely missed > that when looking at the Portfile yesterday. This explains everything. > > This raises the question: how is the MacPorts team mitigating the cost of > compiling OpenBLAS

Re: Wireshark, Qt5 and El Capitan

On 2019-4-21 15:37 , Christopher Jones wrote: > Hi, > > Just to finish up, as the fix seemed trivial (us the PG to set the deps) > I have pushed an update doing just this. So update and try again. This port is not openmaintainer; please don't make changes without maintainer permission or a

Re: Wireshark, Qt5 and El Capitan

On 2019-4-21 14:23 , Chris Jones wrote: > Hi, > > I was curious, so I fired off a build using the buildbots, just to see > what would happen in a clean environment. > > https://build.macports.org/builders/ports-10.11_x86_64-builder/builds/84721/steps/install-dependencies/logs/stdio > > And

Re: Wireshark, Qt5 and El Capitan

On 2019-4-21 21:19 , Chris Jones wrote: > > >> On 21 Apr 2019, at 10:45 am, Joshua Root wrote: >> >>> On 2019-4-21 15:37 , Christopher Jones wrote: >>> Hi, >>> >>> Just to finish up, as the fix seemed trivial (us the PG to set the deps)

New MacPorts ports database site

MacPorts' new ports database is live at . Please consider installing the "mpstats" port to enable submission of anonymous information about your system and installed ports for statistical purposes. The information collected is currently: * MacPorts version * OS name

MacPorts 2.6.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.6.0-beta1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) There

Re: OpenCL deprecation in MacOS 10.14

vincent habchi wrote: > Folks, > > I’m currently upgrading the GDAL port to 3.0.1 and… the OpenCL code doesn’t > work anymore. No way I can find the file OpenCL.h anywhere in the system. I > suppose this is part of Apple policy of deprecating OpenCL, so that no one > can build new software

Re: LibcxxOnOlderSystems

On 2019-8-29 20:04 , Bjarne D Mathiesen wrote: > > > Ken Cunningham wrote: >>> --- >>> Now, how do I switch this automatic process off ? >>> I really need to get my system into a working condition ;-) >>> >> I think if you start over, uninstall all ports, and then set your >> macports.conf back

Re: LibcxxOnOlderSystems

On 2019-8-29 21:21 , Bjarne D Mathiesen wrote: > > #=> port deps clang-3.4 > Full Name: clang-3.4 @3.4.2_12+analyzer > Build Dependencies: cctools > Library Dependencies: libxml2, llvm-3.4, python27, libffi, ncurses, zlib > Runtime Dependencies: clang_select, ld64, perl5 I guess you don't have

Re: LibcxxOnOlderSystems

On 2019-8-30 00:53 , Bjarne D Mathiesen wrote: > I > 1) uninstalled all installed ports > 2) manually cleared the build directory for cruft What about variants.conf? > So ...  it fails already after the first port has been installed  Yeah, there's no getting around the fact that +llvm37

Re: Why does everything now want ncurses-bootstrap, which doesn't build???

Bill Cole wrote: > So it's that time of the month: time for a port > {reclaim,selfupdate,upgrade outdated} cycle on my Snow Leopard machine, > which has a stable working "LibcxxOnOlderSystems" setup. > > Or at least, it HAD a stable working "LibcxxOnOlderSystems" setup. Now, > upgrades are

Re: Why does everything now want ncurses-bootstrap, which doesn't build???

> On 23 Aug 2019, at 21:00, Joshua Root wrote: > >> The reason for the *-bootstrap ports is that 10.6 doesn't come with >> libc++. So you need to be able to build a compiler capable of building >> libc++, while only using the system's libstdc++. That compiler is >

MacPorts 2.6.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.6.0-rc1 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no

Re: output like "port list all" over the web?

Richard L. Hamilton wrote: >> On Aug 4, 2019, at 23:53, Dave Allured - NOAA Affiliate via macports-users >> wrote: >> >> So will it be sufficient to simply run "port list all" on the current stable >> MacPorts package, as a frequent automatic process? Capture the text result >> and put it in

MacPorts 2.6.0 has been released

The MacPorts Project is happy to announce that the 2.6.0 version has now been released. It is available via the usual methods: - selfupdate if you already have MacPorts installed - package installers for 10.14 [1], 10.13 [2], 10.12 [3], 10.11 [4], 10.10 [5], 10.9 [6], 10.8 [7], 10.7 [8],

Re: MacPorts 2.6 - Leopard 20.6 and libgcc8

On 2019-9-27 06:01 , Christopher Jones wrote: > Hi, > > From the output it appears cmake has a dependency on both libgcc and libgcc8. > This is not correct on 10.5. > > You should file a ticket against cmake to bring it to the attention of the > maintainer. It's not cmake doing it. The

Re: Problems with MP 2.6.0 on Snow Leopard

Hi Rob, Rob Widdicombe wrote: > I'm still resolutely running Snow Leopard and last night did a port > selfupdate to take me up to MP 2.6.0. So far so good. > > However, when I then tried to do a port rev-upgrade, the problems began. It > fails on the first step, upgrading gmp. Looking at the

Re: gnutls dependencies

Kastus Shchuka wrote: > gnutls was recently upgraded to 3.6.10_0. When I try to upgrade gnutls, it > pulls in a tall list of dependencies: > > ---> Computing dependencies for gnutls > The following dependencies will be installed: > clang-8.0 > clang_select > docbook-xml > docbook-xml-4.1.2

Re: Problem installing the grace port

On 2019-11-17 04:54 , Ippoliti, Emiliano wrote: > Dear Joshua, > > thank you for your detailed answer. > In fact, looking at the content of my DYLD_LIBRARY_PATH variable: > >> echo $DYLD_LIBRARY_PATH > /usr/local/qt/lib:/usr/local/psh/lib:/usr/local/dt/lib:/usr/local/netpbm/lib:/opt/lib > > and

Re: Problem installing the grace port

> Dear Macports users, > > I have a MacBook Pro with MacOS 10.13.6 on which I installed several programs > through Macports. However, when I installed the grace package in order to use > plotting program xmgrace, the following message error pops up: > > Warning: Widget must be a VendorShell. >

MacPorts 2.6.2 has been released

The MacPorts Project is pleased to announce the release of version 2.6.2. This is a bugfix release with small changes only. See the ChangeLog [1] for the list of changes. If you already have MacPorts installed, the preferred method for updating is to run: sudo port selfupdate For new

  1   2   3   >