Closed hyln9 closed 10 years ago
I have not done a true review of the GC integrity check, it is entirely possible that I have introduced an error in such code; so let's leave it aside.
The first part of the bytevector that causes the error is:
(ascii->string '#vu8(108 105 98 99 114 101 50 46 115 111 46 48 58 32))
"libcre2.so.0: "
it looks like the portion of a system error message caused by problems loading libcre2 (an error returned by dlerror()
), but I failed to replicate it on my system; even when I remove the installed files libcre2.so*
and try to load (vicare cre2) the error message is displayed correctly.
Does everything else work? Is the package cre2 correctly installed? If you compile with "make -k" to let it skip errors as much as possible is cre2 the only library that causes problems? Are you running the latest checkout from the devel
branch? Is the latest release tarball failing with the same error?
Even though I am italian (locale it_IT
) I set british locale LANG=en_GB@euro
in my Bash profile; what is your language setting?
Thanks a lot firstly!
I'm really a newbie to scheme and linux, and very pleasantly surprised to get your help within 2 hours!
I'm Chinese, so I set it in Gnome Settings yesterday. Now I set English and remove gc integrity checks, and every thing goes well!
But there is still a small bug: "ln -s /usr/local/lib/libre2* /usr/lib" and "ln -s /usr/local/lib/libcre2* /usr/lib" need to be executed before make vicare with cre2.
PS:
1、During "make check", "tests/test-issue-058-lalr-unary-prec.sps" is "XFAIL" and "tests/test-vicare-posix-sockets.sps" failed while the other passed.
2、My computer runs on "Linux localhost.localdomain 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7 17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux" (Fedora 20)
Should I close this issue?
Fine. Not handling the character encoding associated to the selected locale is a genuine error in Vicare; I will decide what to do sometime in future. For now I will push a workaround on the devel
branch, by leaving the locale to the default C
which should guarantee that all error messages from the system are in ASCII encoding. With this workaround you should be free to select your preferred locale, with no problems from Vicare other than Vicare is not localised. I will close this issue and open a proper one for the encoding error.
Vicare uses of the GNU Autotools as packaging infrastructure; with it, it is possible to mark a test as "expected failure". If a test completes with status XFAIL
: it means that it has correctly failed; everything is fine.
You have a 64-bit computer; on such computer it is possible to install either a 32-bit distribution or a 64-bit distribution. If you have installed a 64-bit GNU+Linux distribution, usually the libraries are under the lib64
directory, not the lib
one. On my Slackware the libraries are in:
/usr/lib64
/usr/local/lib64
when building and installing both the packages Vicare Scheme and CRE2, you should configure the correct installation directory for libraries. If you take the latest checkout from the CRE2 repository, the script configure.sh
shows what I do for such configuration. After installation do not forget to run the command ldconfig
(with superuser privileges) to make sure the system can find the latest installed libraries.
Thanks a lot for your suggestions!
I'm so sorry for my poor English X﹏X
My computer runs on "Linux localhost.localdomain 3.13.6-200.fc20.x86_64 #1 SMP Fri Mar 7 17:02:28 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"
I use "../configure --enable-maintainer-mode --enable-sources-installation --enable-binfmt --with-pthread --with-libffi --with-libiconv --with-readline --with-cre2" to configure.
When I try to make, something bad happen as following:
When "--gc-integrity-checks" is enabled,
I don't know why, any suggestions much appreciated!