Subject | Re: [firebird-support] FreeUDFLibC |
---|---|
Author | Helen Borrie |
Post date | 2005-02-08T02:53:54Z |
At 01:25 PM 8/02/2005 +1100, you wrote:
ported database still referring to 'FreeUDFLib'? Actually, for
consistency, the Win and Linux libs should have the same main "filename
stub", viz. freeudflib.dll on Windows freeudflib.so on Linux, so you won't
have to drop and redeclare functions when you transport the database.
./hb
>I need to get the FreeUDFLibC working on linux so my DBs can switch overFile name case sensitivity on Linux? Or some database declarations in the
>from windows when I need them to.
>The library "makes" without an extension (no .so) and by default, the make
>file wants to put the file in /lib instead of UDF. I have tried giving it
>.so and also placing it in UDF. I have also ensured the UDFs have All access
>for the moment and that permission are 555 as are the other udf libs.
>Now is there something I need to know about this make?
>Is it static instead of dynamic or something?
>Bottom line is that I can create (declare) the UDFs in employee.fdb OK but I
>get a BLR error when I try to use them. (module name or entrypoint could not
>be found.)
>The declarations are like this:
>declare external function f_mid
> cstring(256), integer, integer
> returns cstring(256) free_it
> entry_point 'mid' module_name 'FreeUDFLibC';
>So what could be no mamthed up
ported database still referring to 'FreeUDFLib'? Actually, for
consistency, the Win and Linux libs should have the same main "filename
stub", viz. freeudflib.dll on Windows freeudflib.so on Linux, so you won't
have to drop and redeclare functions when you transport the database.
./hb