| Summary: | Clisp 2.33.2-r1 compile fails: Xlib connection refused in avcall's minitests | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | katerina <kllba> |
| Component: | Current packages | Assignee: | Gentoo Lisp Project <lisp> |
| Status: | RESOLVED NEEDINFO | ||
| Severity: | major | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
katerina
2004-09-18 00:10:18 UTC
Try performing the emerge while X is running on the machine so that the script can connect to X to run the tests. Let me know if that help. I originally ran the emerge from an xterm. I use X from a user account, and su to root. The error persists. Could it be that having "debug" in your USE set is causing this problem? That is the only difference between my configuration (which works) and yours. Could you try without debug in USE and let me know of the results? You also said you were "upgrading from 2.33.2". I assume this means from dev-lisp/clisp-2.33.2 to dev-lisp/clisp-2.33.2-r1. The -r1 includes a simlpe source compilation fix for the glibc module (see bug #57155) and also installs the Common Lisp Controller aspect of the CLISP port to use the ISO-8859-1 encoding by default. Neither of these seem like they would cause upgrade problems. Thus, can you think of any changes in your general/system-wide/portage configuration between now and when you first got dev-lisp-2.33.2 emerged. USE="-debug" emerge clisp Problem persists. 'You also said you were "upgrading from 2.33.2". I assume this means from dev-lisp/clisp-2.33.2 to dev-lisp/clisp-2.33.2-r1.' <-- That is correct. I've changed CFLAGS in the not-so-distant past, and I occasionally tweak USE flags. I've upgraded packages as new versions hit the x86 arch. Does the problem still persist with clisp-2.38-r2? |