>>> i'm fighting with the attached llvmgcc target definition, but i got >>> stuck, and can't ffigure out where do cflags leak into ldflags. just >>> try building it, you'll see. >>> cluebat, please? >> >> For some reason CPPFLAGS is passed to linker >> (while CFLAGS isn't). This is so since the beginning, >> and no one has touched this remaining strangeness yet. > > it's actually CFLAGS, and is in rules.mk:66 > > is there any ill effect were it to be removed? i'm in a sort of a
I suspect there is, anyhow it would be good to solve this. > hurry now, but without this, at least linux/gcc, linux/g++, > linux/sunpro and linux x os2/watcom c++ is still ok, whereas llvmgcc > definitely gets further on (and now blows up in what at cursory > eyeballing seems to be hb-mkdyn, which is understandable). hb-mkdyn is used only for some smaller tasks at postinst phase, the dynlibs are now created directly by the make system, so maybe the problem isn't that bad. Brgds, Viktor _______________________________________________ Harbour mailing list (attachment size limit: 40KB) [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
