> > > Or is there something wrong with my environment I haven't figured > > > out? > > > > Do you know what is the logic in the dynamic library file name > > numbering in FreeBSD? > > No, not precisely. The handbook > (http://www.freebsd.org/doc/en/books/developers-handbook/policies-shlib.html) > says that only the form libfoo.so.X.Y is supposed to be used > (major.minor) and the ELF linker doesn't handle the minor number. >
Indeed, but seems X and Y mean different things on GNU and BSD :) I fixed the pocl.icd contents in https://github.com/pocl/pocl/commit/9f0f106dd9db48819501e13796553248cfef6253 to conform to what seemed to be the consensus on the 'net. The best explanation (and I hope the correct one) I found was this: http://en.opensuse.org/openSUSE%3aShared_library_packaging_policy#Versioning_schemes So libpocl.so.3 seems to be correct, on BSD. Unfortunately, I didn't get pocl to work :/ It blocks in pthread_create on a mutex. Since Oliver already reported pocl to work on BSD, I blame this failure on my BSD usage skills: I must have goofed somewhere (this was my first time setting up a FreeBSD). Also, this was FreeBSD 9.2, not 11. Oliver, would you please try it out on 11 too, and report. Thanks. kalle ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ pocl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pocl-devel
