On 8/8/2013 5:24 PM, Attila Krasznahorkay wrote: > Hi Hanspeter, > > It's worth mentioning that gccxml doesn't play all that nicely with the > current version (4.2.1) of clang. In order to get it to work, one has to > force it to use gcc as its "backend". There are multiple ways of doing it, > but the simplest is to put > > GCCXML_COMPILER=gcc > > into one's environment.
From this upstream commit [1], it seems that the compiler used to build gccxml and the compiler gccxml uses at runtime can be separated. So in your example above, I take it you mean that if clang is used to compile gccxml, GCCXML_COMPILER=gcc must be set so that 'gcc' is used for parsing input files, because parsing with clang will fail. Since 'gcc' is rather indeterminate, would compiling with gcc-fsf-4.8 (Fink's name for the gcc48 compiler) make it then automatically use that as the 'backend'? Hanspeter [1] https://github.com/gccxml/gccxml/commit/1bfbbe93ae16e97b010fb111305d169e3dcfd5a4 ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Fink-users mailing list [email protected] List archive: http://news.gmane.org/gmane.os.macosx.fink.user Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-users
