I installed Mavericks just a few days ago because Xcode 6.0.1 requires
it. I installed Xcode 6.0.1 because I need to know how to work with
it, as well as to develop for iOS, just to get a job as an iOS App
developer.
I don't have a problem with learning to use the latest tools. What I
don't unde
On Sat, 11 Oct 2014, C.T. wrote:
> I quite agree with you Mike on this one. My main machine is still Snow
> Leopard, and while I am not a developper, I just couldn’t replicate the
> perfect balance it struck between user-friendliness and underlying power
> and compatibility.
I went to Maverick
I quite agree with you Mike on this one. My main machine is still Snow Leopard,
and while I am not a developper, I just couldn’t replicate the perfect balance
it struck between user-friendliness and underlying power and compatibility.
> El 10/10/2014, a las 22:18, Michael Crawford escribió:
>
On Oct 11, 2014, at 12:57 AM, Michael Crawford wrote:
> My plan is to upgrade her to 10.5.x - is that Leopard?
Yes.
> Does 10.6 run on a G4 iMac?
No. Snow Leopard requires Intel hardware.
http://support.apple.com/kb/SP575
vq
___
macports-users mail
I found quite a serious security problem on Mom's Tiger G4 iMac,
something I cannot fix myself because I can't get the source and Apple
hasn't updated Tiger in years.
My memory is hazy but I think it was a problem in Safari. I will look
it up I posted it online somewhere.
My plan is to upgrade h
Hello users,
Effective immediately, the MacPorts Project is deprecating Python 2.4, 2.5,
2.6, 3.1, 3.2, and 3.3, due to cessation of upstream support.
Ports using these series will be migrated to Python 2.7 or 3.4 as appropriate.
New ports will only use 2.7 and 3.4 (and 3.5, when it is released
On Oct 10, 2014, at 10:59 PM, Dave Horsfall wrote:
> Which brings me to security in general (and I'm a security freak). Are
> the fixes for Mavericks also available for Snow Leopard?
No. Snow Leopard no longer receives updates of any sort, and Lion will likely
follow as soon as Yosemite drops
Hi Michael,
On 11/10/2014, at 1:18 PM, Michael Crawford wrote:
> (On the thread about the bash function problem, someone asked why the
> fellow runs such an old version of OS X.)
>
> I myself generally delay upgrading the system software on any platform
> I am developing for, so as to ensure that
On Fri, 10 Oct 2014, Michael Crawford wrote:
> (On the thread about the bash function problem, someone asked why the
> fellow runs such an old version of OS X.)
Ah, that someone would be me :-)
> I myself generally delay upgrading the system software on any platform I
> am developing for, so a
(On the thread about the bash function problem, someone asked why the
fellow runs such an old version of OS X.)
I myself generally delay upgrading the system software on any platform
I am developing for, so as to ensure that the code I write runs well
on old systems.
This so I won't be requiring
On Fri, Oct 10, 2014 at 6:45 PM, Greg Earle wrote:
> Personally I wouldn't replace Apple's bash/sh with MacPorts' versions.
I did suggest building it himself first, with copying MacPorts' bash as a
fallback. I even provided a caveat as to why it might not be a good idea.
--
brandon s allbery
On Oct 10, 2014, at 11:49 AM, Sean Farley wrote:
>
> Daniel Watkins writes:
>
>> I attempted to install petsc using the command
>> sudo port install petsc +mpich +superlu +suitesparse
>> and was unsuccessful. The log file is attached.
>
> Ouch. This appears to be a compiler bug with clang. What
On Oct 10, 2014, at 6:06 PM, René J.V. Bertin wrote:
> On Saturday October 11 2014 00:43:19 Clemens Lang wrote:
>
>>> Is there a reason for this omission?
>>
>> Yes:
>>
>> Consider ports A -> B -> C -> D, where -> is "depends on".
>>
>> A has no variants, B has +foo, C has +bar and D has +baz
On Saturday October 11 2014 00:43:19 Clemens Lang wrote:
> > Is there a reason for this omission?
>
> Yes:
>
> Consider ports A -> B -> C -> D, where -> is "depends on".
>
> A has no variants, B has +foo, C has +bar and D has +baz
Yes, I see. But that situation could also have been addressed b
On Oct 10, 2014, at 16:06 PM, Barrie Stott wrote:
> On 10 Oct 2014, at 15:27, Brandon Allbery wrote:
>
>> That said, 10.6 being unsupported by Apple, it is possible that your best
>> bet is to copy /bin/bash to /bin/bash.apple and then copy MacPorts' bash to
>> /bin/bash. (But beware, if you r
Hi,
- On 10 Oct, 2014, at 23:01, René J.V. Bertin rjvber...@gmail.com wrote:
> Is there a reason for this omission?
Yes:
Consider ports A -> B -> C -> D, where -> is "depends on".
A has no variants, B has +foo, C has +bar and D has +baz
sudo port install A +foo +bar +baz will install
A
Hello,
I just discovered that installing a port with a +unexisting variant goes
through without as much as a warning. A bit annoying if the install involves a
lengthy build process and you don't notice that typo until some expected
functionality proves to be absent ...
Is there a reason for th
Daniel Watkins writes:
> I attempted to install petsc using the command
> sudo port install petsc +mpich +superlu +suitesparse
> and was unsuccessful. The log file is attached.
Ouch. This appears to be a compiler bug with clang. What OS and version
of Xcode are you running?
_
René,
No, I did a selfupdate late yesterday and upgraded all. That is, if I used the
patch, it had already been committed to the port file. I'm a very superficial
user of KDE - primarily for KMyMoney.
Stan
> On Oct 10, 2014, at 4:00 AM, René J.V. Bertin wrote:
>
>> On Thursday October 09 20
I attempted to install petsc using the commandsudo port install petsc +mpich +superlu +suitesparseand was unsuccessful. The log file is attached.
main.log
Description: Binary data
___
macports-users mailing list
macports-users@lists.macosforge.org
https:
On Fri, Oct 10, 2014 at 11:06 AM, Barrie Stott wrote:
> I've done that and I've doe something similar with /bin/sh as well.
> Surprisingly, I found original /bin/bash and /bin/sh different. The new
> stuff is:
> -rwxr-xr-x 1 root wheel 1893232 10 Oct 15:43 /bin/bash
> -rwxr-xr-x 1 root wheel
On 10 Oct 2014, at 15:27, Brandon Allbery wrote:
> That said, 10.6 being unsupported by Apple, it is possible that your best bet
> is to copy /bin/bash to /bin/bash.apple and then copy MacPorts' bash to
> /bin/bash. (But beware, if you remove MacPorts in the future your /bin/bash
> will break;
On Fri, Oct 10, 2014 at 10:07 AM, Barrie Stott wrote:
>
> Where is this Debian/FreeBSD patch? What is it patching? Are there
> instructions for its use?
>
https://svnweb.freebsd.org/ports/head/shells/bash/files/extrapatch-import-functions?revision=369467&view=markup
It's a patch to bash to only i
On 10 Oct 2014, at 13:48, Brandon Allbery wrote:
> On Fri, Oct 10, 2014 at 6:13 AM, Barrie Stott wrote:
> Wouldn't the stopping of function export from MacPorts' bash be a big
> restriction on bash use. For example, I want to be able to type "mvim", with
> or without parameters, to open a MacV
On 10 Oct 2014, at 12:19, Mathias Laurin wrote:
>> Wouldn't the stopping of function export from MacPorts' bash be a big
>> restriction on bash use. For example, I want to be able to type "mvim", with
>> or without parameters, to open a MacVim window. At present, I get the error:
>> "/bin/sh: l
On Fri, Oct 10, 2014 at 7:19 AM, Mathias Laurin
wrote:
> #!/usr/bin/env -i /bin/sh
I expect MacVim would behave very poorly without $HOME and possibly $SHELL
set. Probably others as well.
--
brandon s allbery kf8nh sine nomine associates
allber...@gmail.com
On Fri, Oct 10, 2014 at 6:13 AM, Barrie Stott wrote:
> Wouldn't the stopping of function export from MacPorts' bash be a big
> restriction on bash use. For example, I want to be able to type "mvim",
> with or without parameters, to open a MacVim window. At present, I get the
> error:
> "/bin/sh:
> Wouldn't the stopping of function export from MacPorts' bash be a big
> restriction on bash use. For example, I want to be able to type "mvim", with
> or without parameters, to open a MacVim window. At present, I get the error:
> "/bin/sh: line 8: `BASH_FUNC_usenosql%%': not a valid identifier"
Hello,
It happens rather regularly that I want do a project's configure (or cmake)
step without using `port configure`, for various reasons, including not wanting
to have to rebuild a large port entirely.
The ideal thing would be to have a command (along the lines of port-whatsnew)
that prints
On 9 Oct 2014, at 23:27, Jeremy Lavergne wrote:
> Off the top of my head:
> * Rosetta (for PPC)
> * Apple Mail in Mavericks cannot do any searching without spotlight (among
> other bugs)
> * Mavericks Messages keeps records of every chat you’ve had, the option to
> explicitly “close” can cause
30 matches
Mail list logo
