omission: clang-cc -MD -MF -c -fPIC

Hi,

I do not really have much direct control over the compile lines any more.
I guess I could code up a wrapper for your wrapper so that the libtool wrapper
would be happy, but could you all consider libtool built projects and
embed the necessary option stripping in your clang-cc thing?
Thank you.
Regards, Bruce

make[2]: Entering directory `/home/bkorb/ag/ag/snprintfv'
/bin/sh ../libtool --tag=CC --mode=compile clang-cc -DHAVE_CONFIG_H
-I. -I.. -I.. -g -MT snv.lo -MD -MP -MF .deps/snv.Tpo -c -o snv.lo
snv.c
libtool: compile: clang-cc -DHAVE_CONFIG_H -I. -I.. -I.. -g -MT
snv.lo -MD -MP -MF .deps/snv.Tpo -c snv.c -fPIC -DPIC -o .libs/snv.o
clang-cc: Unknown command line argument '-MD'. Try: 'clang-cc --help'
clang-cc: Unknown command line argument '-MF'. Try: 'clang-cc --help'
clang-cc: Unknown command line argument '-c'. Try: 'clang-cc --help'
clang-cc: Unknown command line argument '-fPIC'. Try: 'clang-cc --help'

[retrying send with different email source]

Hi,

I do not really have much direct control over the compile lines any more.
I guess I could code up a wrapper for your wrapper so that the libtool wrapper
would be happy, but could you all consider libtool built projects and
embed the necessary option stripping in your clang-cc thing?
Thank you.
Regards, Bruce

make[2]: Entering directory `/home/bkorb/ag/ag/snprintfv'
/bin/sh ../libtool --tag=CC --mode=compile clang-cc -DHAVE_CONFIG_H
-I. -I.. -I.. -g -MT snv.lo -MD -MP -MF .deps/snv.Tpo -c -o snv.lo
snv.c
libtool: compile: clang-cc -DHAVE_CONFIG_H -I. -I.. -I.. -g -MT
snv.lo -MD -MP -MF .deps/snv.Tpo -c snv.c -fPIC -DPIC -o .libs/snv.o
clang-cc: Unknown command line argument '-MD'. Try: 'clang-cc --help'
clang-cc: Unknown command line argument '-MF'. Try: 'clang-cc --help'
clang-cc: Unknown command line argument '-c'. Try: 'clang-cc --help'
clang-cc: Unknown command line argument '-fPIC'. Try: 'clang-cc --help'

I'm not sure how this conversation started, but you should probably be
using "clang" rather than "clang-cc" directly.

If you have more questions, it would probably be better to discuss on cfe-dev.

-Eli

Hi Bruce,

clang-cc is similar to cc1. It is a low-level compiler driver not meant to be directly called by most clients. You should use 'clang' instead, which acts as a drop-in replacement to gcc. Please also send Clang-related emails to cfe-dev, which is the list for Clang development.

Hi Ted,

Thank you! I read all three "RTFM" admonishments as well as the "FM" and
came away with using the cc1 replacement and the llvmdev list. Sorry.
Thank you for the pointers. Regards, Bruce