Same ticket is fine. I'll take a look at it.
> On Oct 16, 2014, at 9:35 PM, Mark Anderson wrote:
>
> I have a patch in this ticket to upgrade iTerm2 to v 2.0 - Should we change
> the name of the ticket or start a new one?
>
> —Mark
> ___
> Mark E. Anderson
>
> On Sun, Oc
On Oct 16, 2014, at 2:19 PM, Lawrence Velázquez wrote:
> Pretty sure this has to be grouped with quotation marks or braces. As it is,
> base will blacklist any compilers matching the patterns "llvm-gcc-4.2", "=",
> and "2336.1.00". Needless to say, there are no compilers matching the latter
> t
I have a patch in this ticket to upgrade iTerm2 to v 2.0 - Should we change
the name of the ticket or start a new one?
—Mark
___
Mark E. Anderson
On Sun, Oct 5, 2014 at 11:32 PM, MacPorts wrote:
> #43311: iTerm2: update to 1.0.0.20140403
> -+
Pretty sure this has to be grouped with quotation marks or braces. As it is,
base will blacklist any compilers matching the patterns "llvm-gcc-4.2", "=",
and "2336.1.00". Needless to say, there are no compilers matching the latter
two patterns.
vq
On Oct 16, 2014, at 1:14 PM, davidnich...@macp
On 2014-10-17 05:16 , Ryan Schmidt wrote:
>
> On Oct 16, 2014, at 12:50 PM, Joshua Root wrote:
>>
>> So Yosemite is out today. Might as well tag a new release before I build
>> the pkg. Is there anything critical that needs to go onto the branch first?
>
> Could we update the checks in configure.
On Oct 16, 2014, at 12:50 PM, Joshua Root wrote:
>
> So Yosemite is out today. Might as well tag a new release before I build
> the pkg. Is there anything critical that needs to go onto the branch first?
Could we update the checks in configure.ac that test for outdated OS X and
Xcode versions?
So Yosemite is out today. Might as well tag a new release before I build
the pkg. Is there anything critical that needs to go onto the branch first?
- Josh
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailm
At 6:12 PM +0200 10/16/14, Rainer Müller wrote:
On 2014-10-16 17:30, Craig Treleaven wrote:
I'm working on a new version of MythTV and building in a non-standard
prefix (/opt/dvr). I'm getting hundreds of warning messages like the
following:
2014-10-16 10:43:03.178 osacompile[23932:90b] C
> On Oct 16, 2014, at 11:29 AM, Ryan Schmidt wrote:
>
>> On Oct 16, 2014, at 9:24 AM, davidnich...@macports.org wrote:
>>
>> Revision
>> 126852
>> Author
>> davidnich...@macports.org
>> Date
>> 2014-10-16 07:24:39 -0700 (Thu, 16 Oct 2014)
>> Log Message
>>
>> blacklisted the Xcode 4.2 compiler
> On Oct 16, 2014, at 9:24 AM, davidnich...@macports.org wrote:
>
> Revision
> 126852
> Author
> davidnich...@macports.org
> Date
> 2014-10-16 07:24:39 -0700 (Thu, 16 Oct 2014)
> Log Message
>
> blacklisted the Xcode 4.2 compiler so that the mpfr lib can be build with
> threading enabled and th
Hi,
- On 14 Oct, 2014, at 16:12, Daniel J. Luke dl...@geeklair.net wrote:
> We do have versionability in portgroups, it just hasn't been used much so far.
Just for the record, this isn't true. The active-variants PortGroup exists in
two
versions due to an API change.
On the issue at hand,
On Thu, Oct 16, 2014 at 12:12 PM, Rainer Müller wrote:
> $ dscl . -read /Users/macports NFSHomeDirectory
> NFSHomeDirectory: /opt/local/var/macports/home
>
Oh, blah. I hate it when programs without specific security needs use that
instead of $HOME
--
brandon s allbery kf8nh
On 2014-10-16 17:30, Craig Treleaven wrote:
> I'm working on a new version of MythTV and building in a non-standard
> prefix (/opt/dvr). I'm getting hundreds of warning messages like the
> following:
>
>> 2014-10-16 10:43:03.178 osacompile[23932:90b] CFPreferences: user home
>> directory at file:
On Thu, Oct 16, 2014 at 11:30 AM, Craig Treleaven
wrote:
> I'm working on a new version of MythTV and building in a non-standard
> prefix (/opt/dvr). I'm getting hundreds of warning messages like the
> following:
>
> 2014-10-16 10:43:03.178 osacompile[23932:90b] CFPreferences: user home
>> dire
Hi:
I'm working on a new version of MythTV and building in a non-standard
prefix (/opt/dvr). I'm getting hundreds of warning messages like the
following:
2014-10-16 10:43:03.178 osacompile[23932:90b] CFPreferences: user
home directory at file://localhost/opt/local/var/macports/home/ is
una
Hi,
- On 16 Oct, 2014, at 12:22, David Nichols davidnich...@macports.org wrote:
> This change was made three years ago in svn rev 90220 by c...@macports.org (on
> cc).
See http://trac.macports.org/ticket/33361 and
http://llvm.org/bugs/show_bug.cgi?id=1
for rationale. I was only the comm
Hi All,
Currently mpfr is compiled in a non-thread-safe manner due to a bug in Xcode
4.2 (according to comments in the Portfile):
> # Due to radr://10291355 (llvm.org PR1), the new tls support enabled in
> clang with Xcode 4.2
> # miscompiles mpfr. While this was fixed in Xcode 4.2.1, as th
17 matches
Mail list logo
