I quickly wrote up the following two files: /etc/env.d/05gcc-arm-wince-mingw32ce --------------------------------------------------------- PATH="/opt/mingw32ce/arm-wince-mingw32ce/bin" ROOTPATH="/opt/mingw32ce/arm-wince-mingw32ce/bin"
/etc/env.d/gcc/arm-wince-mingw32ce-4.1.0 -------------------------------------------------------------- LDPATH="/opt/mingw32ce/lib/gcc/arm-wince-mingw32ce/4.1.0" MANPATH="/opt/mingw32ce/man" INFOPATH="/opt/mingw32ce/info" STDCXX_INCDIR="c++/4.1.0" CTARGET=arm-wince-mingw32ce GCC_PATH="/opt/mingw32ce/arm-wince-mingw32ce/bin" When I run 'gcc-config -l', it detects the configuration files, of course, but there are some differences, resulting in the error: * gcc-config: Profile does not exist or invalid setting for /etc/env.d/gcc/arm-wnce-mingw32ce-4.1.0 I believe this has to do with the fact that the 'system' libraries and header files aren't located in /opt/mingw32ce/lib/arm-wince-mingw32ce. For gentoo toolchains, that would be equivalent to /usr/lib/gcc/(ctarget). Perhaps if the system libraries and c++ headers were copied into /opt/mingw32/lib/arm-wince-mingw32/4.1.0, then it might work.... hmm... no error, but arm-wince-mingw32ce-gcc still isn't in the PATH. So much for that. I guess if it's _absolutely_ necessary to work with gcc-config, then we could easily obtain the original source and the cegcc diffs, and compile it using Gentoo rpaths. Regards, Chris On Sat, Mar 28, 2009 at 8:41 PM, Christopher Friedt <[email protected]> wrote: > Hi Nathan, > > On Sat, Mar 28, 2009 at 8:13 PM, Nathan Brink > <[email protected]> wrote: >> layman -f -o http://virtb.visibleassets.com:2080/layman.conf -a cegcc >> You cegcc-mingw32ce ebuild worked out great. I even compiled my first CE >> program from a hello-world example :-). >> Now, it'd be nice if your ebuild could hook into gcc-config or crossdev >> somehow... but at least it works > > Thanks for pointing out the '-f' flag - that's quite important I would > imagine. > > Gcc is a very tricky beast. The Gentoo folks (particularly Mike > Frysinger / vapier) have worked very hard to quasi-standardize > toolchain installation directories (library, header, and 'sysroot') so > that everything 'just works'. Why it 'just works', is that certain > paths (rpaths) need to be hard-coded for the toolchain to work > properly. To do that the compiler needs to be built from scratch, so a > binary toolchain might not be flexible enough. > > In spite of differing rpaths, gcc-config might still work. Let me give > it a try. If it works out, I'll update the overlay and post back to > this list ... I guess I should post to gentoo-embedded as well. > > Cheers, > > C > _______________________________________________ Haret mailing list [email protected] https://handhelds.org/mailman/listinfo/haret
