Hi Vivek, thanks for your update! Please see my responses below.
> Hi, > > Last week I started coding after several setbacks. Good to hear you are alright and coding :-) > 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. OK, as long as you are confident enough that the move to gcc-4.7.0 should not be a problem. > .... > 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? Yes. Eventually we might make some common subdirectory(-ies) for ported software (akin to BSD ports) due to the ultimately different method of building it (and one day there could be some common framework for that). For now uspace/app/gcc seems adequate. > 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 think if we had some kind of ports dir, eg. with uspace/ports/gcc, then I would put them in uspace/ports/libxyz, with uspace/app/gcc I'd prefer the former variant, i.e. place them under gcc - this should work nicely for now, since gcc will be the only consumer for now. Cheers -Jiri _______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/cgi-bin/listinfo/helenos-devel
