Re: openal-soft fails to build (fwd)

Looks like openal-soft is linking with libsndfile despite not depending on it (and fails because the lack of a declared dependency also means the architectures haven't been made to match.) File a ticket. - Josh

Re: Problem with rsync.macports.org mirror?

There hasn't been a base release recently, so that output is completely expected when updating the base sources. There should be some more output involving "---> Updating the ports tree" which, if you have an rsync-based source configured in sources.conf, will run additional rsync commands to

Re: Macports user on login screen after migration from old Mac to new Mac

I don't know what 'macadmin' is. If you mean the 'macports' user, it should be as unprivileged as possible, and thus not a member of any groups other than its own. TBH, the easiest fix is probably to delete the 'macports' user and group, and let them be recreated by the installer during step 2

Re: Macports user on login screen after migration from old Mac to new Mac

On 2022-8-1 03:27 , Murray Eisenberg wrote: In a message posted already in this list’s archives but not yet appearing in the batched emails I receive from the list, Johsua Root writes: “ … the 'macports’ user… should be as unprivileged as possible, and thus not a member of any groups other tha

Re: FOCAL

Dave Horsfall wrote: Be there a Mac implementation of FOCAL? I have a hankering to get back to my early programming days :-) Well there's this one at least: It will need some Makefile patching, but as it already builds on Linux, FreeBSD and

MacPorts 2.4.0-beta1 now available for testing

Source code and pkgs for MacPorts 2.4.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.0-rc1 now available for testing

Source code and pkgs for MacPorts 2.4.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 sh

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] (un

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: MacPorts 2.4.0 has been released

On 2017-2-1 03:33 , William H. Magill wrote: I just updated my two systems - an iMac and aMmac mini. The iMac when cleanly, but the Mac mini “hick-upped”. I thought the mini was on the immediately previous release. I guess not. Not a big deal. just interesting. shianbrae> sudo port selfupdat

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

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

et to see the exact 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 wrote: The crash log contains the following chosen tidbits. Process:

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 installs

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 sources

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: python development environment on a mac

$ which virtualenv /opt/local/bin/virtualenv $ virtualenv $HOME/PyEnv/python/27 New python executable in /Users/paul/PyEnv/python/27/bin/python Installing setuptools, pip, wheel...done. $ virtualenv $HOME/PyEnv/python/36 New python executable in /Users/paul/PyEnv/python/36/bin/python Installing se

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

Re: Trac does not see /opt for attaching files

William H. Magill wrote: I know that Apple has changed things, so I don’t know if this is a bug or a WAI (works as intended). When you file a Trac ticket and attempt to attach a log file — the “choose” option does NOT show /opt. Obviously, easily worked around by copying the /opt file to a us

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: 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 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 fourth possibility listed o

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

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) py

Re: problem with pkg_resources in python 3

On 2017-7-13 00:30 , pagani laurent wrote: It is (to me) very strange! Lorenzo>sudo port upgrade python35 ---> Scanning binaries for linking errors ---> No broken files found. Lorenzo>sudo port installed python35 The following ports are currently installed: python35 @3.5.3_1 (active) Lorenz

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 uni

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

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 be

sudo port security (was: MacPorts shell mode)

Chris Jones wrote: On 19 Oct 2017, at 9:07 pm, Rainer Müller wrote: However, in terms of security, allowing to run 'port' without password is equivalent to allowing the user to run any command. Well, not entirely true. It only lets you run whatever port lets you do. The fact that port lets y

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: > > https://trac.macports.org

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 wh

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

Did the selfupdate actually update macports base? Blowing away your installation won't help in any case. There is an error in the error handling, but that's only a problem because there is an error when running sw_vers in the first place. I just fixed it, so if you're comfortable applying this cha

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 sw

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

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 expected

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: > file:///Users/chrjep2/shar

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

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 installs,

Re: MacPorts 2.4.3 has been released

On 2018-4-12 01:06 , Davide Liessi wrote: > 2018-04-11 15:20 GMT+02:00 Lenore Horner : >> Both last night after receiving this announcement and this morning I have >> run sudo port selfupdate and received the following response. >> ---> Updating MacPorts base sources using rsync >> MacPorts base v

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

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 a

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 installs,

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 a

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 p

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 sho

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 installs,

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 gcc5

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

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 Darw

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

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, Ma

Re: Preventing check of sharedlibs in rev-upgrade

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

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 so

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

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

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 install_name_

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

MacPorts 2.5.3 has been released

The MacPorts Project is pleased to announce the release of version 2.5.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 installs,

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: Unable to execute port: Could not open file

> jjohnston at sd-jjohnston-03 /opt/local/var $ ls -lha > /opt/local/var/macports/sources/ > rsync.macports.org/macports/release/tarballs/ports/sysutils/coreutils/Portfile > -rw-r--r-- 1 root 505 3.7K Jul 19 19:19 /opt/local/var/macports/sources/ > rsync.macports.org/macports/release/tarballs/p

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>&g

