Bug 201659 - math/scilab port build fails
Summary: math/scilab port build fails
Status: Closed Feedback Timeout
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Many People
Assignee: Max Brazhnikov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-07-17 20:51 UTC by leventelist
Modified: 2016-10-25 15:06 UTC (History)
1 user (show)

See Also:

Attachments
console output (46.77 KB, text/plain)
2015-07-17 20:51 UTC, leventelist 		no flags Details
JVM error report (26.50 KB, text/x-log)
2015-07-23 16:27 UTC, leventelist 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description leventelist 2015-07-17 20:51:20 UTC 
Created attachment 158915 [details]
console output

math/scilab fails to build.

This is *NOT* related to #201339.

Attached is the console output.
Comment 1 Max Brazhnikov freebsd_committer freebsd_triage 2015-07-18 00:09:53 UTC 
(In reply to leventelist from comment #0)
> Created attachment 158915 [details]
> console output
> 
> math/scilab fails to build.
> 
> This is *NOT* related to #201339.
> 
> Attached is the console output.

Any chance you have libglesv2/libEGL packages?

Can you run scilab from the working directory with -disable-exception-catching option (e.g. ./bin/scilab-adv-cli -noatomsautoload -nouserstartup -disable-exception-catching) and see how far it goes?
Comment 2 leventelist 2015-07-23 16:27:45 UTC 
Created attachment 159115 [details]
JVM error report
Comment 3 leventelist 2015-07-23 16:29:56 UTC 
(In reply to Max Brazhnikov from comment #1)

No, I didn't fiddle with other package.

No, JVM fails. I attached /tmp/hs_err_pidxxx.log, and I paste here the console output.

leva@jive:/usr/ports/math/scilab/work/scilab-5.5.0$ ./bin/scilab-adv-cli -noatosautoload -nouserstartup -disable-exception-catching
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000082e400761, pid=1098, tid=34632393728
#
# JRE version: OpenJDK Runtime Environment (7.0-b15) (build 1.7.0_80-b15)
# Java VM: OpenJDK 64-Bit Server VM (24.80-b11 mixed mode bsd-amd64 compressed ops)
# Problematic frame:
# C  [libnvidia-tls.so.1+0x761]  _nv024tls+0x31
#
# Core dump written. Default location: /cores/core or core.1098
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1098.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
Abort trap
Comment 4 Ed Maste freebsd_committer freebsd_triage 2015-07-24 13:28:42 UTC 
The hardware is set to arm64, but I suspect this is an error and you meant amd64. Can you confirm and correct if so?
Comment 5 leventelist 2015-07-24 13:33:05 UTC 
Yes, this is on amd64. Sorry, my bad.

Lev
Comment 6 Max Brazhnikov freebsd_committer freebsd_triage 2015-07-31 10:50:45 UTC 
(In reply to leventelist from comment #3)
> # Problematic frame:
> # C  [libnvidia-tls.so.1+0x761]  _nv024tls+0x31

So the problem is with nvidia driver. To be sure you can run scilab-cli and it should work.