Hi, I have put together a few packages which package the mingw gcc compiler as a cross-compiler using ABS. I have one question about standard locations and one question about general ABS usage.
1) It seems that it is standard, for cross-compilers, to store all compiler-specific libraries, includes, etc. in $(prefix)/$(target). In this case, this would be /usr/i686-mingw32. namcap reports this as a non-standard directory. Is there another location which is more Arch Linux? Or is this location fine as it stands? I'm not sure it would be an easy thing to change the location, but I thought I'd ask anyway 2) This one is slightly more complicated. The problem with building a cross-compiler is there's a certain amount of bootstrapping that has to happen. The MinGW binutils cross-compile without a hitch, but building an initial compiler relies on all the right headers being in place, and building the extra languages requires an initial compiler, as it requires the mingw-runtimes and the win32api to already have been cross-compiled. I've managed to do this in the following packages, each of which depends on the last: mingw32-binutils: This holds the binutils mingw32-headers: This installs the headers for the win32api and the mingw runtimes mingw32-gcc-base: This installs gcc (just the C compiler), the win32api and the mingw runtimes mingw32-gcc: This installs the g++ and objc cross-compilers. The last three cumulatively do the same as the base/gcc package does for the native compiler in one package. It occurred to me that someone might have hit bootstrapping problems like this before, so I was wondering if anyone has any ideas of how to get those three packages down to one. Anyone? How was the first gcc built for Arch Linux? Finally, I was interested to find out whether there are other people on this list interested in a cross-compiler package. Are there? TIA, David Moore _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
