On Jun 30, 2014, at 6:46 PM, semaphor...@yahoo.com wrote:
> I found this bug in the list, but it is happening on a fully 64-bit platform.
> I don't get it.
>
> What else could be causing this problem?
The developers of libffi have written code that is incompatible with your
system or compiler
I found this bug in the list, but it is happening on a fully 64-bit platform. I
don't get it.
What else could be causing this problem?
Pat
Le 29 juin 2014 à 17:17, Marius Schamschula a écrit :
>
> On Jun 29, 2014, at 4:13 PM, Ryan Schmidt wrote:
>
>>> On Jun 29, 2014, at 0:55, semaphor...@y
On Jun 29, 2014, at 4:13 PM, Ryan Schmidt wrote:
>> On Jun 29, 2014, at 0:55, semaphor...@yahoo.com wrote:
>>
>> I just tried to run
>>
>> $ sudo port upgrade outdated
>>
>> but soon after it started to compile it, it spit an error. Doing as it said,
>> I looked in the log, but found nothin
> On Jun 29, 2014, at 0:55, semaphor...@yahoo.com wrote:
>
> I just tried to run
>
> $ sudo port upgrade outdated
>
> but soon after it started to compile it, it spit an error. Doing as it said,
> I looked in the log, but found nothing I could understand.
>
> Here is the log.
>
>
>
>
> Ca
... When using gcc, at least. I have no problem building universal with clang
on Mavericks for example.
> On Jun 29, 2014, at 5:39, Marius Schamschula wrote:
>
> Pat,
>
> See https://trac.macports.org/ticket/44170
>
> It’s an issue with the 32 bit platform.
>
>> On Jun 29, 2014, at 12:55
Pat,
See https://trac.macports.org/ticket/44170
It’s an issue with the 32 bit platform.
On Jun 29, 2014, at 12:55 AM, semaphor...@yahoo.com wrote:
> Hello MP list,
>
> I just tried to run
>
> $ sudo port upgrade outdated
>
> but soon after it started to compile it, it spit an error. Doing
Hello MP list,
I just tried to run
$ sudo port upgrade outdated
but soon after it started to compile it, it spit an error. Doing as it said, I
looked in the log, but found nothing I could understand.
Here is the log.
libffi_failed.log
Description: Binary data
Can someone explain why it
