Dimitry Andric d2cc835cb5 After r217375, some startup objects under lib/csu are built in a special ... way: first they are compiled to assembly, then some sed'ing is done on the assembly, and lastly the assembly is compiled to an object file. This last step is done using ${CC}, and not ${AS}, because when the compiler is clang, it outputs directives that are too advanced for our old gas. So we use clang's integrated assembler instead. (When the compiler is gcc, it just calls gas, and nothing is different, except one extra fork.) However, in the .s to .o rules in lib/csu/$ARCH/Makefile, I still passed CFLAGS to the compiler, instead of ACFLAGS, which are specifically for compiling .s files. In case you are using '-g' for debug info anywhere in your CFLAGS, it causes the .s files to already contain debug information in the assembly itself. In the next step, the .s files are also compiled using '-g', and if the compiler is clang, it complains: "error: input can't have .file dwarf directives when -g is used to generate dwarf debug info for assembly code". Fix this by using ${ACFLAGS} for compiling the .s files instead. Reported by: jasone MFC after: 1 week		2012-04-20 21:00:39 +00:00
..
crt1.S	Let all .c and .S files under lib/csu consistently use the __FBSDID()	2010-12-09 21:31:21 +00:00
crti.S	Let all .c and .S files under lib/csu consistently use the __FBSDID()	2010-12-09 21:31:21 +00:00
crtn.S	Let all .c and .S files under lib/csu consistently use the __FBSDID()	2010-12-09 21:31:21 +00:00
Makefile	After r217375, some startup objects under lib/csu are built in a special	2012-04-20 21:00:39 +00:00