Summary: | sci-mathematics/maxima-5.34.1 : Makefile:1198: recipe for target 'binary-sbcl/maxima.core' failed | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Gentoo Science Mathematics related packages <sci-mathematics> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
emerge-history.txt
environment sci-mathematics:maxima-5.34.1:20160517-131123.log |
Description
Toralf Förster
2016-05-17 13:20:07 UTC
Created attachment 434526 [details]
emerge-history.txt
Created attachment 434528 [details]
environment
Created attachment 434530 [details]
sci-mathematics:maxima-5.34.1:20160517-131123.log
It is rather a hardened issue,. But weither in grsec.log nor in pax.log are any entries. Here're the ulimit settings : tinderbox@ms-magpie ~ $ sudo chroot amd64-plasma-stable_20160509-225728/ ms-magpie / # ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 62848 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size (512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 62848 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited ms-magpie / # exit exit This is something specific to hardened. I cannot confirm (or test) it. Generally, hardened does not mix well with lisp systems, there were many examples in the past. And this is one of the reasons I don't use hardened. Also, from emerge-history.txt I guess you use sbcl-1.1.18, it is years old. Why not something reasonable, like sbcl-1.3.x? I hope sbcl-1.3.0 will be stabilize really soon now, and we'll be able to finally forget about sbcl-1.1.x. Maybe, 1.3.x behaves better with hardened? I cannot do anything with this bug. Would it makes sense to have an appropriate tracker then ? Even if bugs can't be solved it might be useful to avoid reporting dups IMO. Or - even more - to collect them in caser, that in future a generalized fix is available ? This looks like the same failure as bug 586146. Closing for the same reason: we'll never be able to reproduce it without grsec/pax available. *** This bug has been marked as a duplicate of bug 586146 *** |