What are the possibilities or difficulties of an fpc for AIX port?

=====
-------------------------------------------
Quinn P. Coldiron

__________________________________________________ Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/

Quinn Coldiron wrote

What are the possibilities or difficulties of an fpc for AIX port?

The main difficulty is the PowerPC code generator. I'm currently working on converting as much of the 1.1 code generator to processor independent stuff (which will not mean it will become slower, on the contrary it may even improve the speed of the generated code over time) and after that's done I can really start with the PowerPC port... But I've been saying this already for a long time, so it will probably still take a while.

On the positive side, I've already written most PowerPC support routines for the RTL (string handling, set handling, general procedures such as move and index*). Most aren't tested yet though, so if some people could do that it would help a lot. You can get them by downloading the 1.1 RTL sources from <ftp://ftp.freepascal.org/pub/fpc/source/rtl.zip> and by looking in the powerpc subdirectory.

Jonas

Hi there!

I tried some somple sockets and mysql programs on Windows 95 and Windows 98, using fpc-1.0.4. They work great on Linux, but not on Windows.

The sockets program gets garbage from the socket, although when run from inside gdbpasw it gets the correct data. The mysql program aborts on error 103 (file not open) at any writeln procedure call after the connection is estabilished. Again, if I run under gdbpasw I can see it gets the correct data from mysql, but this time it aborts also under gdbpasw.

Any hint? It's a problem with the OS or should I try a 1.1 shapshopt?

The programs are attached so you can test them. leweb1.pas is the sockets program and testdb.pas is the mysql one.

PS: Any hope to get 1.0.6 fixing these and other problems?

[]s, Fernando Lozano

Try downloading newer packages. This is an error in the Mysql headers which has been fixed meanwhile. When 1.0.6 is released this problem will be solved for all.

Michael.

Michael,

Wasn't the problem on the Windows version of the mysql unit related just to requiring liibc and libm? Does the problem affect also the sockets unit? As reported on the same message, but the problems are unrelated...

[]s, Fernando Lozano

Hi,

I can say only something to your MySQL problem - there can be 2 reasons (IMHO)
- incompatible (defferent) versions of libmysql.dll and your mysql.pas
- wrong function calling convention in mysql.pas

for the 1st problem check yourself whether you have correct versions of client lib / pascal interface
the 2nd problem - on win32 platform functions must be declared as stdcall instead of cdecl on linux platform

Mirek Novak

Mirek Novak wrote

Hi, I can say only something to your MySQL problem - there can be 2 reasons (IMHO) - incompatible (defferent) versions of libmysql.dll and your mysql.pas

This could be a possible cause. What client library version is being used ?

The latest mysql versions have the correct calling conventions, which is why I proposed to use the latest sources.

Michael.