On Jan 16, 2013, at 21:44, Ryan Schmidt wrote:
>
> On Jan 16, 2013, at 22:06, Jeremy Huddleston Sequoia wrote:
>
>> We may need to figure out a way to deal with this ABI compatibility issue in
>> base … is there currently a way to query what configure.compiler was for
>> another installed po
On Jan 16, 2013, at 22:06, Jeremy Huddleston Sequoia wrote:
> We may need to figure out a way to deal with this ABI compatibility issue in
> base … is there currently a way to query what configure.compiler was for
> another installed port?
I don't think that information is recorded anywhere; I
On Wed, Jan 16, 2013 at 10:06 PM, Jeremy Huddleston Sequoia
wrote:
>
> On Jan 16, 2013, at 19:44, Sean Farley wrote:
I personally have had clang++ bugs with libmesh, moose, armadillo, and
dolfin.
>>>
>>> There are plenty of g++ bugs as well ;) … have you filed radars (or at
>>> least l
On Wed, Jan 16, 2013 at 9:32 PM, Ryan Schmidt wrote:
>
> On Jan 16, 2013, at 19:49, Sean Farley wrote:
>
>> On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia wrote:
>>>
>>> That being said, is there something wrong with clang++ that is causing you
>>> to try g++ instead?
>>
>> Jeremy, pl
On Jan 16, 2013, at 19:44, Sean Farley wrote:
>>> I personally have had clang++ bugs with libmesh, moose, armadillo, and
>>> dolfin.
>>
>> There are plenty of g++ bugs as well ;) … have you filed radars (or at least
>> llvm bugzilla reports) about all of the clang issues you are finding? Can
On Wed, Jan 16, 2013 at 9:19 PM, Jeremy Huddleston Sequoia
wrote:
>
> On Jan 16, 2013, at 17:49, Sean Farley wrote:
>
>> On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia
>> wrote:
>>>
>>> On Jan 15, 2013, at 8:52 AM, Sean Farley wrote:
>>>
On Mon, Jan 14, 2013 at 8:32 AM, David B
On Jan 16, 2013, at 19:49, Sean Farley wrote:
> On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia wrote:
>>
>> That being said, is there something wrong with clang++ that is causing you
>> to try g++ instead?
>
> Jeremy, please understand that this is a frustrating position / stance
>
On Jan 16, 2013, at 17:49, Sean Farley wrote:
> On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia
> wrote:
>>
>> On Jan 15, 2013, at 8:52 AM, Sean Farley wrote:
>>
>>> On Mon, Jan 14, 2013 at 8:32 AM, David Barto wrote:
fails because the /usr/lib/libstdc++.so is found first. W
On Wed, Jan 16, 2013 at 7:16 PM, Jeremy Huddleston Sequoia
wrote:
>
> On Jan 15, 2013, at 8:52 AM, Sean Farley wrote:
>
>> On Mon, Jan 14, 2013 at 8:32 AM, David Barto wrote:
>>> fails because the /usr/lib/libstdc++.so is found first. What can I do to
>>> find the proper /opt/local/lib/libstdc++
On Jan 16, 2013, at 16:51, Lenore Horner wrote:
> There's a ticket http://trac.macports.org/ticket/36940 about patching povray
> so it compiles. It looks to me like the patch attached to that ticket has
> never been committed because I'm still getting the same error.
I'm not comfortable commi
There's a ticket http://trac.macports.org/ticket/36940 about patching povray so
it compiles. It looks to me like the patch attached to that ticket has never
been committed because I'm still getting the same error.
Thanks,
Lenore
___
macports-users ma
On Wed, Jan 16, 2013 at 3:21 AM, Jamie Paul Griffin wrote:
> I installed mutt devel myself into /usr/local, rather than using
> Macports, I don't recall the reasons why; I haven't experienced any
> problems so far but is it likely, then, that I will?
>
I don't think very much requires mutt as a
> I can't reboot it.
> When I press on "shut down" an installation window opens up saying: "Your
> computer can't be shut down now, because software is being installed"- it
> refers to the MacPorts installation although I already closed it.
>
> when I force quit this window, it pops up again a
* Jerry [2013-01-15 00:29:31 -0700]:
>
> On Jan 15, 2013, at 12:13 AM, Ryan Schmidt wrote:
>
> >
> > On Jan 14, 2013, at 18:24, Jerry wrote:
> >
> >> On Jan 13, 2013, at 4:43 PM, Ryan Schmidt wrote:
> >>
> >>> On Jan 12, 2013, at 00:39, Jerry wrote:
> >>>
> Since /opt/local is seen bef
14 matches
Mail list logo