Re: Should games/fifengine be marked as broken on sparc64?

Kaashif Hymabaccus writes:
> games/fifengine's Makefile has the line:
>
> > BROKEN-sparc64 =out of memory when compiling fifePYTHON_wrap.cxx
>
> Which was added in a commit with this message:
>
> > Don't try building fifengine on archs that will definitely run out
> > of memory.
>
> I can build it on my sparc64 box with no issue if I remove the
> BROKEN-*. I guess if it uses more than 4 GB of memory, 32 bit
> architectures can't possibly build it, so it being BROKEN on i386 is
> probably accurate.
>
> But there's nothing stopping someone with enough RAM from building
> this on sparc64, so why is it marked as BROKEN?

I believe you. But I mark such ports as broken when they consistently
fail to build in bulks. Maybe the bulk builder could succeed it with a
bit more memory, but as it is it currently wastes a lot of time on a
system that already takes a long long time to build packages.

http://build-failures.rhaalovely.net//sparc64/2017-11-12/games/fifengine.log
http://build-failures.rhaalovely.net//sparc64/2017-11-22/games/fifengine.log
http://build-failures.rhaalovely.net//sparc64/2017-12-03/games/fifengine.log
http://build-failures.rhaalovely.net//sparc64/2017-12-17/games/fifengine.log

--
Anthony J. Bentley