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 <[email protected]> wrote: > >>> On Jun 29, 2014, at 0:55, [email protected] 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. >>> >>> <libffi_failed.log> >>> >>> >>> Can someone explain why it is failing, if it's a bug or a misconfiguration? >>> I already used "clean" on libffi as was told back in 2012, yielding the >>> same result. >> >> Known bug. See our issue tracker. No solution known yet. Unknown if upstream >> is aware of the problem. > > I’ve informed the developers. > > Marius > -- > Marius Schamschula > > > _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
