New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange Str/linker bug. #7761
Comments
Comment author: administrator
Looks like a libc change, indeed. On my Linux system, the libc header
|
Comment author: administrator Looks like a libc change. |
Comment author: administrator On Tue, Oct 29, 2002 at 02:58:01PM +0100, Xavier Leroy wrote:
Well, after a bit more looking, it happened when glibc 2.3.1 was So, i rebuilt ocaml, and the dependency is now libc6 (>= 2.3.1-1), so BTW, i noticed this already some time ago, but it didn't find a way to BTW2, do you have any idea about the not-dying thread issue i reported BTW3, i plan to move the ocaml libdir from /usr/lib/ocaml to Friendly, Sven Luther |
Original bug ID: 1450
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)
Bug description
Hello, ...
This is a strange problem i got with the debian package.
==============================
aurora:~$ ocamlopt str.cmxa stuff.ml
/usr/lib/ocaml/libasmrun.a(str.o)(.text+0x1de): In function
is_printable': : undefined reference to
__ctype_b'collect2: ld returned 1 exit status
Error during linking
stuff.ml is an empty file.
This does not occur when I build the distribution from source by hand,
Debian or upstream. I can actually copy the libasmrun.a file from the
compiled source tree into /usr/lib/ocaml and the build will succeed:
aurora:/usr/src/ocaml/ocaml-3.06/asmrun# cp libasmrun* /usr/lib/ocaml
aurora:
$ ocamlopt str.cmxa stuff.ml$aurora:
This is, in addition to the first time I've seen the error, the first
time I've used Str. Learning the language :)
Well, it is solved by just rebuilding the package, so that is what i
will do. I guess it may be linked with the fact that we changed libc or
something like that between the time the ocaml package was built and the
time it was used.
Still it seems strange to me, and so i think it may be interresting for
you to know. Also if you have any hint as to the reason of this problem,
i am interrested.
Friendly,
Svne Luther
The text was updated successfully, but these errors were encountered: