> On Wen, Oct 1, 2014 at 2:30 PM, <[email protected]> wrote: > [...] similar to GCC [the proprietary toolchain] uses a control program > (cctc.exe), which calls the real assembler/compiler/linker depending on > command line options. So the behaviour of the compile-step and the link-step > shouldn't be different from tup's point-of-view, I guess.
Just to make sure this is not an issue of the control program: I replaced the control program command by calling the linker executable directly (using the same command line the control program would have used to call the linker) and I see the exact same behaviour of tup. Kind regards, Bernhard. -- -- tup-users mailing list email: [email protected] unsubscribe: [email protected] options: http://groups.google.com/group/tup-users?hl=en --- You received this message because you are subscribed to the Google Groups "tup-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
