Hello,
Since yesterday, I noticed that I am now getting MacPorts “macports-users
Digest” email from two different lists, one at “macosforge.org” (Vol 125, Issue
10 today) and one at “macports.org” (Vol 129, Issue 19 today). Is this a fork
of the MacPorts Users mailing list or a transition? I
umanth" <cs15btech11...@iith.ac.in>
> Date: 01-Nov-2016 12:36 PM
> Subject: Re: Error in updating macports
> To: "Ryan Schmidt" <ryandes...@macports.org>
> Cc: <macports-users-ow...@lists.macosforge.org>
>
> I've tried using different networks. With an
s it survive upgrading (or downgrading) nginx?
>
> I won’t know until it gets updated next.
If you wanted to test, you could downgrade:
https://trac.macports.org/wiki/howto/InstallingOlderPort
> In any event, I don’t think it is an issue. I think when you are updating the
> po
s an
issue. I think when you are updating the port, you should relaunch the
startupitem as part of that upgrade process. What if the startupitem changed?
We can know as Macports committers, but normal users generally will not know.
So it is best practice to do such.
Cheers!
Frank
Hello Zachery,
> On Oct 7, 2016, at 8:55 AM, Zachary Waibel <zjwai...@gmail.com> wrote:
>
> Hello Ryan & Frank,
>
> Being new to the list I was not sure where to look for your response. I was
> thinking/hoping the replies would simply come to me via em
> survived reboot for me!
Does it survive upgrading (or downgrading) nginx?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
> On Oct 7, 2016, at 7:55 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>
>
>> On Oct 7, 2016, at 8:54 AM, m...@macports.org wrote:
>>
>> [Cc’ing Macports Users this time]
>>
>>> On Oct 7, 2016, at 7:39 AM, Ryan Schmidt <ryandes...@macpo
> On Oct 7, 2016, at 8:54 AM, m...@macports.org wrote:
>
> [Cc’ing Macports Users this time]
>
>> On Oct 7, 2016, at 7:39 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>>
>>
>>> On Oct 7, 2016, at 8:35 AM, m...@macports.org wrote:
>>&g
[Cc’ing Macports Users this time]
> On Oct 7, 2016, at 7:39 AM, Ryan Schmidt <ryandes...@macports.org> wrote:
>
>
>> On Oct 7, 2016, at 8:35 AM, m...@macports.org wrote:
>>
>> Hi Ryan,
>>
>>
>> Thank you for the reply. So I think t
On 10/5/16 3:28 PM, Brandon Allbery wrote:
On Wed, Oct 5, 2016 at 6:21 PM, Mick Jordan <mick.jor...@oracle.com
<mailto:mick.jor...@oracle.com>> wrote:
I have several libraries installed via MacPorts (that also exists
in /usr/lib FWIW), e.g, libpcre and libz. I was rath
On Wed, Oct 5, 2016 at 6:21 PM, Mick Jordan <mick.jor...@oracle.com> wrote:
> I have several libraries installed via MacPorts (that also exists in
> /usr/lib FWIW), e.g, libpcre and libz. I was rather surprised to see that
> these resolve to the MacPorts location,i.e., /opt/local/
> On Oct 5, 2016, at 5:21 PM, Mick Jordan <mick.jor...@oracle.com> wrote:
>
> I have several libraries installed via MacPorts (that also exists in /usr/lib
> FWIW), e.g, libpcre and libz. I was rather surprised to see that these
> resolve to the MacPorts location,i.e.
I have several libraries installed via MacPorts (that also exists in
/usr/lib FWIW), e.g, libpcre and libz. I was rather surprised to see
that these resolve to the MacPorts location,i.e., /opt/local/lib even
though I am not passing -L/opt/local/lib to the link step. I thought
this might
> On Sep 29, 2016, at 2:05 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>
>
>> On Sep 29, 2016, at 10:30 AM, Zachary Waibel <zjwai...@gmail.com> wrote:
>>
>> Here’s my question:
>>
>> I've installed the latest MacPorts and my issue is
.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
er...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
looking at any of the commands involved.)
Craig
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
s allbery kf8nh sine nomine associates
allber...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists
Apple_HFS MacOSX 999.3 GB disk0s2
3: Apple_Boot Recovery HD 650.0 MB disk0s3
/dev/disk1 (external, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme
bably need to wait for diskarbitrationd or some other daemon to be
ready. Unfortunately it looks like launchd has gone in the direction of
requiring programs to use socket, Mach port, or xpc dependencies, which
would be incompatible with a shell script. :/
Looks like on my current machine I have only one n
> On 3 Oct 2016, at 3:00 AM, macports-users-requ...@lists.macosforge.org wrote:
>
>> Over the years I?ve seen many clever people here, perchance one of them will
>> cast an eye and say THERE . . .
>>
>> I?m trying to run a rc.local at start up
>> I creat
> On Sep 29, 2016, at 3:01 PM, m...@macports.org wrote:
>
> - Edit /etc/pf.conf with your favorite text editor
> - Add the following lines to the bottom of the file:
> # Macports Apache
> pass in proto tcp from any to any port 80
> - Reboot or manually reload the firewa
> On Sep 29, 2016, at 2:05 PM, Ryan Schmidt <ryandes...@macports.org> wrote:
>
>> On Sep 29, 2016, at 10:30 AM, Zachary Waibel <zjwai...@gmail.com> wrote:
>>
>> I've installed the latest MacPorts and my issue is that if I start apache2
>> using
> On Sep 29, 2016, at 10:30 AM, Zachary Waibel <zjwai...@gmail.com> wrote:
>
> Sorry for the spam, but I have a question regarding my MacPorts installation,
> and I’m not sure if filing a ticket is the right way to go to get my question
> answered. If it is then I will do
On Tue, Sep 27, 2016 at 12:08 AM, Rainer Müller <rai...@macports.org> wrote:
> your assumptions are correct.
Thank you very much Rainer.
--
Eneko Gotzon Ares
enekogot...@gmail.com
___
macports-users mailing list
macports-users@lists.macos
On 09/26/2016 11:49 PM, Eneko Gotzon wrote:
> In the /Download and execute the restore_ports script/ section (Migration
> procedure of a MacPorts installation
> <https://trac.macports.org/wiki/Migration#Migrationprocedure>), please, how
> many
> commands are in the provi
Hi Byte Riders.
I'm sorry about this kind of questions; please, excuse me.
In the *Download and execute the restore_ports script* section (Migration
procedure of a MacPorts installation
<https://trac.macports.org/wiki/Migration#Migrationprocedure>), please, how
many commands are in the pr
>
>receiving file list ... done
>rsync: mkstemp
> "/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/.base.tar.sH7E8E"
> failed: Permission denied (13)
>inflate returned -3 (19 bytes)
>rsync error: error in rsync protocol data stream (
Upgraded recently to 10.12 Sierra, and "port upgrade" now fails:
Welcome to the RSYNC daemon on ftp.fau.de.
Not all of our mirrors are available through rsync.
receiving file list ... done
rsync: mkstemp
"/opt/local/var/macports/sources/rsync.macports.org/r
MacPorts wrote on 20160915::23:53:47 re: "Re: [MacPorts] #51689:
preserve_runtime_libraries convenience PortGroup"
>Changes (by ryandesign@…):
>
> * status: new => closed
> * resolution: => wontfix
> We've already solved this problem: whenever a port is u
ports.org/browser/trunk/dports/sysutils/python_select/files
>
> vq
You refer above to the “documentation system”. Could you be more explicit? Are
you referring to something that is part of a MacPorts installation—if so, what
is the file/directory name—or to an online document—if so what is th
e libpng port. The problem, as Ryan had already noted, is that the mechanism
for deleting .la files that is in the current base release mistakenly leaves
symlinks behind.
> is that I made a mistake when updating the OS, to have updated my MacPorts
> installation, rather than reinstal
.6.22_0
> libpng @1.6.23_0
> libpng @1.6.25_0 (active)
>
> This looks to me as though it is saying that Ryan was right. the .la file
> does not exist, only a shadow of it which presumably won’t cause any harm.
> One question: why the 6 Sept date. Would my uninstall of python have
On Tue, Sep 13, 2016 at 3:06 AM, David Epstein <david.epst...@warwick.ac.uk>
wrote:
> One thing that seems to be brought out (by the erroneous answer by “port
> provides ligpng.la
>
> ") is that I made a mistake when updating the OS, to have updated my
> MacPorts in
hanged the
date on the broken symlink?
One thing that seems to be brought out (by the erroneous answer by “port
provides ligpng.la") is that I made a mistake when updating the OS, to have
updated my MacPorts installation, rather than reinstalled. I have been
hankering after reinstal
be I’ve just been lucky. I see that
https://trac.macports.org/ticket/29172 has been there for five years now, so I
won’t hold my breath until it happens.
-Al-
--
Al Varnell
Mountain View, CA
smime.p7s
Description: S/MIME cryptographic signature
___
d /opt/local/lib/libpng.la not exist on Mavericks
> or later, it shouldn't be a symlink on any system; it should be a text file.
>
> If it's a symlink on your system, what's it a symlink to?
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
On Mon, Sep 12, 2016 at 11:02 PM, Al Varnell <alvarn...@mac.com> wrote:
> In all the years I've been using MacPorts I have never needed to reinstall
> the MacPorts base for a minor upgrade.
I think that's stated, although maybe not clearly enough. Needing to do
that on a minor u
ile is a tad buggy.
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users
n't understand security will suffer."___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
be a text file.
If it's a symlink on your system, what's it a symlink to?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
t; /opt/local/libexec/qt4/include/QtDesignerComponents is provided by: qt4-mac
>> /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers is
>> provided by: qt4-mac
>
> With regard to your remark about libpng, isn’t it the case that the MacPorts
> guide now indicat
png.la should not have existed on your system, if your OS
>>> is Mavericks or later.
>
> Now you made me curious. My OS is Sierra, and has been for about a month. I
> had installed MacPorts from sources. At first I couldn’t install much of
> anything, since I always got an error on Sierr
/include/QtCLucene is provided by: qt4-mac
>> /opt/local/libexec/qt4/include/QtDesignerComponents is provided by: qt4-mac
>> /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers is
>> provided by: qt4-mac
>
> With regard to your remark about
> On Sep 11, 2016, at 7:59 PM, David Epstein <david.epst...@warwick.ac.uk>
> wrote:
>
> In view of all my moans and groans, I would like to make it clear that I
> think MacPorts is great, and it adds greatly to my productivity. I use it all
> the time, and te
de me curious. My OS is Sierra, and has been for about a month. I had
installed MacPorts from sources. At first I couldn’t install much of anything,
since I always got an error on Sierra. About a week or so ago, things sorted
themselves out.
Since then I’ve installed 3 ports(I believe).
xfig
In view of all my moans and groans, I would like to make it clear that I think
MacPorts is great, and it adds greatly to my productivity. I use it all the
time, and tend to regard it as “Just there and working perfectly” usually
without thinking of the arduous contributions being made behind
;
> What do you get if you run that "port provides" command?
I get
% port provides /opt/local/etc/select/python3/*
/opt/local/etc/select/python3/current is not provided by a MacPorts port.]
>> A final point, that I hope is not out-of-place. On my system
>>> port
play the name of the port, if any, that provides each
>> select group entry.
>
> That's an idea, although then entries like "python27-apple" would appear to
> come from "python_select", which would be a little weird.
Provide a way for a port to override it, so that we can fix that to say that it
comes from macOS whatever.version.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
t;> provide. It might be a pain to fix that at this late date.
>
> Maybe we could also display the name of the port, if any, that provides each
> select group entry.
That's an idea, although then entries like "python27-apple" would appear to
come from "python_select", which would be a little weird.
vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
don't have the concept of files/directories shared between
>>> ports, so it just doesn't get listed and therefore doesn't get cleaned up.
>>
>> MacPorts does delete empty directories whenever a port is deactivated...
>
> But not all the files in the etc/selec
Feel free to Cc yourself on the ticket Mojca linked earlier.
https://trac.macports.org/ticket/47755
> Possibly I misunderstand, but your earlier emails seem to imply that you feel
> that the only problem with “select” in MacPorts is the creation of symlinks
> that are not deleted
ular files and directories from
>> /opt/local. Rather than spend more time on the problem, I will now move
>> /opt/local to /opt/local.old and start again from scratch.
>
> If you like, but that sounds like a lot of work to me. It didn't sound like
> there was anything par
tory are provided by the
>>> following ports:
>>
>> I think they're complaining that the directory itself should have been
>> cleaned up. We don't have the concept of files/directories shared between
>> ports, so it just doesn't get listed and therefore doesn
een
> cleaned up. We don't have the concept of files/directories shared between
> ports, so it just doesn't get listed and therefore doesn't get cleaned up.
MacPorts does delete empty directories whenever a port is deactivated...
___
macports-
frastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
/local.old and start again from scratch.
If you like, but that sounds like a lot of work to me. It didn't sound like
there was anything particularly wrong with your old MacPorts installation,
aside from a few broken symlinks created by port select, and maybe one or two
other broken symlinks whose o
on s allbery kf8nh sine nomine associates
allber...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing l
I’m not
intending to work on the problem, but only want to know when it has gone away.
Possibly I misunderstand, but your earlier emails seem to imply that you feel
that the only problem with “select” in MacPorts is the creation of symlinks
that are not deleted when uninstalling. However, I do
b/libpng.la
> /opt/local/libexec/qt4/include/QtCLucene
> /opt/local/libexec/qt4/include/QtDesignerComponents
> /opt/local/libexec/qt4/Library/Frameworks/QtCLucene.framework/Headers
vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
.5" port.
>
> vq
Thanks for clearing up my misconception/misinterpretation of the output from
“port select —summary”.
Is there a port command that would have given me this information?
David
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
s?
>
>> On Sep 11, 2016, at 1:13 AM, David Epstein <david.epst...@warwick.ac.uk>
>> wrote:
>>
>>> livm
>
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
I don’t get the correspondence between “llvm” and “livm” in your posts. Is it a
typo, or are there really two different ports?
> On Sep 11, 2016, at 1:13 AM, David Epstein <david.epst...@warwick.ac.uk>
> wrote:
>
>> livm
___
m
posed to change anything.
No, it's very clear that you haven't been mucking around inside your MacPorts
prefix. The issue is that select symlinks are not updated when the selected
port is deactivated. That is not great behavior.
vq
___
macports-users mai
ts are installed.
Port names and select entries need not match. The "mp-llvm-3.5" select entry
corresponds to the "llvm-3.5" port.
vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
ython27 as an
> option.
Why? You can't select an inactive port.
> Secondly, it seems to incorrectly and indirectly imply that python26-apple
> and python27-apple are installed, which I think was your interpretation, but
> they aren’t installed, as I have checked with t
y one is active.
I interpret the output from your system to mean that you had python27 installed
and active but now it is not active. Probably because of a command like ‘sudo
port deactivate python27 @2.7.12_1’.
You should be able to get your python back with ‘sudo port activate pytho
mp-llvm-3.5 none
I did the following
> sudo find /opt/local/ -type f -exec egrep -l llvm {} \; -print | egrep select
> | tee llvm
and found the following files
> /opt/local//etc/select/llvm/base
> /opt/local//etc/select/llvm/mp-llvm-3.5
> /opt/local//var/macports/registry/portfile
. More to the point, if the options do not include a
> MacPorts-installed one, then you can safely assume you do not have any
> related port installed. For reference, your summary reports only one setting
> for which a MacPorts port is installed: llvm 3.5 (mp-llvm-3.5) for llvm.
For th
talled, which I think was your interpretation, but they
aren’t installed, as I have checked with the “port installed” command.
It does feel as though I will, with the help of the list, be able to clean up
my ports: I had been thinking that I would have to delete everything in
/opt/local and
> On 10 Sep 2016, at 23:13, Lawrence Velázquez <lar...@macports.org> wrote:
>
… snip …
> Run this:
>
> find -L /opt/local -type l
>
> This will print any broken symlinks in your MacPorts prefix. Email the output
> to this list, and we can tell you what you
oken symlinks in your MacPorts prefix. Email the output
to this list, and we can tell you what you can safely delete.
vq
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
knowledge. By definition, uninstalling a port removes
its archive, which is how we could tell what files it installed.
IIRC the only "remnants" might be files created by a post-activate phase, which
MacPorts does not track. Deactivation should remove everything else.
Your issue is not rel
e file
describing the previously selected option was removed and therefore is not
a valid setting. More to the point, if the options do not include a
MacPorts-installed one, then you can safely assume you do not have any
related port installed. For reference, your summary reports only one
setting for wh
> Did you uninstall python27?
I think so. The ls -l command above does not find /opt/local/bin/python*,
except for symbolic links.
What port command could I give to make sure?
What port command can I give to extirpate remnants of an uninstalled port, if
there are any remna
t.
https://trac.macports.org/ticket/47755
Mojca
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
ython,
python2, and python3 select groups at some point.
> You will see that none of the files on the righthand side of the arrow ->
> appears on any lefthand side. I tried “port provides” on both lefthand and
> righthand sides and received error messages from port such as
>> /opt/
nv-3.5
You will see that none of the files on the righthand side of the arrow ->
appears on any lefthand side. I tried “port provides” on both lefthand and
righthand sides and received error messages from port such as
> /opt/local/bin/pydoc2.7 does not exist.
and
> /opt/local/bin/pydoc is
On Thu, Sep 8, 2016 at 1:55 PM, Roberto <ferro...@tiscali.it> wrote:
> Do i need to uninstall MacPorts first, before installing the CLDT and
> then reinstall MacPorts, or can I just install the missing CLDT?
Just install the command line tools.
--
brandon s a
Hello,
for some reason it happened that I installed MacPorts having
installed Xcode 7.3.1, but I didn't install the Command Line
Developer Tools. I thought it was included but apparently it
isn't.
I realized during a port installation
..@gmail.com
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
ts.org for a short
> time. This would include selfupdating or syncing MacPorts, downloading binary
> archives or distfiles from our network of mirror servers, accessing our web
> sites and source code repository, and sending email to our forwarding
> addresses.
>
> DNS cha
I'm switching macports.org to a new DNS provider momentarily.
Hopefully this will not result in an interruption of service, but it's possible
you'll be unable to access the services on macports.org for a short time. This
would include selfupdating or syncing MacPorts, downloading binary
supporting the 2 versions.
R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
> On Sep 3, 2016, at 11:49 AM, René J.V. Bertin <rjvber...@gmail.com> wrote:
>
> On Saturday September 03 2016 10:57:24 Ryan Schmidt wrote:
>
>> You mustn't change the version in a variant, because MacPorts decides when a
>> port is outdated based on what's in th
On Saturday September 03 2016 10:57:24 Ryan Schmidt wrote:
>You mustn't change the version in a variant, because MacPorts decides when a
>port is outdated based on what's in the portindex, and the portindex only
>includes one entry for each port, and the version recorded in the
sion provided by their dependents should be irrelevant to them. OTOH, it's
> easier to provide 2 (or more) different versions via variants because that
> allows ports to use the simplest depends_* declarations if they don't care
> about version, while those that do can exclude the u
pment it seems quite
likely that it (or even 5.9) will be released before the 5.6LTS EOL.
R.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
, using a variant to provide it is not an option. A variant shall
not change the version field.
You mentioned support for older OS. What is the minimum OS version for 5.7, vs
5.6?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
dependency declarations in the PortGroup have
already prepared the way for supporting different versions rather than
different build flavours through a single mechanism to declare dependencies on
Qt.
R.
___
macports-users mailing list
macports-users
e dialog asking me if I wanted to install command
>> line tools. Does it come up with a "clean" install of XCode / Mac OS X?
>
> I think Apple added that in Lion.
>
>
___
macports-users mailing list
macports-users@lists.ma
ink Apple added that in Lion.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
port: can't read "build.cmd": Failed to locate 'make' in
>> path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at
>> its MacPorts configuration time location, did you move it?
>>
>> You forgot to install the command line tools.
>
> ...
de 4 on there (still don't understand how
> unless there was a brief window before they made it pay only...)
I think that must have been the case. You're not the first person I've heard
say that. ___
macports-users mailing list
macports-users@lis
llbery kf8nh sine nomine associates
allber...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
___
macports-users mailing list
ma
installer.
>
> Hm, I recall them being installable via the download pane in Preferences
> back then (I stayed with SL quite a while).
That change came in Xcode 4.
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-users
ayed with SL quite a while).
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com ballb...@sinenomine.net
unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net
__
l/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at
>> its MacPorts configuration time location, did you move it?
>
> You forgot to install the command line tools.
...which, back in the Snow Leopard days, were not separate from Xcode. Rerun
the Xcode installer.
On Wed, Aug 24, 2016 at 9:55 PM, [ftp83plus] <ges...@ftp83plus.net> wrote:
> Unable to open port: can't read "build.cmd": Failed to locate 'make' in
> path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or
> at its MacPorts configuration time locatio
now works and nothing's missing, but I got one issue with "port
upgrade outdated" command: it outputs
Unable to open port: can't read "build.cmd": Failed to locate 'make' in path:
'/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at its
MacPorts configuration time lo
1 - 100 of 4529 matches
Mail list logo
