Kassen <[email protected]> writes: > Dear list, > > I build racket from source, using the command from the fluxus readme to make > sure it all ends up in > /usr/local where fluxus expects it. > I compiled fluxus and this went without a problem. > > Now running fluxus gives me > > fluxus: error while loading shared libraries: libracket3m-5.0.1.so: cannot > open shared object file: > No such file or directory > > that doesn't seem fair, because it could find it all just fine when scons > checked for it. Also; > > whereis libracket3m-5.0.1.so > libracket3m-5.0.1: /usr/local/lib/libracket3m-5.0.1.so > > Just to make sure I also copied the file to /usr/local/lib/racket That didn't > help. > > I manually (tried to...) clean all of the stuff left over from when I thought > the binary install of > racket would do, or that the "full" install would have the 3m stuff, after > that I re-build racket > to make sure. No luck. No news on why the "full" install doesn't simply have > the 3m stuff in it > either; it claims it has everything. > > Just now I reasoned that if fluxus can find it's libraries at compilation, > then loses track of > them, I could just build it in static mode and hope it includes the > libraries. This gets me; > > Checking for C++ function lo_arg_size_check()... (cached) yes > path->bytes: expects argument of type <path>; given "?" > > === context === > /usr/local/lib/racket/collects/compiler/embed-unit.rkt:893:60 > /usr/local/lib/racket/collects/racket/private/map.rkt:18:11: map > /usr/local/lib/racket/collects/racket/private/map.rkt:18:11: map > /usr/local/lib/racket/collects/compiler/embed-unit.rkt:776:4: > do-write-module-bundle > /usr/local/lib/racket/collects/compiler/commands/ctool.rkt: [running body] > /usr/local/lib/racket/collects/raco/raco.rkt: [running body] > /usr/local/lib/racket/collects/raco/main.rkt: [running body] > > ERROR: Failed to run command 'raco' > > I'm now out of ideas; I really do have libracket3m-5.0.1.so but fluxus can't > find it and I can't > figure out where fluxus is looking for it. > > This makes me a bit sad because I'm really getting into it all and wanted to > polish my error prints > with some of the suggestions I got. > So; now what? Is there some log that fluxus generates with errors or some > other way to figure out > where it looks for this library so I could simply put the file there? > > Thanks, > Kas. what does LD_LIBRARY_PATH points to? make it so /usr/local/lib i think is recognizable, alternatively you can install on /usr and give fluxus the approppriate flags at compile time. btw very nice work on error messages its pretty good.
cheers, glauber.
