Created attachment 205911 [details] 12.0 poudriere build log In many of my recent poudriere builds, scilab has failed for a "runaway process" violation. The process in the configuration portion of the build that is causing this is testing arpack-ng compatibility... and runs with 8 or more threads (only one busy). I'm pretty sure I'm not geared to analyze this. I've attached the poudriere biuld log for 12.0, but I've encountered this on 11.2 and now recently 11.3. I've tried quadrupling my timeout... it doesn't give any evidence that it's working.
(In reply to dgilbert from comment #0) > Created attachment 205911 [details] > 12.0 poudriere build log > > In many of my recent poudriere builds, scilab has failed for a "runaway > process" violation. The process in the configuration portion of the build > that is causing this is testing arpack-ng compatibility... and runs with 8 > or more threads (only one busy). I'm pretty sure I'm not geared to analyze > this. Apparently test program loops forever. I see you build scilab with OPENBLAS option. Do you have the same problem with default set?
Should be solved with ports r508978.
I think I need to clarify? Are you asking me to rebuild scilab with all default options or rebuild it with whichever blas was the default? Which blas is the default again?
So... my result: it builds with entirely default options (but I assume you knew that) but it fails with my options. I'm attaching my options.
Created attachment 206648 [details] the options for math/scilab that lead to failure
after testing and rebuilding a number of times, I've narrowed down the cause of the failure. the 64 bit integer option of openblas causes the problem.
(In reply to dgilbert from comment #6) Do you mean INTERFACE64 option in math/openblas? Seems this is not a scilab bug, if it's really a bug at all. I'm closing the ticket, feel free to re-open, if you have an idea for improvement.