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

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

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.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.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: 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

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.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

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: 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

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: 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: 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: 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: 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

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: 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

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: 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

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: 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: 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: 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: 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: 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: 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: 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: 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

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: 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: '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: 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: 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: 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

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: 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

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: 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'

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]

<    1   2   3