On Wednesday, August 07, 2013 02:57:00 PM Jakub Jermar wrote: > Hi Zbigniew, > > On 6.8.2013 2:30, Zbigniew Halas wrote: > > I have been busy with other thing and haven't been working on Helenos > > recently, but now I'm planning to bring my Python port to fully usable > > state. The next thing needed is a math library. I'm planning to integrate > > openlibm (https://github.com/JuliaLang/openlibm/) with Helenos. > > which is meant to be a standalone math library. It's based on FreeBSD's > > msun library (which is in turn based on Sun's fdlibm). > > As it's standalone it should be easier to port than FreeBSD's msun > > library, > > and actually I managed to build it for ia32 architecture (with a few dirty > > hacks) in not too long time and try it with Python. > > > > What are you thoughts on integrating openlibm into Helenos? > > My general idea has been that perhaps your python port and its > dependencies, including openlibm, could live in the Vojta's coastline > repository, together with the gcc port and all other non-native things. > > http://vhotspur.blogspot.cz/2013/03/introducing-helenos-coastline.html
I was thinking of that approach as well. The only drawback is that some libm functions (or rather stubs) are implemented as part of HelenOS POSIX library and they are required to build some components being part of HelenOS (binutils at least). It could be solved by using proper linking order or by separating libm functions from POSIX library which will allow to link POSIX library independently from libm. If you think it's a proper solution I will do that. Cheers, Zbigniew _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
