I've got a branch locally where I fix several build warnings in gcc, g++, and icc. I'm hoping that some of these fixes will get things progressing again on OSX. I will try to push my changes tonight.
As to the test failures, it probably does have something to do with rigid text-matching in some tests. We'll have to see whether we can fix the formatting to exactly match what the tests expect. --Andrew Whitworth On Mon, Dec 13, 2010 at 8:05 AM, Dichi <[email protected]> wrote: > Thanks kid51++ for that report. > > Looking at it briefly it looks like the failures are related either to the > *wording* of some error messages or the exe's ( parrot, ... ) exiting > without an error exit code. I'll try to fix them in the course of this week. > > Said that, I'm more concerned of Parrot not building in OSX. Will, since I > don't have access to any OSX HW can you send me the full output of "make" so > I can see what's going on? > > Thanks. > > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
