Summary: | dev-lisp/sbcl-1.0.31(?) fails to build cause of inaccessible syslog(/dev/log) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Diego Elio Pettenò (RETIRED) <flameeyes> |
Component: | New packages | Assignee: | Common Lisp Bugs <common-lisp> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | pva |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build log (bzip2)
build.log |
Description
Diego Elio Pettenò (RETIRED)
![]() Created attachment 210974 [details]
Build log (bzip2)
One test fails because of ECONNREFUSED when connecting to /dev/log. I think that the problem lay in the tinderbox configuration, not in SBCL. Well, it really shouldn't fail to *build* if the syslog is inaccessible, should it? Upstream policy is that contrib tests are always run and build fails if they don't all pass And Gentoo policy states that tests should be separated and build shouldn't fail if syslog is not working… As a workaround for this issue I removed /dev/log from the build host. I think since it builds successfully without /dev/log it's safe to drop this exact test, or at least make failure non fatal. (In reply to comment #6) > As a workaround for this issue I removed /dev/log from the build host. I think > since it builds successfully without /dev/log it's safe to drop this exact > test, or at least make failure non fatal. > i got the same problem and i have removed /dev/log but nothing changed what should i do? Created attachment 211863 [details]
build.log
@Bronsa: Your build fails because of a different error: unhandled SIMPLE-ERROR in thread #<SB-THREAD:THREAD "initial thread" RUNNING {1002A030A1}>: couldn't fork child process: Cannot allocate memory You seem to be running out of virtual memory and I have the impression that it's because you're using tmpfs on /var/tmp/portage. Try to disable tmpfs and recompile If you can still reproduce with current stable, 1.0.55-r1, bug 326217, please reopen the bug. |