On Apr 17, 2018, at 06:08, pagani laurent wrote:
> ---> Activating xorg-xproto @7.0.31_0
> Error: Failed to activate xorg-xproto: Image error:
> /opt/local/include/X11/X.h is being used by the active tk port. Please
> deactivate this port first, or use 'port -f activate xorg-xproto' to force
On Apr 16, 2018, at 15:50, Murray Eisenberg wrote:
> Error: Failed to fetch qrupdate: must set at least one Fortran variant
> (e.g. +gfortran, +gccX, +g95)
>
This message is printed by the compilers-1.0 portgroup, and is not customized
for the set of variants that a particular port offers:
On Apr 16, 2018, at 08:37, pagani laurent wrote:
> Here one such example :
>
> […]
> ---> Installing py36-six @1.11.0_0
> ---> Activating py36-six @1.11.0_0
> Error: Failed to activate py36-six: Image error:
> /opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-pack
On Apr 13, 2018, at 14:26, macpo...@parvis.nl wrote:
> On 2018-04-13, at 20:17, Rainer Müller wrote:
>
>> On 2018-04-13 18:21, macpo...@parvis.nl wrote:
>>> with makefile:
>>> ---
>>> pango-list-typefaces: pango-list-typefaces.c
>>>cc -o $@ -Wall -g pango-list-typefaces.c \
>>>
Thanks for the pointers! The problem was that release/base was configured to
sync from the *old* location of trunk/base (from before I moved everything but
the rsync data onto the SSD):
git -C /Volumes/RAID/var/tmp/mprsyncup/release/base config remote.origin.url
/var/tmp/mprsyncup/trunk/base
I
On Apr 12, 2018, at 11:27, Rainer Müller wrote:
> On 2018-04-12 17:42, Ryan Schmidt wrote:
>> On Apr 12, 2018, at 03:50, Clemens Lang wrote:
>>>
>>> Can you remove the -q flag and/or retry running git fetch? That should give
>>> us
>>> an id
On Apr 12, 2018, at 11:05, Chris Jones wrote:
> On 12/04/18 04:24, Ryan Schmidt wrote:
>> On Apr 11, 2018, at 21:54, Joshua Root wrote:
>>> On 2018-4-12 12:39 , Ryan Schmidt wrote:
>>>>
>>>> On Apr 11, 2018, at 10:23, Joshua Root wrote:
>>>&g
On Apr 12, 2018, at 03:50, Clemens Lang wrote:
>
> Can you remove the -q flag and/or retry running git fetch? That should give us
> an idea what went wrong here.
No change. No additional output is produced.
On Apr 11, 2018, at 21:54, Joshua Root wrote:
> 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 t
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:
2018-04-11T02:10:34+ error: pathspec 'v2.4.3' did not match any file(s)
known to git.
On Apr 7, 2018, at 15:13, Murray Eisenberg wrote:
> Would it be appropriate to open a ticket http://trac.macports.org?
No, since we were not involved in the creation of the openmodelica portfiles
nor do we host them in our repository, and we have no influence over those who
do host them to mak
On Apr 7, 2018, at 15:02, Ken Cunningham wrote:
> Also, installing both gcc5 and gcc7 and libgcc6 and libgcc just seems nutty,
> so I added gcc6 and gcc7 to the fortran variants — but that has nothing to do
> with the above.
Using both gcc5 and gcc7 in a single port would indeed be nutty, if i
On Apr 7, 2018, at 13:56, Murray Eisenberg wrote:
> On 7 Apr2018, at 2:51 PM, Ryan Schmidt wrote:
>
>> On Apr 7, 2018, at 13:50, Murray Eisenberg wrote:
>>
>>> What’s happening now is befuddling to me. Doing the step
>>>
>>> echo rsync://build.
On Apr 7, 2018, at 13:50, Murray Eisenberg wrote:
> What’s happening now is befuddling to me. Doing the step
>
>echo rsync://build.openmodelica.org/macports/ >>
> /opt/local/etc/macports/sources.conf
>
> as root (sudo su - ) seems to have worked, as
> /opt/local/etc/macports/sources.conf
On Apr 7, 2018, at 12:49, Ken Cunningham wrote:
> sounds like this software needs a port and a maintainer!
It already has a port, and a collection of hundreds of related ports, in an
entirely separate ports collection that the user must load into MacPorts in
order to use. The previous messages
On Apr 7, 2018, at 11:27, Murray Eisenberg wrote:
> Thanks, that seems to have worked.
>
> To do the remaining steps…
>
> port selfupdate
> port install gcc44 # With the addition of llvm/clang as the default compiler
> in XCode, many ports now fail to build unless you force GCC to be used
> po
On Mar 25, 2018, at 09:57, Joshua Root wrote:
> A port with no destroot phase will install no files. I doubt that is
> what you want.
Well it's technically possible to write a port that performs the destroot tasks
in an earlier phase. We'd prefer a port not do this, but some build systems are
On Mar 25, 2018, at 01:49, Jan Stary wrote:
> On Mar 24 14:14:37, Mojca wrote:
>> On 24 March 2018 at 13:54, Jan Starý wrote:
>>> The 'platforms' field of a Portfile is currently
>>> both _required_ and _ignored_. By the Guide,
>>>
>>>A list of the platforms on which the port has been te
On Mar 24, 2018, at 08:14, Mojca Miklavec wrote:
>> I propose that the 'platforms' field be no longer required
>> if it is ignored, and if it stays, let it be a free form text,
>> as opposed to a predefined definitive list of all unixes.
>
> We'll need it to specify which darwin versions are sup
On Mar 24, 2018, at 04:49, Jan Stary wrote:
> what is the plan really with libressl and libressl-devel?
> We have 2.5.5 in security/libressl, 2.6.2 in security/libressl-devel,
> and now 2.7.1 is out.
>
> I would just prepare an udate of libressl to 2.7.1,
> but I want to as kfirst: why do we have
On Mar 24, 2018, at 07:35, Andreas Falkenhahn wrote:
> When I compile my C++11 project on a 10.5 PPC system using gcc6 and try to
> run it on another 10.5 PPC system that doesn't have gcc6 installed, I get an
> error that a symbol cannot be imported from /usr/lib/libstdc++.6.dylib. I
> guess t
On Mar 22, 2018, at 18:26, Qianqian Fang wrote:
> I don't know if this si common, but when I tried to install gdb (because my
> lazarus 1.8 complains about missing gdb) using
>
> sudo port install gdb
>
> I got an error when installing the dependency package xz, with the following
> error
>
On Mar 20, 2018, at 15:32, Andreas Falkenhahn wrote:
> Where does this difference come from? On my 10.5 G5 PowerMac it really was
> just a few minutes and now it's taking hours. Yes, the G5 is faster but
> certainly not that much. To me it looked as if on 10.5 binaries were
> downloaded and insta
On Mar 20, 2018, at 08:29, db wrote:
> On 20 Mar 2018, at 00:34, Ryan Schmidt wrote:
>> Error: Unable to determine location of a macOS SDK.
>
> Could it instead be a warning?
If a port specifies that it requires an SDK, and the SDK does not exist, it is
proper for MacPorts
On Mar 20, 2018, at 17:22, Jeremy Huddleston Sequoia wrote:
> On Mar 19, 2018, at 4:34 PM, Ryan Schmidt wrote:
>
>> Ok, I've figured out that the reason why I'm not seeing the "Unable to
>> determine location of a macOS SDK" message is that I was running
Ok, I've figured out that the reason why I'm not seeing the "Unable to
determine location of a macOS SDK" message is that I was running MacPorts 2.4.2
and the message is new for MacPorts 2.5. MacPorts 2.5 considers it an error
when it can't find an SDK. MacPorts 2.4.x and earlier just returned t
On Mar 19, 2018, at 11:21, db wrote:
> On 19 Mar 2018, at 16:56, Ryan Schmidt wrote:
>> Probably an unintended consequence of one of my changes last month.
>> What version of macOS and what version of Xcode are you using?
>
> OS X 10.8.5, Xcode 5.1.1.
Hmm. I can't rep
On Mar 16, 2018, at 09:08, Marius Schamschula wrote:
> On Mar 16, 2018, at 9:05 AM, Ray Zimmerman wrote:
>
>> Octave 4.2.2 was released recently. Would love to have the octave port
>> updated, so I could benefit from the bug fixes.
>
> Waiting for maintainer: see: https://trac.macports.org/tic
On Mar 18, 2018, at 08:32, Andreas Falkenhahn wrote:
> There's just one little problem remaining: I cannot use gcc-ar-mp-6 because
> it reports the following error: "Cannot find plugin liblto_plugin.so".
> So I just use the "ar" that came with Xcode and it worked fine but maybe
> gcc-ar-mp-6 shou
On Mar 19, 2018, at 08:03, Yanni wrote:
> I'm not sure if this has anything to do with macports but I am using macports
> to install a specific software called pymol. The laptop is 10.13.3 High
> Sierra and up to date.
>
> When I try to install it ("sudo port install pymol") I get the error:
>
On Mar 19, 2018, at 10:00, db wrote:
> Today I tried syncing and it failed, see log below. It succeeded when I moved
> the portfile away. Base is from source.
>
>
> $ sudo port -v sync
> ---> Updating the ports tree
> Synchronizing local ports tree from file:///opt/local/myports
> Creating po
On Mar 16, 2018, at 03:11, Dave Horsfall wrote:
> What should I be using now?
Possibly git.
On Mar 15, 2018, at 07:18, pagani laurent via macports-users wrote:
> Hello,
>
> Running Mac OS 10.12.6, I try to install ATLAS with macports but 1) it
> selects /usr/bin/clang as a C compiler (why not the /opt/local/bin/gcc one ?),
MacPorts intentionally builds ports with specific compilers.
On Mar 11, 2018, at 21:53, Bill Cole wrote:
> On 10 Mar 2018, at 18:47 (-0500), db wrote:
>
>> Btw, how can I change the two-week period for the warning. I couldn't find
>> an option in macports.conf, either to change the period or to suppress it
>> altogether.
>
> port reclaim --disable-remi
On Mar 10, 2018, at 18:15, Lenore Horner wrote:
> I don’t know whether the fetch errors are related at all.
Nope.
> qscintilla-qt4-2.10.3_0.darwin_17.x86_64.tbz2 doesn't seem to exist in
> /opt/local/var/macports/incoming/verified
> Attempting to fetch qscintilla-qt4-2.10.3_0.darwin_17.x86_64.
On Mar 10, 2018, at 18:51, Lenore Horner wrote:
> I just tried to run port upgrade outdated and a dependency of openscad
> (qscintilla-qt4) failed to upgrade. I still have the previous version of
> that dependency listed as active and only one version of port is listed as
> installed and it i
On Mar 10, 2018, at 17:47, db wrote:
> Btw, how can I change the two-week period for the warning. I couldn't find an
> option in macports.conf, either to change the period or to suppress it
> altogether.
I don't think we offer any options to configure that. We want users to stay up
to date; w
On Mar 10, 2018, at 14:53, S. L. Garwood wrote:
> I need boost 1.65 … is it available on MacPorts? All I see is 1.66
No, MacPorts provides only the current version of a port.
Instructions for installing an older version of a port are here:
https://trac.macports.org/wiki/howto/InstallingOlderPo
On Mar 10, 2018, at 14:24, db wrote:
> On 10 Mar 2018, at 20:05, Ryan Schmidt wrote:
>> Are your port definitions in fact more than two weeks old?
>
> Yes, but I'd expect the warning after I actually ran the command.
When you press tab, the bash completion code runs. Lookin
On Mar 10, 2018, at 12:18, db wrote:
>
> bash-completion for port outputs stderr on pressing tab, right before it
> completes a word, on certain actions like contents.
>
> $ port contents bash-complWarning: port definitions are more than two weeks
> old, consider updating them by running 'port
Are any MacPorts users or developers attending South by Southwest in Austin
(March 9-18)? Maybe we could meet up.
On Mar 7, 2018, at 19:28, Dave Horsfall wrote:
>> As always, changes are described in perldelta:
>>
>> http://search.cpan.org/dist/perl-5.26.0/pod/perldelta.pod#Removal_of_the_current_directory_(".")_from_@INC
>
> Aha - all is now clear! Was there actually a port note about it that I
> missed
to patch. But since this one does offer a variable, you don't.
> On 2018-03-07, at 12:16, Ryan Schmidt wrote:
>
>> Presumably, you're meant to specify PREFIX=/opt/local in build.args.
>
> The advantage is not making a patch for Makefile.
Yes.
> combined:
On Mar 6, 2018, at 09:01, pdv wrote:
> I'm trying to local install jdupes with my own test fixes, but i cannot
> destroot/activate due to more violation.
>
> how can i - without patching the Makefile, specify /opt/local as destination?
>
> logextract:
> ---
> # port install jdupes
> --
On Mar 6, 2018, at 04:00, db wrote:
> On 6 Mar 2018, at 10:49, Ryan Schmidt wrote:
>> The portindex indexes Portfiles, not portgroups. So the port's version must
>> be set in the Portfile, not anywhere else.
>
> Would then portindex fail if the port's versio
On Mar 6, 2018, at 03:47, db wrote:
> On 6 Mar 2018, at 02:34, Ryan Schmidt wrote:
>> On Mar 5, 2018, at 05:43, db wrote:
>>> As I said in my previous post, you can get HEAD's hash with 'git ls-remote
>>> --heads'. And store it somewhere.
>> Who are
On Mar 5, 2018, at 22:09, Ryan Schmidt wrote:
> On Mar 5, 2018, at 20:06, Dave Horsfall wrote:
>
>> A script that I wrote and has worked fine for ages is now breaking with:
>>
>> Can't locate Scanner.pm in @INC (you may need to install the Scanner
>> mod
On Mar 5, 2018, at 20:06, Dave Horsfall wrote:
> A script that I wrote and has worked fine for ages is now breaking with:
>
>Can't locate Scanner.pm in @INC (you may need to install the Scanner
> module) (@INC contains:
> /opt/local/lib/perl5/site_perl/5.26/darwin-thread-multi-2level
> /o
On Mar 5, 2018, at 05:43, db wrote:
> On 5 Mar 2018, at 11:39, Ryan Schmidt wrote:
>> hash+date is specific, predictable, repeatable. The portfile developer tests
>> a specific hash+date, and when satisfied, commits it to make it available to
>> MacPorts users.
>
&g
On Mar 5, 2018, at 04:34, db wrote:
>
> I know, but I don't see how HEAD is pragmatically that much different from
> the devel ports that use a hash+date instead.
"HEAD" is not a specific version. It will vary as developers make new commits.
A user installing a port that fetches from "HEAD" wil
On Mar 4, 2018, at 11:21, Michael wrote:
> Ok, What am I doing wrong?
>
> bash-3.2# port install ffmpeg "@3.2.4_4+gpl2"
Specifying the version at install time is not a feature of MacPorts.
> ---> Computing dependencies for ffmpeg
> ---> Fetching archive for ffmpeg
> ---> Attempting to fetc
On Mar 4, 2018, at 13:07, Michael wrote:
> On 2018-03-04, at 10:41 AM, David Strubbe wrote:
>
>> I'm not sure what you saying here. MacPorts only ever links against the
>> current version of a library. Why don't you explain what kind of problem you
>> are having here, and perhaps we can help m
On Feb 27, 2018, at 13:24, Michael wrote:
> On 2018-02-27, at 10:03 AM, Ryan Schmidt wrote:
>
>> On Feb 26, 2018, at 13:40, Michael wrote:
>>
>>> :info:configure Include the log file "ffbuild/config.log" produced by
>>> configure as this w
On Feb 28, 2018, at 01:12, Jan Stary wrote:
> Back to the original problem: using depends_fetch is not a solution
> to downloads of tar.gz failing on some https sites, right? Because
> whatever the port adds to depends_fetch, the https fetching will
> still be done with the (lib)curl macports was
On Feb 26, 2018, at 00:57, Jan Stary wrote:
> On Feb 22 19:04:41, Jan Stary wrote:
>> On Feb 22 17:09:22, Rainer Mueller wrote:
>>> On 2018-02-21 20:14, Jan Stary wrote:
If I am reading https://guide.macports.org/chunked/reference.phases.html
right, there is are no "fetch dependencies".
On Feb 26, 2018, at 13:40, Michael wrote:
> :info:configure Include the log file "ffbuild/config.log" produced by
> configure as this will help
> :info:configure solve the problem.
If you could show us this file, it might help.
On Feb 24, 2018, at 16:34, Ken Cunningham wrote:
> thread_local is a c++11 feature that newer software is increasingly using. It
> is available with gcc 4.8+, and with clang since about clang-3.5. On macOS
> (darwin) it requires system supports that arrived in 10.7.
>
> My goal is to get thre
On Feb 22, 2018, at 20:04, Ken Cunningham wrote:
> or until we bundle in libcurl.
Note that bundling libcurl is insufficient to fix the issue; we would have to
bundle an ssl library too, and there was an objection that we don't want to be
in the business of needing to quickly release a new ver
The fix:
https://trac.macports.org/ticket/55878
On Feb 22 18:54:18, Jan Stary wrote:
> One of the libraries in MP providing SSL functionality is WolfSSL.
> Only two other ports mention it:
>
> sysutils/gearmand explicitly disables it
> net/curl has a +wolfssl variant (beside +ssl, +darwinssl, etc).
>
> Is anyone using it? Would there be any o
On Feb 21, 2018, at 13:14, Jan Stary wrote:
>
> Would it make sense
> to introduce fetch dependencies just like we have build dependencies
> and run dependencies, so that the affected ports could specify e.g. curl,
> and MP vuld use _that_ for those ports?
As was mentioned, depends_fetch exists.
On Feb 20, 2018, at 08:34, Joshua Kordani wrote:
> Not the OP, but regarding DYLD_LIBRARY_PATH, I don't understand how to make
> use of dylib's provided by macports in my own programs without setting this
> flag. I've read in several places that, esp with macports, this should not
> be necess
On Feb 19, 2018, at 13:37, Qianqian Fang wrote:
> I don't know what was changed recently, the built-in git command from Xcode
> stopped working with the following error
>
> fangq@jinwy:~/space/git/Project/autobuild/mcx$ git pull
> dyld: lazy symbol binding failed: Symbol not found: _iconv_open
On Feb 14, 2018, at 13:46, Ken Cunningham wrote:
> On 2018-02-14, at 5:56 AM, Ryan Schmidt wrote:
>
>
>> We will definitely never offer a user-facing feature for building the HEAD
>> version of a port's code.
>
>
> I completely recognize why you stick wi
On Feb 14, 2018, at 17:16, db wrote:
> On 14 Feb 2018, at 14:56, Ryan Schmidt wrote:
>> I'm aware of "cask" being a feature of Homebrew. If that's what you're
>> referring to, what does the feature do / what do you want MacPorts to do in
>> regard
On Feb 14, 2018, at 17:42, Michael wrote:
>> I think we should look at ways in which MacPorts is harder to use and see if
>> we can address those.
>
> I'd say that being able to install software without having to use sudo would
> be my number one.
Step 1: edit the sudoers file so that you are
On Feb 13, 2018, at 08:40, db wrote:
> On 13 Feb 2018, at 07:01, Ken Cunningham wrote:
>> If there is anything worth having in MacPorts that is in Homebrew but not
>> MacPorts, just ask for it.
>
> I'm trying homebrew as a fallback for MacPorts, but since you said anything,
> here's a wish list
On Feb 13, 2018, at 05:07, Jan Stary wrote:
> On Feb 13 10:08:02, miniu...@free.fr wrote:
>> Are you sure the command line development tools from Xcode are properly
>> installed ?
>>
>> $ xcode-select -p
>
> /Applications/Xcode.app/Contents/Developer
>
> And indeed, mkdep is not there.
> But w
On Feb 10, 2018, at 03:23, James Linder wrote:
> On 10 Feb 2018, at 3:15 am, dan d. wrote:
>
>> What is the shutdown message in terminal? If it is the one requesting
>> confirmation it can be turned off in terminal system preferences.
>
> “You have 6 processes running, do you want to review t
On Feb 10, 2018, at 03:23, James Linder wrote:
> iTerm’s preference for middle mouse IS paste but clicking the tab bar kills
> and exits the tab. I can find no options to confirm this it is just gone.
>
> I’m somewhat knackered being right handed but having to use left due to MS.
> Operation wo
On Feb 9, 2018, at 00:46, James Linder wrote:
> I’ve been using iTerm2 for a while but the 100th time I accidently
> middle-mouse clicked the tab bar only to have the tab be-gone usually in vi I
> binned it.
> Terminal is a pretty good replacement except it askes stupid questions every
> time
On Feb 4, 2018, at 16:05, Rainer Müller wrote:
>> nickel% ls -ltrd /opt/local/var/macports/portdirs/ports/*dex*17*
>> drwxr-xr-x 4 500 505 128 Jan 30
>> 15:17 /opt/local/var/macports/portdirs/ports/PortIndex_darwin_17_i386/
>
> This looks like the directory belongs to a user id that has no
>
On Jan 29, 2018, at 18:15, Jepeway, Chris wrote:
> I'm looking to use & build ports offline, without any direct internet access.
>
> Is this possible?
>
> I've got a recent install of MacPorts via the v2.4.2 disk image.
>
> I've got a copy of ports.tar.
>
> I've got an rsync'ed set of distfil
On Jan 28, 2018, at 09:17, Stephen Rasku wrote:
> I just enabled bash-completion for MacPorts but the already installed
> ports didn't have this enabled. I would like to upgrade the installed
> ports to enable this variant. Eventually, I would like to do this for
> all installed ports but I am
On Jan 27, 2018, at 06:04, Jan Stary wrote:
>> --- libsndfile-1.0.28/programs/sndfile-play.c.orig 2018-01-26
>> 23:13:33.0 +0100
>> +++ libsndfile-1.0.28/programs/sndfile-play.c2018-01-26
>> 23:15:17.0 +0100
>> @@ -61,7 +61,9 @@
>>
>> #elif (defined (__MACH__) && defi
On Jan 21, 2018, at 02:47, Bill Cole wrote:
> The worst problem generally on SL is the trickle of creeping C++11
> dependencies that have made it essentially mandatory to do this:
> https://trac.macports.org/wiki/LibcxxOnOlderSystems and then hack around
> breakage in ports like lz4 that blind
On Jan 20, 2018, at 14:55, Uli Wienands wrote:
> Ok, I did selfupdate Macports and tried again, and indeed it now gets past
> this hurdle.
>
> However, at the end it tells me that all compilers are blacklisted & it will
> default to first fall-back option (whatever that is)_. It then wants to
On Jan 20, 2018, at 17:11, Richard L. Hamilton wrote:
> The lspci command might be handy for those not wishing to parse native tools
> in hopes of finding similar info.
>
> The version at https://mj.ucw.cz/sw/pciutils/ built easily enough for me,
> although it does require boot-args debug=0x1
On Jan 20, 2018, at 02:47, Jan Stary wrote:
> On Jan 20 02:27:23, Ryan Schmidt wrote:
>
>> On Jan 19, 2018, at 15:42, Jan Stary wrote:
>>
>>> On Jan 19 14:18:00, Chris Jones wrote:
>>>> The point is third party applications (and perhaps even some Apple
On Jan 19, 2018, at 15:15, Dave Horsfall wrote:
> On Fri, 19 Jan 2018, Jan Stary wrote:
>
>> This is MacOS 10.13.2. Is this expected? I see it but I don't believe it.
>
> MacOS has a broken filesystem; case is preserved but not honoured i.e. "file"
> is the same as "FILE" is the same as "FiLe"
On Jan 19, 2018, at 15:42, Jan Stary wrote:
> On Jan 19 14:18:00, Chris Jones wrote:
>> The point is third party applications (and perhaps even some Apple stuff) is
>> not well tested on anything other than the defaults. So its far from
>> impossible for there to be applications that internally a
On Jan 19, 2018, at 12:41, Clemens Lang wrote:
> On Fri, Jan 19, 2018 at 03:53:15PM +0100, db wrote:
>> But since this is MacPorts, I wonder if anyone has had problems
>> specifically with a port not working and crashing.
>
> Remember that our buildbots use case-sensitive HFS, so we would usuall
On Jan 19, 2018, at 11:46, Franco Vaccari wrote:
> Here it is, but I wonder whether such a SSL version requirement is
> per-package, because I had no problem in installing a large number of
> packages before finding this issue.
The people who run the servers that distribute python-related file
On Jan 18, 2018, at 11:26, Bill Hill wrote:
>
> This failed with an error in deps/src/libff/libff/common/profiling.cpp
> complaining about this line :"::clock_gettime(CLOCK_PROCESS_CPUTIME_ID, &ts)"
>
> Some flailing around on google and it seems that this function only exists in
> OSX 10.12 but
On Jan 16, 2018, at 03:13, Bjarne D Mathiesen wrote:
> Ryan Schmidt wrote:
>>
>> Using the root account is not recommended; you should use an admin account
>> instead.
>>
>> If you must use the root account, and you have no admin account with which
>&g
On Jan 17, 2018, at 10:59, Riccardo Mottola wrote:
> However 10.5 runs considerably faster on 32bit macs.s and those who cannot
> take 4GB of RAM. My own experience
I see; I hadn't heard that feedback before. According to Apple, 10.6 focused
not on new features but on performance, so it should
On Jan 13, 2018, at 16:02, Tom Scott wrote:
> 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 sure where to direct it.
>
> I’m using MacOS high Sierra 10.13.2 and prior to installing Macports Xcode
> 9.2 was inst
On Jan 14, 2018, at 14:47, Mojca Miklavec wrote:
> On 14 January 2018 at 11:40, Chris Jones wrote:
>>
>> A buildbot exists for PPC, but not intel
>>
>> The assumption I believe being if you have an intel machine, you should
>> update at least to 10.6... the 10.5 buildbot exists because that is
On Jan 14, 2018, at 19:26, Bjarne D Mathiesen wrote:
> The 10.13.2 supplemental update in-activates the root account if enabled
> Luckily, on the machines I've updated, I also had a normal admin
> account, so no big deal ; but I also have a machine with no normal admin
> account, so if it does th
On Jan 12, 2018, at 08:14, Bill Cole wrote:
> On 12 Jan 2018, at 8:49 (-0500), Ryan Schmidt wrote:
>
>> On Jan 11, 2018, at 11:31, Vincent Habchi wrote:
>>
>>> Alternatively to what Ryan just mentioned, you can statically link the
>>> executable, which m
On Jan 11, 2018, at 11:31, Vincent Habchi wrote:
> Alternatively to what Ryan just mentioned, you can statically link the
> executable, which means that you embed all the code the executable and its
> dependencies need into the main code. This result in a bigger executable
> (more code) but le
On Jan 12, 2018, at 07:40, db wrote:
> On 18 Nov 2017, at 20:38, Ryan Schmidt wrote:
>> It is preferable to install MacPorts with root (administrator) privileges
>> and to run it with sudo. This is more secure, because, with those
>> privileges, MacPorts can drop p
On Jan 11, 2018, at 10:23, Michael wrote:
> On 2018-01-11, at 4:37 AM, Ryan Schmidt wrote:
>
>> openssl provides libssl.1.0.0.dylib. The absolute path
>> /opt/local/lib/libssl.1.0.0.dylib is baked into the lynx executable as a
>> library that it needs in order to run
On Jan 11, 2018, at 01:08, Jan Stary wrote:
> On Jan 10 15:53:59, Daniel Luke wrote:
>> On Jan 10, 2018, at 2:49 PM, Jan Stary wrote:
>>> these ports specify a hard dependency on openssl with "port:openssl".
>>
>> is libressl now ABI compatible with openssl? IIRC some ports moved from path
>> ba
On Jan 11, 2018, at 01:05, Jan Stary wrote:
> On Jan 10 14:20:21, Ryan Schmidt wrote:
>
>> On Jan 10, 2018, at 14:03, Jan Stary wrote:
>>>
>>> $ port installed depends:libressl
>>> None of the specified ports are installed.
>>
>> This r
On Jan 10, 2018, at 14:03, Jan Stary wrote:
>
> $ port installed depends:libressl
> None of the specified ports are installed.
This result means: of the ports that specify a dependency containing the
substring "libressl", you don't have any installed.
> Obviously,
>
> $ otool -L /opt/loca
On Jan 6, 2018, at 21:56, Richard L. Hamilton wrote:
> Given that 32-bit support may be reduced by future OS versions, it would be
> good to know what ports or variants only build 32-bit.
>
> If there is already a list, a pointer to a list or a way to discover this, it
> might be FAQ-worthy gi
It's already been reported to us:
https://trac.macports.org/ticket/55643
On Jan 5, 2018, at 17:49, Dave Horsfall wrote:
> On Fri, 5 Jan 2018, Ryan Schmidt wrote:
>
>> If you have been using perl5.24 and p5.24 modules for your own projects and
>> now want to use perl5.26, simply install the p5.26 versions of the modules
>> you want.
>
&g
On Jan 5, 2018, at 06:11, Clayson wrote:
> Dear Ryan,
>
> Have you had a chance to look at this? I’ve been told by several rresponders
> to my qurestion that Quartz is of course in ALL recent Mac system BUT my
> question was not that.
>
> Instead I was asking about: when I install python usin
1201 - 1300 of 1642 matches
Mail list logo
