One obstacle to fixing these problems properly is that handling of library
search paths is not centralized, but it really should be. A Pharo package
for sqlite or cairo or whatever should provide only the library name; UFFI
or some associated package should deal with the search for it. Otherwise
On October 1, 2017 12:33:04 AM GMT+02:00, "p...@highoctane.be"
wrote:
>Usually there are a number of names to try but on Linux, there are less
>users and more distros, so people are not adding more libs to try.
>
>So, yes, symlink in the plugin directory works usually.
>
Usually there are a number of names to try but on Linux, there are less
users and more distros, so people are not adding more libs to try.
So, yes, symlink in the plugin directory works usually.
Alternative would be to use LD_LIBRARY_PATH or pkg_config support to do
this cleanly (not done at
Dan Wilczak wrote:
Hernan -
I haven't opened an issue - how do I do it? (I'm very new to Pharo.)
About continuing the search - I only mean continuing the search of the
LD_LIBRARY_PATH directories, not the whole filesystem. Two changes would be
needed to accomplish this:
FWIW, I had problem
Stephane Ducasse wrote:
Would you pls care to look at the sibling thread "How to make pharo find
SQLite", it seems that it struggles with similar problem, is it supposed
to created symlinks on linux, or it should be able to fund the library
but somehow fails?
Thanks, Herby
https://pharo.fogbugz.com
On Sat, Sep 30, 2017 at 6:53 PM, Dan Wilczak wrote:
> Hernan -
>
> I haven't opened an issue - how do I do it? (I'm very new to Pharo.)
>
> About continuing the search - I only mean continuing the search of the
> LD_LIBRARY_PATH directories, not
Hernan -
I haven't opened an issue - how do I do it? (I'm very new to Pharo.)
About continuing the search - I only mean continuing the search of the
LD_LIBRARY_PATH directories, not the whole filesystem. Two changes would be
needed to accomplish this:
1) Athens-Cairo >> CairoLibrary would have
Hi Dan
2017-09-23 13:24 GMT-03:00 Dan Wilczak :
> It does search on LD_LIBRARY_PATH now, it just fails because it finds the
> 32-bit libcairo before the 64-bit one.
>
> The traceback displayed inside Pharo says "Error: External module not found"
> which is quite
It does search on LD_LIBRARY_PATH now, it just fails because it finds the
32-bit libcairo before the 64-bit one.
The traceback displayed inside Pharo says "Error: External module not
found" which is quite misleading. A minimal fix would be to just provide a
better error message.
There is a
What about shipping the dedicated libcairo with the Linux Virtual Image?
Hilaire
Le 23/09/2017 à 10:03, Esteban Lorenzano a écrit :
hi,
this is not a bug, UFFI cannot know where a library is (because it can be
anywhere).
but, not being a bug, this remains a problem:)
One solution is to
hi,
this is not a bug, UFFI cannot know where a library is (because it can be
anywhere).
but, not being a bug, this remains a problem :)
One solution is to search on LD_LIBRARY_PATH but this is not generalised (it
should) for the moment. And of course, this is a solution that works for linux
Can you open a bug entry and propose your solution?
Stef
On Fri, Sep 22, 2017 at 9:56 PM, Dan Wilczak wrote:
> That pointed me in the right direction, thanks. I've got it working now.
>
> I think there's a bug there which may bite other people ---
>
> If you have both
That pointed me in the right direction, thanks. I've got it working now.
I think there's a bug there which may bite other people ---
If you have both 32-bit and 64-bit versions of the library installed,
Unix64ModuleName can find the
32-bit version first (depending on your LD_LIBRARY_PATH) and
Hi dan
We are sorry that you encounter a problem.
Not sure that this is the solution but check
ffiLibraryName
^ CairoLibrary
CairoLibrary >> unix32ModuleName
"On different flavors of linux the path to library may differ
depending on OS distro or whether system is 32 or 64 bit.
Packages such
I've just installed the 64-bit version of Pharo 6.1 on OpenSuse linux (64
bit). The Athens demos fail because
UFFI looks for libcairo in /usr/lib rather the /usr/lib64. I tried setting
LD_LIBRARY_PATH but that has no effect.
How can I force it to use lib64?
Dan
--
Sent from:
15 matches
Mail list logo