On Dec 21, 2020, at 12:55, Michael wrote:
> This should be a simple one. I hope.
>
> I just installed a program that was compiled against the release version of
> mac's X11. Crashes on startup with this:
>
> dyld: launch, loading dependent libraries
>
> Dyld Error Message:
> Library not
On Dec 21, 2020, at 14:52, Christoph Kukulies wrote:
> Excuses if is not actually a macports issue but I’m a bit lost.
>
> I’m about to build this:
> https://gitlab.com/LinkiTools/binutils-gdb
>
>
> /Users/kuku/Downloads/binutils-gdb-users-ARM-embedded-gdb-master-2018q4/
>
>
>
>
>
On Dec 21, 2020, at 21:01, Michael wrote:
> OK. Next question: Is there any reason I cannot install libpng version 15 at
> the sametime?
>
> I am aware that there is a non-versioned link file, that the latest version
> of the dynamic library installs. That can stay at 16 where it belongs. I
On Dec 29, 2020, at 00:55, James Linder wrote:
> I posted this to mythtv-users, but I wondered in anyone had any interest. The
> obvious first step is wrapping John's work in a port.
>
> -
> John (Hoyt) did a stellar job getting the macos/ansible build
On Dec 28, 2020, at 19:09, Tom Gederberg wrote:
> I updated my system to Big Sur and followed the MacPorts migration
> instructions and updated Xcode to version 12.3.
>
> However, when I try to build ports in MacPorts, I now get the following
> warnings.
>
> Warning: The macOS 11.1 SDK
On Dec 21, 2020, at 20:55, Ken Cunningham wrote:
> There are likely to be more libraries missing after you fix this one, but you
> can try.
>
> EIther symlink a real library that is the same or as similar as you have into
> the position being looked for:
>
> sudo ln -s
On Nov 21, 2020, at 15:42, Curtis Matz wrote:
> I’m receiving this error on Big Sur. Does anyone have thoughts on how to fix
> this?
>
> sudo port clean fpc
> sudo port install fpc
>
> :info:build
> /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.
>
On Nov 21, 2020, at 19:32, Vahid Askarpour wrote:
> In attempting to install grace, my Mac crashes losing internet connection.
> The stall occurs when trying to fetch the following package:
>
> Attempting to fetch p5.28-xml-entities-1.0.200_0.darwin_20.noarch.tbz2 from
>
On Dec 6, 2020, at 11:31, Murray Eisenberg wrote:
> Any chance of povray being fixed to avoid the fatal build errors reported
> already at https://trac.macports.org/ticket/60961?
>
> I note that no maintainer is listed (from sp info --maintainer povray or on
> the ticket).
Working on it.
On Dec 6, 2020, at 15:59, Murray Eisenberg wrote:
> My mistake in calling the learning system WIMS a port — it is not. Rather, it
> is a separate download, from:
>
>
>
On Dec 5, 2020, at 19:51, Murray Eisenberg wrote:
> Those instructions say that if the older versions have been uninstalled —
> which I did do — then to start by searching in the repositiry — which I did.
> But I don’t see any History item for that port.
The history of the bison portfile is
On Dec 6, 2020, at 12:23, Murray Eisenberg wrote:
> I just installed the openscad port and find that nearly all its menu items in
> the installed GUI OpenSCAD.app are in Russian, in which I’m rather rusty.
>
> How can that language be changed? I tried its preferences but found no
> language
On Dec 6, 2020, at 15:52, Richard L. Hamilton wrote:
> I'm going to play devil's advocate on this and another post (with competing
> positions, so don't feel bad).
>
> MacPorts knows the library dependencies of a port. While it does not now
> (AFAIK) record the specific versions of each
On Dec 6, 2020, at 09:31, Riccardo Mottola wrote:
> I can think of two scenarios:
>
> - building "always safe" binaries which can be used at system level, e.g.
> login shells, tools, things put in launchd. That is things you want to always
> work, even if you are during a MacPorts upgrade.
On Dec 6, 2020, at 16:00, Murray Eisenberg wrote:
> On 6 Dec2020, at 3:49 PM, Ryan Schmidt wrote:
>>
>>
>>
>> On Dec 6, 2020, at 12:23, Murray Eisenberg wrote:
>>
>>> I just installed the openscad port and find that nearly all its menu it
On Dec 6, 2020, at 11:13, Richard L. Hamilton wrote:
> Of course, that also requires that every library port it depends on builds a
> static version as well as a shared version.
>
> So I would imagine, even given the argument in favor of limited static
> executables, that there would be at
On Dec 6, 2020, at 15:27, Dave Horsfall wrote:
> On Sun, 6 Dec 2020, Riccardo Mottola via macports-users wrote:
>
>> I can think of two scenarios [ for static binaries ]:
>> - building "always safe" binaries which can be used at system level, e.g.
>> login shells, tools, things put in
On Dec 5, 2020, at 01:23, Ken Cunningham wrote:
> On 2020-12-04 11:07 p.m., Ryan Schmidt wrote:
>> I can't think of a reason why we would want to offer such a thing.
>>
> You probably noticed some specifically asked how this would be done one
> question before, which
On Dec 6, 2020, at 16:44, Richard L. Hamilton wrote:
> Why should that change? You don't pre-build binaries for more than a few very
> common variants, so you wouldn't do so for static variants using such a
> capability.
True, we only build the port's default variants (and universal, if
On Dec 7, 2020, at 01:01, Jeffrey Walton wrote:
> Static linking also allows you to move binaries around the filesystem
> with dicking around with otool and install_name_tool.
Since programs are linked to libraries by their absolute path, you can move a
program anywhere in the filesystem
On Dec 6, 2020, at 18:40, Richard L. Hamilton wrote:
> I was thinking about port mpkg or port mdmg as an alternative, but since it
> looks like that may put its files in the same place as the MacPorts
> installation on which it was created does, it's not practical for anything
> except
On Dec 4, 2020, at 19:52, Timothy Allison wrote:
> I have been using kmymoney on my Macs for many years now. I stupidly
> upgraded to Big Sur a month ago, and have been paying the price with
> kmymoney4 for about a month.
> Now that qt4 installs, kmymoney4 fails because gwenhywfar4 fails
On Dec 4, 2020, at 09:18, Alejandro Imass wrote:
> quick question: is Apple using more or less the same stack and toolchain i.e.
> Mach + FBSD backbone and LLVM, etc. ? or has something very important changed
> for Apple silicon?
The very important thing that has changed is that Apple
On Dec 4, 2020, at 20:24, Jeffrey Walton wrote:
> On Fri, Dec 4, 2020 at 8:53 PM Timothy Allison wrote:
>>
>> I have been using kmymoney on my Macs for many years now. I stupidly
>> upgraded to Big Sur a month ago, and have been paying the price with
>> kmymoney4 for about a month.
>> Now
On Dec 4, 2020, at 21:32, Ken Cunningham wrote:
> On 2020-12-04 6:56 p.m., Ryan Schmidt wrote:
>> The reason for this is that ports.macports.org only shows status for ports
>> that were built directly. It does not show status for ports that were built
>> indirectly
&
> On Dec 4, 2020, at 21:19, Michael wrote:
>
>> Error: Can't install oniguruma6 because conflicting ports are active:
>> oniguruma5
>> Error: Problem while installing oniguruma6
>> Error: Follow https://guide.macports.org/#project.tickets to report a bug.
>> bash-3.2#
>
> What is
On Dec 5, 2020, at 00:09, Ken Cunningham wrote:
> There was a nice tweak put forth by -- I think it was Bill Cole -- to link a
> port statically. I used it for bash and gmake, but the idea might work for
> other ports too.
>
>
> See
>
On Dec 4, 2020, at 02:58, Christopher Jones wrote:
> On 4 Dec 2020, at 2:36 am, Michael wrote:
>
>>> ---> Computing dependencies for libgcc
>>> The following dependencies will be installed: libgcc10
>>> Continue? [Y/n]: y
>>> ---> Activating libgcc10 @10.2.0_3
>>> Error: Failed to activate
On Dec 4, 2020, at 20:27, Jeffrey Walton wrote:
> On Fri, Dec 4, 2020 at 9:26 PM Ryan Schmidt wrote:
>
>> On Dec 4, 2020, at 20:24, Jeffrey Walton wrote:
>>
>>> On Fri, Dec 4, 2020 at 8:53 PM Timothy Allison wrote:
>>>>
>>>> I have be
On Dec 4, 2020, at 15:50, Mojca Miklavec wrote:
>
> You should be able to install MacPorts and many ports. But you should
> not be surprised if you hit some that will refuse to build and you may
> need to wait for upstream to fix the issue (or try to fix it yourself
> and submit a patch or
> On Dec 4, 2020, at 20:51, Jeffrey Walton wrote:
>
> On Fri, Dec 4, 2020 at 9:38 PM Ryan Schmidt wrote:
>>
>> On Dec 4, 2020, at 20:27, Jeffrey Walton wrote:
>>
>>> On Fri, Dec 4, 2020 at 9:26 PM Ryan Schmidt wrote:
>>>
>&g
On Dec 4, 2020, at 21:09, Richard L. Hamilton wrote:
> If there was a port-level view of how the buildbots are doing (maybe there is
> and I haven't found it?) that might come close.
There is no such feature at this time.
> But from what little I figured out looking at the buildbot pages,
On Dec 3, 2020, at 11:44, K Hindall wrote:
> I have never been a coder, which is why I have Macports.
>
> Now I need a static ffmpeg file (to run ff·Works, thereby proving that I am
> not a coder!). I know that Macports uses dynamic libraries rather than static
> ones and somehow that
On Dec 4, 2020, at 16:00, James Secan wrote:
> I think a large number of us are very interested in the status of ports
> vis-a-vis both Apple Silicon (M1) and Big Sur. Some sort of simple
> red-yellow-green status board for ports that have been checked would be very
> useful.
Unfortunately
On Dec 4, 2020, at 08:58, Jonathan Stickel wrote:
> I'm not sure why `reclaim` doesn't provide such an option.
Because nobody has contributed the code to implement it.
https://trac.macports.org/ticket/60754
On Dec 8, 2020, at 02:42, Ken Preslan wrote:
> On Mon, Dec 07, 2020 at 03:41:57PM -0500, Justin Vallon wrote:
>> I currently use a VNC server on a debian machine, and a VNC client on my
>> Mac. I am trying to configure my Mac to run the Xserver/VNC server so that
>> I don't need to
On Dec 8, 2020, at 23:44, Ken Preslan wrote:
> My main problem was performance. In the Mojave time-frame the xorg server
> was updated from 1.18 to 1.20. Performance for xterm scrolling tanked. It
> was unusable. I complained on macports-users on April 1st 2019. There was a
> thread
On Dec 8, 2020, at 07:54, James Linder wrote:
> Sorry about the subject line: macports is my only digest mail and I keep
> forgetting :-(
Note that just changing the subject line of your reply to match the thread's
subject is not enough to preserve threading. You would also have to use the
On Dec 7, 2020, at 13:56, Dominik Reichardt wrote:
> Thank you, that helps the first step, but does it need to be a patch with
> source in the net, or can I manage this with local source as well?
You can put a patchfile in a "files" directory (in the same directory as the
Portfile) (this is
On Nov 27, 2020, at 09:15, Giovanni Cantele wrote:
> is there any ongoing project for porting the whole macports staff on the new
> Apple silicon architecture?
> What happens to those who extensively make use of macports and have bought
> the recent released MacBook Pro running on the new
On Nov 27, 2020, at 15:50, Kevin Horton wrote:
> I'm apparently a slow learner, but once again I forgot to change my login
> shell back to one supplied by Apple before migrating to Big Sur (I had been
> using.
>
> Suggestion - add a step to the Migration docs, before the step that removes
On Nov 27, 2020, at 18:25, Riccardo Mottola wrote:
> However, only native Cocoa apps wil install an .app bundle inside the
> MacPorts folder. E.g. emacs, gimp do that if they are compiled in the
> "+quartz" variant. Other apps if not Mac native will have their own launch
> method which will
On Nov 28, 2020, at 08:32, Joshua Root wrote:
> Ryan Schmidt wrote:
>> We have tens of thousands of ports in MacPorts and it's not always clear to
>> us which ones people use.
>
> That at least can be easily remedied by installing the mpstats port. You
> sh
On Nov 23, 2020, at 21:27, Jeff Greenberg wrote:
> :debug:archivefetch openssl output: couldn't create error file for command:
> permission denied
This message has been seen a few times before and a common cause seems to be
that your tmp directory does not have the right permissions. See:
On Nov 29, 2020, at 06:24, Riccardo Mottola wrote:
> On 2020-11-17 00:30:33 +0000 Ryan Schmidt wrote:
>
>> On Nov 16, 2020, at 17:58, Riccardo Mottola wrote:
>
>>> Here were are in the situation that if, for some upstream reason, libxml2
>>> stops com
On Dec 18, 2020, at 13:32, DaveC wrote:
> The primary failure yesterday of youtube-dl gave this verbose output.
>
> Dave
> - - -
> Daves-Mac-mini:~ davec$ youtube-dl -v -x
> https://www.youtube.com/watch?v=RXawa90YU2s
> [debug] System config: []
> [debug] User config: ['--output',
On Dec 18, 2020, at 14:28, Clemens Lang wrote:
>> 2. Next time(?) I update MP I presume YouTube-dl won’t update. Will it
>> be removed? Will it no longer work? Is there a way to keep the port I
>> have currently functioning?
>
> MacPorts mirrors the upstream files, so even if youtube-dl were
On Dec 14, 2020, at 16:26, Carlo Tambuatco wrote:
> I have python38 installed via macports. It is the default python
> via python_select.
>
> I don’t think I should file a ticket in this case because this error isn’t
> local to the python(s)
> installed via macports. It even occurs when
> On Dec 9, 2020, at 01:30, list_email--- wrote:
>
>
>> On Dec 6, 2020, at 9:35 AM, Ken Cunningham wrote:
>>
>> of course the simplest method of reverting to an older binary is to just
>> reactivate it if you still have it installed, but inactive, after an update.
>>
>> This will show you
On Dec 12, 2020, at 15:23, dan d. wrote:
> Does a binary, like lynx the browser, work over several versions of os10. I
> have one older machine which version is 6 upgrades removed from
> the most recent one. Will that lynx continue to work if most of the versions
> are skipped by
On Nov 7, 2020, at 12:46, Riccardo Mottola wrote:
> I need to rebuild a package which is not working due to a dependency upgrde.
> revdep "catches" it but revdep fails to build it because it uses the wrong
> compiler and I need to force it (also because the compiler itself is broken
>
On Nov 9, 2020, at 16:51, Greg Earle wrote:
> On 7 Nov 2020, at 1:43 AM, Ryan Schmidt wrote:
>
>> Do what it says and clean the affected ports.
>>
>> sudo port clean expat
>>
>> sudo port clean db48
>
> Thanks Ryan. That just pushed it down the
On Nov 11, 2020, at 22:27, Dave Horsfall wrote:
> On Wed, 11 Nov 2020, Ryan Schmidt wrote:
>
>> Apple has announced that macOS 11 Big Sur will be released tomorrow,
>> November 12, 2020. In the coming days we will either release an installer
>> for Mac
On Nov 12, 2020, at 23:08, Richard L. Hamilton wrote:
> One or two times past, an Xcode version around the time of a new OS release
> has been a problem on the older OS.
>
> I don't see anything likely to be that way with Xcode 12.2 (and MacPorts) on
> Catalina, but I'm looking for
On Nov 13, 2020, at 17:45, Riccardo Mottola wrote:
> On 2020-11-08 08:18:22 +0100 Ryan Schmidt wrote:
>
>> On Nov 7, 2020, at 12:46, Riccardo Mottola wrote:
>>> I need to rebuild a package which is not working due to a dependency
>>> upgrde. revdep "ca
Perhaps the action is remembered somewhere in Xcode?
>
> On 11/15/20 17:28, Ryan Schmidt wrote:
>>
>> On Nov 15, 2020, at 16:53, John Chivian wrote:
>>
>>> For me, every time Xcode is updated, the first time I start it following
>>> its update
On Nov 15, 2020, at 16:53, John Chivian wrote:
> For me, every time Xcode is updated, the first time I start it following its
> update I am prompted to update components,
Yes.
> and the current version command line tools are installed.
No. "Components" are not "command line tools". You
On Nov 14, 2020, at 14:31, Ken Cunningham wrote:
> I’m not positive, but I think at one point in time macports base added this
> flag to most or all builds, but that went by the wayside when most builds
> became 64bit intel.
>
I have no recollection of that being the case, and searching the
On Nov 14, 2020, at 17:53, Jonathan Allen wrote:
> I fully installed the Mac Ports application successfully, and then once that
> was finished I entered “sudo port install homebank” in the command line, no
> errors were presented. I then went to the “MacPorts” folder in the
> Application
On Nov 16, 2020, at 02:55, Dominik Reichardt wrote:
> Yes, everyone replying that you have the CLT installed, check if it’s
> actually the correct one. Because apparently there is a bug that makes Xcode
> report that the CLTs are installed *without* checking whether it is the
> correct
On Nov 16, 2020, at 02:40, Andrew Udvare wrote:
> I have a PR here to update the QLColorCode port
> https://github.com/macports/macports-ports/pull/9138 and while everything
> builds, the highlight functionality of this does not work.
>
> One observation: /opt/local/lib/liblua.dylib (port:
On Nov 16, 2020, at 17:32, raf wrote:
> On Sun, Nov 15, 2020 at 11:56:54AM -0600, Ryan Schmidt wrote:
>
>> You should definitely never run with a mismatched set of Xcode and its
>> command line tools. Either update the command line tools to the Xcode
>> 12.2 ve
On Nov 16, 2020, at 17:58, Riccardo Mottola wrote:
>
> Ryan Schmidt wrote:
>>> So I have to force the "gcc-4.2" of xcode... that one works (and, luckily,
>>> libxml2 still compiles with it)
>> My point is that "sudo port upgrade outdated"
> On Nov 18, 2020, at 10:39, Peter Hancock wrote:
>
> On 13/11/2020 10:42, Ryan Schmidt wrote:
>> On macOS 10.15, you can avoid even more problems by limiting yourself to
>> Xcode 11.7 and the Xcode 11.5 version of the command line tools. Upgrading
>> to Xcode
On Nov 14, 2020, at 06:05, Joshua Root wrote:
> The MacPorts Project is pleased to announce the release of version
> 2.6.4. This is a bugfix release with small changes only. See the
> ChangeLog [1] for the list of changes.
Thank you, Josh, for doing this release. I know it takes time to
On Nov 16, 2020, at 13:17, Andrew Udvare wrote:
> On 16/11/2020 11:45, Ryan Schmidt wrote:
>> You get this error when doing what?
>
> This happens when I try to load a preview.
>
> 1. Load Finder
> 2. Pick a file that would load a preview with it like a shell script t
On Nov 17, 2020, at 20:04, Jim DeLaHunt wrote:
> Hi, folks:
>
> In doing my daily `sudo port selfupdate` on 16 November UTC, I encountered a
> warning which is new to me:
>
> "Warning: No port […portname…] found in index"
>
> In redoing `sudo port selfupdate`, this warning did not reoccur.
On Nov 22, 2020, at 05:34, Vahid Askarpour wrote:
> I have AMP for endpoints but disabling it did not change the outcome. I will
> just wait until the .darwin_20.* package becomes available and then try again.
I'm hoping the perl modules will be done in a couple days.
You can also try building
On Nov 11, 2020, at 10:06, Ryan Schmidt wrote:
> Apple has announced that macOS 11 Big Sur will be released tomorrow, November
> 12, 2020. In the coming days we will either release an installer for MacPorts
> 2.6.3 for macOS 11 or will release a new version of MacPorts with i
Please keep the discussion on the mailing list by using the Reply All button in
your mail program.
On Nov 15, 2020, at 11:18, Kevin Horton wrote:
> Caution - It looks like some recent macOS update fiddled with the preferences
> in Software Update. I found this morning that XCode on one Mac
On Oct 28, 2020, at 02:31, Fielding, Eric J (US 329A) wrote:
> I just upgraded my MacBook to Catalina 10.15.7 from 10.14.6 and I installed
> the latest Xcode 12.1. I started Xcode and agreed for it to install required
> components. When I tried to run “xcode-select –install” it asked me to
Don't forget to Reply All so the conversation stays on the list.
On Dec 26, 2020, at 05:06, Christoph Kukulies wrote:
> There were times in history where implicit function declarations were not
> considered as an error (consulting my book „The C programming language by
> Kernighan/Ritchie“
>
On Dec 29, 2020, at 20:12, Kevin Horton wrote:
> On Dec 29, 2020, at 17:20, Ken Cunningham wrote:
>>
>> Interesting.
>>
>> /opt/local/Library/Frameworks/wxWidgets.framework/Versions/wxWidgets/3.0/lib/libwx_osx_cocoau_core-3.0.0.4.0.dylib
>> and
>>
On Dec 29, 2020, at 20:28, Richard Bonomo TDS personal wrote:
> My system runs MacOS 10.12 (Sierra). I've used Macports for some time every
> now and again.
>
> However, when I tried to use it recently, this happened:
>
> **
> $ port version
>
On Dec 29, 2020, at 12:21, Richard L. Hamilton wrote:
> Saw the MacVim updater window recently. I would think that (if not too
> difficult) builtin updaters should be disabled (I think this came up with
> iTerm or iTerm2 or something before) in MaPorts ports, which should only be
> updated
On Dec 28, 2020, at 06:12, Christoph Kukulies wrote:
> I’m trying to compile a package „blackmagic“ (a microcontroller gdb debugging
> and flashing program addendum to gdb).
>
> It has some issues like missing packages (libftdi1 - I was able to add that
> via macports)
>
> Now I want to
Please Reply All so that the conversation stays on the list.
On Dec 28, 2020, at 20:04, Tom wrote:
> Because nearly no port is building here, I wanted to try a different
> compiler. But that is not the problem.
> And because of this error:
>
> Warning: The macOS 11.1 SDK does not appear to be
On Dec 27, 2020, at 10:11, Ken Cunningham wrote:
> However, I would float the idea it's time the buildbot and all 10.13 users
> moved to Xcode 10.
>
> Xcode 10's issues have largely been worked around by this point it seems,
> although there a couple of stragglers still.
I intentionally
On Dec 28, 2020, at 23:05, Ken Cunningham wrote:
> On Dec 28, 2020, at 3:35 PM, Ryan Schmidt wrote:
>
>> On Dec 27, 2020, at 10:11, Ken Cunningham wrote:
>>
>>> However, I would float the idea it's time the buildbot and all 10.13 users
>>> moved to Xcode
On Dec 27, 2020, at 20:06, Tom wrote:
> how can I build a port with a MacPorts gcc compiler?
> For example gcc9.
Normally, ports choose what compiler to use and you should not attempt to
override it. Why do you want to?
On Dec 30, 2020, at 17:10, raf wrote:
> Error: Error installing new MacPorts base: command execution failed
> Please run `port -v selfupdate` for details.
> Error: /opt/local/bin/port: port selfupdate failed: Error installing new
> MacPorts base: command execution failed
>
> (it was
Remember to Reply All so the conversation stays on the list.
On Dec 30, 2020, at 10:36, Richard Bonomo TDS personal wrote:
> Here are the outputs:
>
> Aquinas-276:bonomo$ lipo -info
> /opt/local/share/macports/Tcl/macports1.0/MacPorts.dylib
> Architectures in the fat file:
>
On Jan 7, 2021, at 16:26, Andrew Udvare wrote:
> Sometimes the release tarball will come with the submodule source
> https://github.com/macports/macports-ports/pull/9612#issuecomment-756376258
> but this probably depends on the project.
If a release tarball doesn't come with everything
On Jan 20, 2021, at 16:44, Murray Eisenberg wrote:
> Given that neither openscad nor kdelibs4 is currently upgrading successfully,
> what is the correct syntax to upgrade all other outdated ports?
>
> I’ve tried each of the following, but in each case it either still tries to
> upgrade one
On Jan 16, 2021, at 17:05, Kennedy, Smith (Wireless & IPP Standards) wrote:
> Did the update to BigSur last week on my MacBook Pro (13-inch, 2016, Four
> Thunderbolt 3 Ports), then tried to do my usual routine whenever there is an
> OS major version update:
>
> A. Delete /opt with a "sudo
On Jan 12, 2021, at 00:34, raf wrote:
> I treated this like a migration, recorded and uninstalled existing ports,
> then installed/upgraded macports, and then restored the ports.
>
> Mac OS X 10.6 (darwin/10.8.0) arch i386
> MacPorts 2.6.4
> Xcode 3.2.6
> SDK 10.6
>
On Jan 16, 2021, at 08:18, Peter West wrote:
> Following some general advice given earlier on the list, I had removed
> XQuartz and installed xorg-server. Now I am trying to load the rgl R library.
> At the end of the error message is
> This build of rgl depends on XQuartz, which you can
On Jan 20, 2021, at 17:32, Peter West wrote:
> I tried specifically building rgl from source. The source is available at
> https://cran.r-project.org/src/contrib/rgl_0.104.16.tar.gz.
>
> In R.app console, remove rgl package.
>
> > remove.packages(“rgl”)
> > install.packages(, repos = NULL,
On Jan 19, 2021, at 09:52, ximon wrote:
> Hi, I have a new install of macports on 11.1 BigSur. mysql8 is installed and
> works, as does the mysql client, perl 5.28 installed also. When I try to
> install p5.28-dbd-mysql +mysql8 it fails with the below log messages.
See the last paragraph of
On Jan 18, 2021, at 19:38, Tom wrote:
> how can I build clang with -ilocal option support in order to build CrossOver
> Wine for 32on64?
That's an option that Crossover added to clang. When I last looked into the
issue last year, you had to use Crossover's special version of clang, which
On Jan 18, 2021, at 06:40, Janosch Peters wrote:
> I need sparkle as a dependency for the new MacPass port. Your points about
> sparkle are of course valid. When I wrote the message I thought it might
> still be nice to give users the choice to use it or not - via a variant for
> instance.
On Jan 18, 2021, at 04:56, Peter West wrote:
> I’ve removed XQuartz (again), and installed R and R-app from MacPorts. The R
> install warned me that
> Clang compilers provided by Xcode do not support OpenMP. Some R packages
> using OpenMP may require additional
> flags in the Makevar file
On Jan 18, 2021, at 21:11, Richard L. Hamilton wrote:
> ...which is a problem given that a lot of ports were apparently changed to
> use it.
>
>
Yes, all ports that depend on jpeg were changed to depend on libjpeg-turbo
yesterday. This had been requested for years but hadn't been done
On Jan 24, 2021, at 21:26, Tong Sun wrote:
> On Sun, Jan 24, 2021 at 10:24 PM Ryan Schmidt wrote:
>>
>> On Jan 24, 2021, at 21:15, Tong Sun wrote:
>>
>>> On Sun, Jan 24, 2021 at 9:30 PM Ryan Schmidt wrote:
>>>
>>>> On Jan 24, 2021, at 18:01,
On Jan 24, 2021, at 21:42, Tong Sun wrote:
> On Sun, Jan 24, 2021 at 10:31 PM Ryan Schmidt wrote:
>
>> I found this article about how to do this. Maybe it will help?
>>
>> https://medium.com/@mreichelt/how-to-show-x11-windows-within-docker-on-mac-50759f4b65cb
>&
On Jan 24, 2021, at 18:01, Tong Sun wrote:
> For any Xserver in host, I normally just do the following in the
> docker container
>
> export DISPLAY=':0'
> xterm &
>
> and I'll be all set.
>
> However, I found that it is not the case for Xserver from macport, as
> I see my DISPLAY in my host
On Jan 24, 2021, at 21:15, Tong Sun wrote:
> On Sun, Jan 24, 2021 at 9:30 PM Ryan Schmidt wrote:
>
>> On Jan 24, 2021, at 18:01, Tong Sun wrote:
>>
>>> For any Xserver in host, I normally just do the following in the
>>> docker container
&g
On Jan 24, 2021, at 22:35, Tong Sun wrote:
> I checked the x11.app's preference, but it seems to be missing the
> capability to start the Xserver automatically when user logs in.
>
> Is it so? Any plan to add it?
The X server will start automatically when you launch any X11-using program.
This
On Jan 12, 2021, at 02:31, Steve Wardle wrote:
> On 12 Jan 2021, at 01:37, Ryan Schmidt wrote:
>
>> On Jan 9, 2021, at 12:16, Steve Wardle wrote:
>>
>>> I’ve got apache2 2.4.46 running on Big Sur 11.1 and it’s not listening on
>>> the IPv6 interfaces.
On Dec 31, 2020, at 03:12, Michael Newman wrote:
> Some months ago I upgraded the OS on a remote 2010 MacBook (the white one) to
> High Sierra (10.13.16). After the upgrade I did the recommended MacPorts
> migration without problems.
>
> I don’t visit this machine very regularly, so only
901 - 1000 of 1456 matches
Mail list logo
