Hi, Last week I started coding after several setbacks. I made a build process structure for gcc similar to that done for binutils. Currently, I am working with gcc-core-4-6.3, but there would not be a big problem when bumping to gcc-4.7.0. I chose the core package so as to not confuse me with the new packaging structure of gcc-4.7.0 where all the components are present at one place, and also because my primary goal now is to port the C compiler part.
I started my porting attempt with cross-compilation of gcc. I will be using the target `all-gcc' in the gcc-core Makefile.in to initiate the target build from my Makefile. But before that, the challenge is to get past the configure stage with host and target set to that of the HelenOS. This stage requires the presence of libgmp, libmpfr and libmpc. So the configure stage currently fails and asks for the location of gmp (--with-gmp) , mpfr (--with-mpfr) and mpc (--with-mpc) to proceed. Now, I have started porting the libgmp and libmpfr. There are few questions related to design decisions about which I would like to get suggestions: 1. gcc will obviously go in uspace/app/, am i right? 2. The external libraries libgmp, libmpfr and libmpc should be placed in uspace/app/gcc/dependencies/lib/ or other directory e.g. uspace/lib ? I have also started looking at libposix at what functions or stubs needs to be implemented or improved there. That will become evident in the porting process. So, my next step is to port the external libraries on which gcc build is dependent and then proceed forward. Also the current patching of gcc source is very minimal, with cross_compilation flags set to `yes'. I am studying the source too to examine what all sorts of patching that are required. Thanks, Vivek Prakash _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
