Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2007-05

Bringing back fpc 2.3.1 to BeOS

7 messages · 4 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Olivier Coursiere

Hi all,

After a long period of inactivity, i finally took the time to update the BeOS port of fpc. I have successfully compiled the latest trunk (revision 7420) under BeOS using a new libc based RTL (1.0.* versions were based on system calls).

The patch i propose to achieve this is in two parts :

- the first part is a zip file containing all files in the ../rtl/beos directory. As there is a lot of change in this directory, i think it does not make sense to produce a diff file. This file is available at http://olivier.coursiere.free.fr/diff/beos.zip.
- the second part is a diff file of all other changes made to compile fpc under BeOS (based on revision 7420). This file is available at http://olivier.coursiere.free.fr/diff/beos.diff. Most of those changes are related to missing system functions under BeOS (it is only an "almost" POSIX system).

A lot of feature are not tested or even not implemented (like threading for example). But at least, it should be enough to do a "make zipinstall".

All those files may still need a lot of work before finding a path to the source tree, so comments (especially about the second part as there is changes in common source files) and improvements are welcome.

A binary version of the trunk (fpc 2.3.1, revision 7420) is available at http://olivier.coursiere.free.fr/download/fpc-2.3.1.i386-beos.tar.gz (compiled under BeOS R5 with BONE).

Regards,

Olivier

Reply by email

Marco van de Voort
to Olivier Coursiere
Show quoted text 17 lines
After a long period of inactivity, i finally took the time to update the BeOS port of fpc. I have successfully compiled the latest trunk (revision 7420) under BeOS using a new libc based RTL (1.0.* versions were based on system calls). The patch i propose to achieve this is in two parts : - the first part is a zip file containing all files in the ../rtl/beos directory. As there is a lot of change in this directory, i think it does not make sense to produce a diff file. This file is available at http://olivier.coursiere.free.fr/diff/beos.zip. - the second part is a diff file of all other changes made to compile fpc under BeOS (based on revision 7420). This file is available at http://olivier.coursiere.free.fr/diff/beos.diff. Most of those changes are related to missing system functions under BeOS (it is only an "almost" POSIX system).

I'll have a look at it in this weekend.

Reply by email

Peter Vreman
to Olivier Coursiere: After a long period of inactivity, i finally took the time to update the BeOS port of…
Show quoted text 29 lines
Hi all, After a long period of inactivity, i finally took the time to update the BeOS port of fpc. I have successfully compiled the latest trunk (revision 7420) under BeOS using a new libc based RTL (1.0.* versions were based on system calls). The patch i propose to achieve this is in two parts : - the first part is a zip file containing all files in the ../rtl/beos directory. As there is a lot of change in this directory, i think it does not make sense to produce a diff file. This file is available at http://olivier.coursiere.free.fr/diff/beos.zip. - the second part is a diff file of all other changes made to compile fpc under BeOS (based on revision 7420). This file is available at http://olivier.coursiere.free.fr/diff/beos.diff. Most of those changes are related to missing system functions under BeOS (it is only an "almost" POSIX system). A lot of feature are not tested or even not implemented (like threading for example). But at least, it should be enough to do a "make zipinstall". All those files may still need a lot of work before finding a path to the source tree, so comments (especially about the second part as there is changes in common source files) and improvements are welcome. A binary version of the trunk (fpc 2.3.1, revision 7420) is available at http://olivier.coursiere.free.fr/download/fpc-2.3.1.i386-beos.tar.gz (compiled under BeOS R5 with BONE).

Thanks, the patches are applied. One small change in ttyname.inc to use {$ifndef beos} instead of disabling the code for all platforms.

Peter

Reply by email

Marco van de Voort
to Olivier Coursiere
Show quoted text 11 lines
Peter Vreman a ?crit : > Thanks, the patches are applied. One small change in ttyname.inc to use {$ifndef beos} instead of > disabling the code for all platforms. > Oups ! I forgot this one. This is why code review is important. After updating my working copy, i found that i forgot two lines in netdb/makefile.fpc to successfully "make zipinstall" : The diff file is available at http://olivier.coursiere.free.fr/diff/netdb.diff.

Done

Reply by email

Florian Klaempfl
to Marco van de Voort
Show quoted text 13 lines
> Peter Vreman a ?crit : >> Thanks, the patches are applied. One small change in ttyname.inc to use {$ifndef beos} instead of >> disabling the code for all platforms. >> > Oups ! I forgot this one. This is why code review is important. > > After updating my working copy, i found that i forgot two lines in > netdb/makefile.fpc to successfully "make zipinstall" : > > The diff file is available at > http://olivier.coursiere.free.fr/diff/netdb.diff. Done

Do you plan to continue with the BeOS port? Then we can grant you svn write access.

Reply by email

Olivier Coursiere
to Florian Klaempfl

Hi,

Florian Klaempfl wrote
Do you plan to continue with the BeOS port? Then we can grant you svn write access.

Thank you for the offer.

Yes, i will continue with the BeOS port. Just don't expect too much from me :-) The only fixed item in my plan is to keep the compiler working under BeOS and make sure basic stuff will work on the upcoming Haiku-OS. Thanks to binary compatibility, the compiler can already compile a simple "Hello world" on this platform.

It could be interesting to have access only to the rtl/beos directory, as i am not yet confident in my SVN's knowledge to avoid mistakes. Committing only from this directory in my working copy should work too, i think, but less secure. For other changes, i think it is better to send patchs for review. There is probably some rules i am not aware of to avoid breaking others targets.

Olivier

Reply by email