On Nov 24, 2018, at 18:29, Jasper Frumau wrote:
> When I go to https://lists.macports.org/mailman/options/macports-users to
> unsubscribe my password no longer works. So I ask for a new one. The new one
> is never sent. So this way I cannot unsubscribe from the MacPorts Users Mail
> list. I
> On Nov 17, 2018, at 10:03, Uli Wienands æwrote:
> Well, some progress: I was able to get over the hump by not updating all
> dependencies (-n switch),
That is not a good idea. You can end up with ports in a broken state. However,
rev-upgrade should fix that, if so.
The PR I submitted has
On Nov 16, 2018, at 13:37, Mark Brethen wrote:
> There are a number of local ports that I was developing that never came to
> fruition. Is it possible to remove them from the registry?
The registry only contains information about installed ports. To remove
information about a port from the r
On Nov 16, 2018, at 17:20, Dave Horsfall wrote:
> On Thu, 15 Nov 2018, Ryan Schmidt wrote:
>
>> That's called System Integrity Protection. It's a new macOS feature as of OS
>> X 10.11 El Capitan. You cannot modify files installed by Apple unless you
>> t
On Nov 15, 2018, at 19:14, Riccardo Mottola wrote:
> Hi,
>
> as you thought, it is specific ASM stuff, so the typos are relative to a
> precise architecture only,
>
> On 2018-11-14 20:55:58 +0100 Ryan Schmidt wrote:
>
>> On Nov 14, 2018, at 11:17, Riccardo Mot
On Nov 15, 2018, at 18:21, Dave Horsfall wrote:
> Sierra, latest Macports, GNU Enscript 1.6.6.
>
> Some time ago I discovered that an upgrade (dunno what) had blown away all my
> crafted printer definitions, so "enscript" was no longer working; the error
> is "lpr: The printer or class does
On Nov 15, 2018, at 00:51, j...@tigger.ws wrote:
> The new bit is a Telstra NBN modem (for Aus’s new high speed broadband.) If
> any Aus user has tamed the Telstra NBN modem please tell me what and how.
Have you tried using a closer mirror instead of the master (which is in
Germany)?
https:
> On Nov 15, 2018, at 00:11, j...@tigger.ws wrote:
>
> Is the wiki wrong?
> This does not look correct:
>
> [twill] /Users/jam [24]% tail -n 2 /opt/local/etc/macports/sources.conf
> # rsync://rsync.macports.org/macports/release/tarballs/ports.tar [default]
> https://distfiles.macports.org/port
On Nov 14, 2018, at 19:33, Mark Brethen wrote:
> BTW, py36-tables also has those reinplace warnings.
>
> ---> Extracting py36-tables
> Warning: reinplace s:utils.h:xxx_utils.h: didn't change anything in
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_releas
On Nov 14, 2018, at 18:53, Mark Brethen wrote:
> I followed the note below after a selfupdate:
>
> NOTE: Default fortran changed to +gcc8; consider switching variants to enable
> pre-built packages for mpich-default by running:
> "sudo port clean mpich-default && sudo port upgrade mpich-defau
On Nov 14, 2018, at 15:42, Mark Brethen wrote:
> I performed a selfupdate today and noticed the hdf5 port issued these
> warnings:
>
> Warning: reinplace s|ccache || didn't change anything in
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs
On Nov 14, 2018, at 16:12, Mark Brethen wrote:
> Unable to configure with given options: FCFLAGS and FFLAGS are both set, but
> with different values (FCFLAGS=-pipe -m64, FFLAGS=-pipe). Attaching log file.
Looks like this has already been reported:
https://trac.macports.org/ticket/57424
And
On Nov 14, 2018, at 11:26, Ulrich Wienands wrote:
> On Nov 14, 2018, at 12:31 AM, Ryan Schmidt wrote:
>
>> On Nov 13, 2018, at 20:33, Uli Wienands wrote:
>>
>>> Ok, so I did upgrade tk. That went ok, sort of. In the process of upgrading
>>> tk it butchered s
On Nov 14, 2018, at 11:17, Riccardo Mottola wrote:
> I wonder if this will cause issues on my 10.5 at the next upgrade, since it
> is 32bit form me.. I'll see.
zstd and tiff built successfully on our 10.5 PowerPC builder. The problem may
be specific to 32-bit Intel, or it may be specific to
On Nov 13, 2018, at 02:56, Achille Fiore wrote:
> Hello. I think that I have a problem with the update to Mojave. I was
> installing via Macports an ESO pipeline following this procedure "Quick
> start" described in
> https://www.eso.org/sci/software/pipelines/installation/macports.html . Th
On Nov 13, 2018, at 20:33, Uli Wienands wrote:
> Ok, so I did upgrade tk. That went ok, sort of. In the process of upgrading
> tk it butchered several other ports ("found 61 broken files, 5 broken
> ports"). In the process of fixing those it ran aground trying to install
> zstd. As a result,
On Nov 12, 2018, at 15:40, Dave Horsfall wrote:
> On Mon, 12 Nov 2018, Mojca Miklavec wrote:
>
>> Since you are talking about the optical drive and 10.6: is your
>
> I take it you mean 10.12.6 (Sierra)? The OS works fine, but Mojave is
> officially not supported on this model (and I couldn'
On Nov 12, 2018, at 15:09, Mojca Miklavec wrote:
> The fun thing
> is that once I finally decided to upgrade it, I could no longer even
> download 10.11.
There are knowledge base articles from which you can download older macOS
versions. Here's the one for 10.11:
https://support.apple.com/en
On Nov 12, 2018, at 15:52, Ken G. Brown wrote:
> Following https://trac.macports.org/wiki/Migration
>
> Got to sudo ./restore_ports.tcl myports.txt
> then:
>> sudo ./restore_ports.tcl myports.txt
>> Error: we appear to be stuck, exiting...
>> infinite loop
>>while executing
>> "sort_ports
On Nov 12, 2018, at 16:52, db wrote:
> On 12 Nov 2018, at 22:32, Ryan Schmidt wrote:
>> What we really want is a web site where this information can more easily be
>> seen.
>
>> I don't really want the public making massive numbers of http requests to
>>
On Nov 12, 2018, at 15:50, Mojca Miklavec wrote:
> On Mon, 12 Nov 2018 at 22:32, Ryan Schmidt wrote:
>> On Nov 12, 2018, at 15:25, db wrote:
>>> On 11 Nov 2018, at 13:00, Ryan Schmidt wrote:
>>>
>>>> I'll probably need to write a script to pull all
On Nov 12, 2018, at 15:25, db wrote:
> On 11 Nov 2018, at 13:00, Ryan Schmidt wrote:
>
>> I'll probably need to write a script to pull all the failures out of the
>> buildbot logs, since we don't have anything set up to do that yet. If there
>> are ports
On Nov 12, 2018, at 04:52, Dr M J Carter wrote:
> On Sat, Nov 10, 2018 at 03:47:26PM -0600, Ryan Schmidt wrote:
>
>> The only file MacPorts always copies into its home directory is the
>> Xcode preferences plist.
>
> Quick note: on our 10.13 build systems, I find that
On Nov 12, 2018, at 04:15, Dr M J Carterwrote:
>> I'm not aware of any changes in MacPorts specific to Mojave that
>> would relate to the handling of the home directory. So I think the
>> bug you're investigating is a bug in macOS or Xcode, not MacPorts.
>
> Possibly APFS? that test's pen
On Nov 11, 2018, at 14:36, Dave Horsfall wrote:
> On Sat, 10 Nov 2018, Bill Cole wrote:
>
>>> OK, I've been talked out of trying Mojave on this thing (it's unlikely to
>>> work)
>>
>> Indeed. https://support.apple.com/kb/SP777?locale=en_US says it definitely
>> won't.
>
> So I see; well, i
On Nov 12, 2018, at 11:24, Riccardo Mottola wrote:
>>> If I try to uninstall gegl:
>>> $ sudo port uninstall gegl
>>> Note: It is not recommended to uninstall/deactivate a port that has
>>> dependents as it breaks the dependents.
>>> The following ports will break: gimp2 @2.8.22_2
>>
>>> I wo
On Nov 12, 2018, at 12:47, Uli Wienands wrote:
> Hi, after Riccardo Mottola mentioned that he contributed a patch to gimp to
> make Gimp 2.10 run under 10.6 I tried to install it.
>
> The install went a fair amount but then died at xorg-xorgproto, whatever that
> is, with the error:
>
> Err
On Nov 9, 2018, at 10:36, Dr M J Carter wrote:
> On Fri, Nov 09, 2018 at 04:05:34PM +0100, Vincent Habchi wrote:
>> On 9 Nov 2018, at 11:31, Dr M J Carter wrote:
>>>
>>> On Wed, Oct 03, 2018 at 01:25:28PM +0100, Chris Jones wrote:
On 03/10/18 13:16, S. L. Garwood via macports-users wrote:
>
On Nov 10, 2018, at 14:37, Dave Horsfall wrote:
> are the binaries more or less ready to go?
I have not yet finished telling the buildbot to build all ports on Mojave. I'm
doing them in small batches, which I believe is more efficient and allows
builds for recent commits to be processed soon
On Nov 6, 2018, at 09:14, Nicholas Papadonis wrote:
> This article goes into depth on how Homebrew opens OSX to a number of
> security issues. I'm curious if a security expert could comment if similar
> vulnerabilities exist with Macports.
>
> One vulnerability is a malicious program acquiri
> On Nov 6, 2018, at 00:17, Mojca Miklavec wrote:
>
> However the folder for dvisvgm doesn't exist due to:
>
>$ port_binary_distributable.tcl -v dvisvgm
>"dvisvgm" is not distributable because its license "GPL-3+"
> conflicts with license "GPL-2" of dependency "libpaper"
>
> (I wasn't
On Nov 3, 2018, at 09:48, Rainer Müller wrote:
> On 02.11.18 19:25, Carlo Tambuatco wrote:
>> Macports docker port, aka The Moby project...is upstream of the official
>> Docker, so...
>>
>> I guess I'm asking is there anything Docker can do that macports docker
>> can't do?
>
> Not sure I und
On Oct 30, 2018, at 14:24, Ryan Schmidt wrote:
> On Oct 30, 2018, at 14:06, Ryan Schmidt wrote:
>
>> On Oct 29, 2018, at 22:20, Christian Calderon wrote:
>>
>>> I was compiling git as ppc64 on my G5 running Leopard 10.5.8, and it failed
>>> when trying
On Oct 30, 2018, at 14:06, Ryan Schmidt wrote:
> On Oct 29, 2018, at 22:20, Christian Calderon wrote:
>
>> I was compiling git as ppc64 on my G5 running Leopard 10.5.8, and it failed
>> when trying to configure the port in the subject. A quick search shows that
>&g
On Oct 29, 2018, at 22:20, Christian Calderon wrote:
> I was compiling git as ppc64 on my G5 running Leopard 10.5.8, and it failed
> when trying to configure the port in the subject. A quick search shows that
> my exact failure mode seems to have been very common: while configuring
> p5.26-l
On Oct 30, 2018, at 05:37, Michael Dickens wrote:
> 2) generally located in "$PREFIX/var/macports/software/$PORT/" will be
> compressed tarballs of the activated files for any given PORT. Use "tar jtvf
> $FILENAME" to get contents, where FILENAME will be something like
> "$PORT-$VERSION+$VAR
On Oct 29, 2018, at 22:03, Michael wrote:
> On 2018-10-29, at 7:47 PM, Ryan Schmidt wrote:
>
>> On Oct 29, 2018, at 21:26, Michael wrote:
>>
>>> So two things when I attempted to update macports and ffmpeg.
>>>
>>> Number 1: There was a HUGE c
On Oct 29, 2018, at 21:26, Michael wrote:
> So two things when I attempted to update macports and ffmpeg.
>
> Number 1: There was a HUGE chain of things to update first. Surprising to me
> was what looked like all of Xwindows.
>
> XWindows? Why?
>
> After X, it updated openssl, then sqlite3, t
On Oct 28, 2018, at 19:18, Bill Cole wrote:
> On 27 Oct 2018, at 8:27, Steve Wardle wrote:
>
>> # port list clamav
>> clamav @0.100.2sysutils/clamav
>
> Not relevant, because 'port list' shows the only *available* version, not the
> version you have installed.
On Oct 26, 2018, at 15:29, Riccardo Mottola wrote:
> This gives me another clue: if it is ld64 is it building a universal binary?
> I am on a 32bit Mac.
No, ld64 is just the name of Apple's linker. It works for 32-bit and 64-bit.
Which one is used depends on your -arch or -m flags as usual.
On Oct 28, 2018, at 04:03, Carlo Tambuatco wrote:
>> If you want to switch from X11 to Quartz, you should uninstall and reinstall
>> ports, so doing so at migration time is ideal.
>>
>> There are many occurrences of the string "+x11" in your myports.txt. You
>> will not want those when switc
On Oct 27, 2018, at 19:46, Carlo Tambuatco wrote:
> I’ve got gnucash installed at the moment, but it’s the x11 build not the
> native quartz build.
>
> I’ve been thinking about following the instructions detailed here:
>
> https://wiki.gnucash.org/wiki/MacOSX/MacPortsDetail
>
> for building
Please don't do that. Please instead fix it in the affected compiler port(s).
https://trac.macports.org/ticket/57412
> On Oct 28, 2018, at 02:24, Ken Cunningham
> wrote:
>
> something like this from another port earlier today should do, until this
> issue finally gets fixed in the compiler r
On Oct 25, 2018, at 23:43, Ken Cunningham wrote:
> a little experimenting on 10.5 today shows this:
>
> $ /usr/bin/ld
> ld warning: -arch not specified
> ld: no object files specified for inferred architecture i386
>
>
> $ /opt/local/bin/ld
> ld: warning: -arch not specified
> ld: warning: -
On Oct 25, 2018, at 14:52, Richard L. Hamilton wrote:
> Took me a moment to realize you were referring to the Portfile facility, not
> the obsoleted (as of what OS version?) OS facility, regarding StartupItems.
Yes, I'm referring to the MacPorts portfile options whose names begin with
"start
On Oct 25, 2018, at 11:28, Kevin Layer wrote:
> Curiously, after
>
> port unload rsync
>
> I still see rsync running:
>
> 21693 ?? Ss 0:00.00 /opt/local/bin/rsync --daemon
> --config=/opt/local/etc/rsyncd.conf
>
> I've been unable to find what starts it. Ideas?
Kill it? If it com
On Oct 25, 2018, at 10:08, Kevin Layer wrote:
> Richard L. Hamilton wrote:
>
>>> I've had issues before with the whole daemondo wrapper bit. Some
>>> things may need it, given how launchd has different expectations
>>> from other system's approaches to starting daemons, and some
>>> daemons m
On Oct 25, 2018, at 11:01, Murray Eisenberg wrote:
> On 25 Oct2018, at 11:58 AM, Ryan Schmidt wrote:
>>
>>
>> On Oct 25, 2018, at 10:34, Murray Eisenberg wrote:
>>
>>> Such searches give different instructions on what permissions to give the
>>&g
On Oct 25, 2018, at 10:34, Murray Eisenberg wrote:
> Such searches give different instructions on what permissions to give the
> mysql datadir !
>
> If the datadir is
>
> /Users/me/Databases/mysql/data
>
> (and my.cnf includes "datadir = /Users/murray/Databases/mysql/data”, of
> cour
On Oct 24, 2018, at 15:25, Murray Eisenberg wrote:
> Starting MySQL
>. ERROR! The server quit without updating PID file
> (/Users/me/Databases/mysql/data/mysql.pid).
>
This is probably not a MacPorts-specific problem; you should search the
Internet. I did, and one result suggested
On Oct 24, 2018, at 01:50, Michael Newman wrote:
> I decided to compare the ports found in myports.txt with those in
> requested.txt.
>
> I figured that every port in requested.txt should also be in myports.txt.
>
> But, that’s not the case. Requested.txt contains only the following ports:
>
On Oct 23, 2018, at 04:29, Michael Newman wrote:
> On Oct 23, 2018, at 16:21, Ryan Schmidt wrote:
>
>>> Not by me. I’ve always installed ports with the simplest command: sudo port
>>> install [port]
>>
>> Right, and doing so may, in some cases, cause depen
On Oct 23, 2018, at 04:20, Michael Newman wrote:
> On Oct 23, 2018, at 16:17, Ryan Schmidt wrote:
>
>> Were any of the ports in myports.txt, by chance, installed with the
>> +universal variant? If so, you'll have to install them without the
>> +universa
On Oct 23, 2018, at 04:14, Michael Newman wrote:
> On Oct 23, 2018, at 15:31, Ryan Schmidt wrote:
>
>>> Makes me thing something went seriously wrong with restore_ports.tcl.
>>
>> Ok, pick one, try to install it, see what happens. If it fails, show us what
>> t
On Oct 23, 2018, at 03:30, Michael Newman wrote:
> On Oct 23, 2018, at 15:09, Ryan Schmidt wrote:
>>> Is there any way to find our without manually checking each and every port
>>> in myports.txt?
>>
>> Sure, get a list of only the port names you want to know ab
On Oct 22, 2018, at 06:25, Christian Calderon wrote:
> Hello all! First time asking a question on the mailing list.
>
> I have a Power Mac G5 Quad running OS X 10.5.8. My macports.conf contains
> "buildarch pcc" and "universal_archs ppc ppc64". My variants.conf contains
> the line "+universal".
On Oct 23, 2018, at 01:26, rmgls wrote:
> Source-hiLight failed to compile!
> Main.log attached.
>
> any idea?
The log shows you're using Xcode 10 with clang 1000.11.45.2 on macOS 10.14.
The error in the log is:
:info:build /opt/local/bin/ranlib: object: .libs/libgnu.a(dirname-lgpl.o)
malform
On Oct 23, 2018, at 00:16, 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 were reinstalled. I
On Oct 15, 2018, at 19:38, Yuri wrote:
> GAMESS is a popular open source quantum chemistry package:
> https://www.msg.chem.iastate.edu/gamess/
>
> GAMESS is used by academics, who in turn use MacOS a lot, so this port would
> be much appreciated if created.
>
>
> You can look at the FreeBS
On Oct 15, 2018, at 20:48, M P wrote:
> Do you think cleaning up directories like below will help?
>
> $ sudo port -fp uninstall installed
> followed by
> $ sudo rm -rf \
> /opt/local \
> /Applications/DarwinPorts \
> /Applications/MacPorts \
> /Library/LaunchDaemo
On Oct 14, 2018, at 12:09, M P wrote:
> Yes, I did
> sudo tar xvf
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/ports.tar
>
> in
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp
>
> and went fine
>
> the listing is attache
On Oct 14, 2018, at 06:42, Al Varnell wrote:
> It's been ten days now and the Seattle mirror still doesn't have the MacPorts
> 2.5.4! Makes me wonder what else is out of date there?
Looks like the Seattle mirror has not updated MacPorts content since July 17,
2018. I will ask the administrator
On Oct 13, 2018, at 19:50, M P wrote:
> On Thu, Oct 11, 2018 at 11:23 PM Ryan Schmidt wrote:
>> Ok, so it's the extraction of the tarball that's failing.
> Yes, all is as expected.
Are you able to extract the tarball manually? For example...
cd /tmp
/usr/bin/tar xf
/
Ok, so it's the extraction of the tarball that's failing.
On Oct 11, 2018, at 19:57, M P wrote:
> The admin used CarbonCopy for backup. Any suggestions
Does the macports user exist and is its home directory set to the correct path?
It should be:
$ dscl . read /Users/macports NFSHomeDirectory
On Oct 10, 2018, at 09:55, Kevin Horton wrote:
> on Mojave, with Xcode 10.0:
>
> $ xephem
> Warning: Fatal Error:
> _XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL
> [1]34379 segmentation fault xephem
>
> Any troubleshooting advice is appreciated.
Sounds li
On Oct 9, 2018, at 02:34, Richard L. Hamilton wrote:
> The audio plays fine, and the window comes up the right size, but it's always
> black, with a variety of files (mp4, mkv, m4v, avi, swf, at least; what I had
> handy to try).
>
> It worked back on High Sierra (same version of mpv, I thin
On Oct 8, 2018, at 22:50, M P wrote:
> DEBUG: successful verification with key
> /opt/local/share/macports/macports-pubkey.pem
> DEBUG: system: /usr/bin/tar -C
> /opt/local/var/macports/sources/rsync.macports.org/macports/release/tarballs/tmp
> -xf
> /opt/local/var/macports/sources/rsync.ma
On Oct 9, 2018, at 03:54, Riccardo Mottola wrote:
> /usr/bin/gcc-4.2 -o pamtris pamtris.o boundaries.o framebuffer.o input.o
> triangle.o utils.o
> -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_graphics_netpbm/netpbm/work
On Oct 8, 2018, at 21:26, M P wrote:
> On Mon, Oct 8, 2018 at 8:24 PM M P wrote:
>
>> I removed
>> /opt/local/var/macports/sources/rsync.macports.org
>>
>> Then still a problem with nco port:
>>
>> %sudo port -v selfupdate
>> ---> Updating MacPorts base sources using rsync
>>
>> Willkomm
On Oct 8, 2018, at 19:50, M P wrote:
>
> This is what happens when I issue
> %portindex
> Creating port index in ~/ports
>
> Total number of ports parsed: 0
> Ports successfully parsed:0
> Ports failed: 0
> Up-to-date ports skipped: 0
>
> also
>
> %port version
>
Don't forget to Reply All so that the conversation stays on the mailing list.
On Oct 8, 2018, at 19:12, M P wrote:
> On Mon, Oct 8, 2018 at 4:19 PM Ryan Schmidt wrote:
>
>> On Oct 8, 2018, at 07:19, M P wrote:
>>
>> > Hello,
>> > There is a port "
On Oct 8, 2018, at 07:19, M P wrote:
> Hello,
> There is a port "nco" listed as available but its installation fails under
> Mojave 10.14
> with
>
> sudo port install nco
> Error: Port nco not found
>
> What is the reason?
Sounds like a problem with your port index. Try running
sudo port -
On Oct 7, 2018, at 12:07, Richard L. Hamilton wrote:
> This change to the Portfile got it to build for me; apparently those files
> are in a different location now, so the original pre-check failed (properly
> installed Xcode and command line tools will find it regardless of the
> pre-check,
On Oct 6, 2018, at 12:29, Murray Eisenberg wrote:
> With MacPorts 2.5.4 under macOS 10.14…
>
> I just did a "port sync", then "port upgrade outdated”. The port dvisvgm
> @2.3.4_4 was configured, built, staged into destroot, installed, and cleaned.
>
> Next I saw “Computing dependencies for
On Oct 4, 2018, at 10:26, Ken Cunningham wrote:
> On 2018-10-04, at 8:19 AM, Ryan Schmidt wrote:
>>
>> Josh brought up some reasonable objections:
>>
>> https://lists.macports.org/pipermail/macports-dev/2018-October/039443.html
>>
>
> I was thinking
On Oct 4, 2018, at 10:14, Ken Cunningham wrote:
> 2. do an SDK trick with MacOS.10.13.sdk so it builds 32bit on Mojave (pretty
> easy, but required manual intervention)
This requires the MacOSX.sdk port and changes to base that I've mentioned
before.
https://lists.macports.org/pipermail/mac
On Oct 1, 2018, at 17:59, Daniel J. Luke wrote:
> On Oct 1, 2018, at 6:25 PM, Michael Newman wrote:
>>> MacPorts, for the most part, works fine on macOS10.14 now.
>>
>> Does that mean that I can install Mojave
You can install Mojave, but bear in mind what I said previously on this list
about
On Sep 28, 2018, at 21:10, Anand Pathak Sharma wrote:
> Hi everyone!
>
> I cannot figure out what and how happened to cause this issue but today, out
> of the perceived blue, I found that my local nginx/mysql servers installed
> via macports have stopped working. I have a feeling this may be
On Sep 28, 2018, at 13:20, Michael wrote:
> On 2018-09-28, at 9:50 AM, Thomas Bodlien wrote:
>
>> But why?
>> What do you need 32-Bit Support for?
>
> Wine is probably the best example of a 32 bit only port right now.
Wine isn't 32-bit only; it's universal. And with a few changes to the Port
On Sep 27, 2018, at 08:35, David wrote:
> Source extension osxfuse
> Assertion 'common_is_variable DEFAULT_SDK_10_14_ARCHITECURES' failed
> at common_variable_clone (./build.d/lib/common.sh, line 501)
> at common_variable_clone (./build.d/lib/common.sh, line 514)
> at build_target_invoke (./bui
On Sep 25, 2018, at 12:51, Werner LEMBERG wrote:
> I have to use `sync' anyway since I'm running MacPorts directly from
> the git repositories.
Not sure exactly what you mean.
If you mean you've configured macports to use the macports-ports git repository
as your ports tree, then there's no
On Sep 25, 2018, at 19:50, Ken Cunningham wrote:
> On 2018-09-25, at 5:38 PM, Ryan Schmidt wrote:
>
>> On Sep 25, 2018, at 10:35, Ken Cunningham wrote:
>>
>>> There is one hiccup. Updating macports with "sudo port selfupdate" does not
>>> respect
On Sep 25, 2018, at 10:35, Ken Cunningham wrote:
> There is one hiccup. Updating macports with "sudo port selfupdate" does not
> respect the curlprefix.
I'm not sure what you mean. selfupdate doesn't use curl; it uses rsync.
On Sep 23, 2018, at 20:21, Mike Crawford wrote:
> Taco Bell's firewall blocks "Downloads and Freeware". I contemplated
> explaining the difference between freeware and Open Source to the
> manager, but realized I was still hungry. Having blown the last of my
> cash on a Beefy 5-Layer Burrito,
On Sep 21, 2018, at 17:59, Mike Crawford wrote:
> MacPorts doesn't have psql.
Yes it does. You can pick which version you want; postgresql11 is the latest:
$ port echo name:^postgresql..$
postgresql10
postgresql11
postgresql80
postgr
On Sep 19, 2018, at 11:54, Richard L. Hamilton wrote:
> So I think that the 10.13 SDK on Mojave, assuming one can still build against
> it there, may well be a short-term answer.
Mojave requires Xcode 10 which contains only the 10.14 SDK.
MacPorts doesn't have any particular support at this
On Sep 19, 2018, at 10:25, m...@macports.org wrote:
> On Sep 19, 2018, at 6:35 AM, Vincent Habchi wrote:
>
One specific change in Mojave is the deprecation of 32-bit software.
Mojave can run existing 32-bit software but can't build 32-bit software
anymore [3] so MacPorts can't
An addendum to my previous email about macOS Mojave, for users of Wine:
Wine is at its core 32-bit software. On 64-bit systems we offer the Wine ports
with the universal variant, but the 64-bit parts are add-ons that don't
function without the 32-bit parts. But since we can't build 32-bit softwa
Apple has announced [1] that macOS Mojave (10.14) will be released on September
24, 2018. Mojave removes support for some older Macs; see the system
requirements for more details [2].
As with any new macOS release, there are likely to be problems with several
ports on this new macOS version, wh
On Sep 11, 2018, at 01:34, Werner LEMBERG wrote:
> * Where can I get a concise and up-to-date description of
> portfiles? `portfiles.7' seems to be heavily out of date...
What would you like to know?
>>>
>>> A list of all available variables/keywords, with a description.
>>
On Sep 10, 2018, at 15:18, joerg van den hoff wrote:
> issuing `help overview' (or `help {any_other_topic}') in `calc' results in
> "no such help file".
Fixed:
https://github.com/macports/macports-ports/commit/c2c413321117ca470b1ebd4680acf148a960c320
Wait an hour, then run `sudo port selfupdat
On Sep 9, 2018, at 10:23, Christopher Jones wrote:
> Note that MacPorts has a policy of not using external libraries, as far as
> possible (apart from obvious system ones) so if you aim is to have a port
> that basically allows something externally externally to pretend to be
> something MacPor
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" was the combination of an operating system name, major
>> version nu
On Sep 8, 2018, at 16:31, Werner LEMBERG wrote:
>>> * Where can I get a concise and up-to-date description of
>>> portfiles? `portfiles.7' seems to be heavily out of date...
>>
>> What would you like to know?
>
> A list of all available variables/keywords, with a description.
Yup, that's su
On Sep 8, 2018, at 20:00, Joshua Root wrote:
> 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 err
On Sep 9, 2018, at 13:49, Andrew Luke Nesbit wrote:
> I am preparing to install and configure MacPorts on a new machine that
> has been supplied by my employer. It will be used in a corporate
> network with strict access controls between the intranet and the Internet.
>
> The only option is t
Hi Werner,
On Sep 8, 2018, at 09:08, Werner LEMBERG wrote:
> macports newbie here :-)
Welcome!
> I'm running a Lion box and I'm running macports from git, which works
> just fine. I've followed the advice on LibcxxOnOlderSystems and did
>
> cxx_stdlib libc++
> buildfromsourcea
On Sep 7, 2018, at 19:25, Kenneth F. Cunningham wrote:
> On 2018-09-07, at 5:20 PM, Ryan Schmidt wrote:
>
>>> I guess the real problem is that xattr is not a dependency on almost any
>>> system, and so it should not come into the list when you look for the rdeps.
>
On Sep 7, 2018, at 19:19, Kenneth F. Cunningham wrote:
> On 2018-09-07, at 1:57 PM, Ryan Schmidt wrote:
>
>> The problem is that you are asking MacPorts to install *all* of wine-devel's
>> recursive dependencies with the universal variant:
>>
>> On Sep 7, 2
On Sep 7, 2018, at 15:42, Watson Ladd wrote:
> I'm trying to write a portfile for Macauly 2 and it is complicated by
> the fact that all the build commands have to be executed in a
> subdirectory. Does anyone have any tips? The guide doesn't seem to say
> much about this as far as I can tell.
1001 - 1100 of 1642 matches
Mail list logo
