Re: [fpc-pascal] Error compile library on Linux.

2014-03-18 Thread Fred van Stappen
> but you will have to provide the source code required to reproduce > it and compilation instructions, otherwise there is nothing we can do (as > always).> Jonas Hum, ok (but you promise not to tell, it is still a secret...) ;-) The project-units : >> https://github.com/graemeg/fpGUI/tree/deve

Re: [fpc-pascal] Error compile library on Linux.

2014-03-18 Thread Jonas Maebe
On 18 Mar 2014, at 12:52, Fred van Stappen wrote: /usr/bin/ld: /home/fred/mylib/lib/x86_64-linux/thefile.o: réadressage de R_X86_64_32S en vertu de « .bss.n_u_$thefile_$$_usedfirstmessage » cannot be used when creation of shared object, recompile with -fPIC/ home>> >/fred/fmylib/lib/x86_

Re: [fpc-pascal] Error compile library on Linux.

2014-03-18 Thread Fred van Stappen
> /usr/bin/ld: /home/fred/mylib/lib/x86_64-linux/thefile.o: réadressage de > R_X86_64_32S en vertu de « .bss.n_u_$thefile_$$_usedfirstmessage » cannot > be used when creation of shared object, recompile with -fPIC/home>> > >/fred/fmylib/lib/x86_64-linux/thefile.o: error adding symbols: Bad value

Re: [fpc-pascal] TSQLQuery.ApplyUpdates problem with UTF-8

2014-03-18 Thread Dennis Poon
LacaK wrote: Dennis Poon wrote / napísal(a): Dennis Poon wrote: Michael Van Canneyt wrote: On Fri, 14 Mar 2014, Dennis Poon wrote: the content appeared as garbage. I already specified the CHARSET=utf8 in the Create Table SQL. Did you set the TSQLConnection.Charset property to UT

Re: [fpc-pascal] TSQLQuery.ApplyUpdates problem with UTF-8

2014-03-18 Thread LacaK
Dennis Poon wrote / napísal(a): Dennis Poon wrote: Michael Van Canneyt wrote: On Fri, 14 Mar 2014, Dennis Poon wrote: the content appeared as garbage. I already specified the CHARSET=utf8 in the Create Table SQL. Did you set the TSQLConnection.Charset property to UTF8 as well ?

Re: [fpc-pascal] TSQLQuery.ApplyUpdates problem with UTF-8

2014-03-18 Thread LacaK
Dennis Poon wrote / napísal(a): Dennis Poon wrote: Michael Van Canneyt wrote: On Fri, 14 Mar 2014, Dennis Poon wrote: the content appeared as garbage. I already specified the CHARSET=utf8 in the Create Table SQL. Did you set the TSQLConnection.Charset property to UTF8 as well ?