Re: "Error mapping file into memory"?

Lee Bast wrote: > Latest version of MacPorts & Xcode on a Mac Pro 2010 12-core running > 10.13, 64GB memory. After performing a normal selfupdate/upgrade outdated > routine today I got a pile of "Error mapping file into memory" for various > ports/libraries. I rolled back and rebooted then

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 ca

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 > (iden

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: >>> >>> https://github.com/macports/macports-ports/commit/0e46e32ec2ff78ce3adc725cb3aed714b8203

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 p

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++ standard

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: Foiled Again - Part 3 Addendum

Michael Newman wrote: Anyway, I was able to get MacPorts fully working by: sudo rm -rf /Library/Developer/CommandLineTools You don't have to fully remove the CLTs to fix the problem, just /Library/Developer/CommandLineTools/usr/include/c++. Install CLT 16 from the DMG available from ​ht

Re: Foiled Again - Part 3 Addendum

Michael Newman wrote: So, I decided to run reclaim and try again with ffmpeg. But this time the list of dependencies was huge: [long list of dependencies] Yes, ffmpeg has a lot of dependencies and even more when building from source. Reclaim may have removed some of the latter because they'r

Re: Graphviz build fails

David Nicholls wrote: With the latest Sonoma 14.7.1 on an Intel Mac, the most recent Xcode tools and Macports 2.10.4 self updated, I ran port upgrade outdated, and after a few port upgrades, I got this message: sudo port upgrade outdated ---> Computing dependencies for graphviz ---> Fetchin

MacPorts 2.10.3 has been released

The MacPorts Project is pleased to announce the release of version 2.10.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 in

MacPorts 2.10.4 has been released

The MacPorts Project is pleased to announce the release of version 2.10.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 i

Re: what setting to use to force only arm64 (Apple Silicon) binaries/libraries, no universal ports?

Clearing universal_archs in macports.conf will disable universal entirely. Some ports that don't support arm64 may still install as x86_64 if they don't require any universal dependencies. - Josh

Re: Migration Errors after Sequoia

I still can’t install msmtp because: Error: Failed to build gss: command execution failed I hesitate to file a bug report on this problem because it appears that there is already a bug report on gss (#70869), but I can’t tell if mine would be a duplicate of that. The only way to be certain i

Re: failed migration to Sequoia

On 21/9/2024 21:18, Artemio González López wrote: julia :info:build curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 :info:build make[1]: *** [/opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports.org_macports_r

Re: several ports cannot be installed due to a Perl circular dependency hell...

Error: The following dependencies were not installed because all of them have unmet dependencies (likely due to a dependency cycle): p5.34-authen-sasl p5.34-net-smtp-ssl p5.34-cgi p5.34-pod-coverage-trustpod p5.34-test-simple p5.34-pod-eventual p5.34-mixin-linewise p5.34-sub-exporter p5.34-data-op

Re: Tcl mess

Ryan Carsten Schmidt wrote: On Sep 23, 2024, at 03:29, Christoph Kukulies wrote: > > How can I overcome this? I'm not sure. I haven't seen this before. It almost sounds like the selfupdate didn't fully work and didn't fully update the bundled copy of Tcl. Try installing MacPorts using the i

Re: Requested Ports

Michael Newman wrote: I did what Arno suggested (thank you) and I now have a requested.txt file that, as far as I can tell, is a good representation of both: • The ports I migrated to this machine when I first set it up last October. • The ports that I later installed. What I still don’t unde

Re: segmentation fault when fetching from ftp

Ryan Carsten Schmidt wrote: On Sep 27, 2024, at 16:51, Murray Eisenberg wrote: >//>/Does installing the MacPorts version of curl accomplish anything in this regard? / Not unless you build MacPorts from source and configure it to use MacPorts curl but that's not recommended because your MacPor

Re: segmentation fault during an install

Just trying again seems to have eliminated the curl issue (after cleaning libmagic and first installing some other ports that were missed on the migrate sweep). Typically the crash only happens when connecting to an FTP site after having connected to a HTTP/2 site. So availability of binaries

Re: failed migration to Sequoia

On 20/9/2024 08:27, Artemio González López wrote: Before reading your message, I deleted the directory /Library/Developer/ CommandLineTools and reinstalled the Command Tools for Xcode 16 (which I also have installed) from scratch using the dmg at the Developer website. This should be equivale

Re: failed migration to Sequoia

On 21/9/2024 03:36, Artemio González López wrote: I just ran port selfupdate, but the only outdated port it found is xorg- libXi  (which I updated). I guess it is not worth to give port restore — last another try, since the problematic por was libgcc14, which hasn’t¡t been updated. Am I right

<    1   2   3   4   >