On Fri, 19 Jul 2002, Tom Tromey wrote:
[...] > Grzegorz> Question: how can I get *.o files in the external linker > Grzegorz> command line? > > You can't. The .lo files are the ones you want, as they are compiled > -fPIC. Linking the .o files would be incorrect on some platforms. > > It is arguably a bug in purify that it can't handle this. I would hardly call it a bug. Some tools just understand .o/.so (or local equivalents), but not .lo . This is lack of feature. [...] > Grzegorz> And yet one funny thing. When in the example above I replace > Grzegorz> $(SRCS) with explicit "foo.cc", the external link command > Grzegorz> becomes > Grzegorz> purify g++ -o foo.pure foo_pure-foo.o > > Adding a per-executable *FLAGS setting causes the .o files to be > renamed by automake. That's to avoid clashes when a file is compiled > twice with different flags. I was puzzled by the extension rather than the prefix. My confusion was due to the bug in Automake 1.6 mentioned earlier by Alexandre. Thanks Grzegorz ################################################################## # Grzegorz Jakacki Huada Electronic Design # # Senior Engineer, CAD Dept. 1 Gaojiayuan, Chaoyang # # tel. +86-10-64365577 x2074 Beijing 100015, China # ##################################################################
