This is the mail archive of the libc-alpha@sources.redhat.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: use CPPFLAGS at configure time


On Apr  4, 2003, Roland McGrath <roland at redhat dot com> wrote:

> I have checked in configure changes to make it consistent throughout.

CFLAGS must be used in every invocation of the C compiler, both those
which do compilation and those which do linking.  This is straight
from the GNU coding standards.

For assembling, it is often expected that $(AS), not $(CC), will be
used.  Using $(CC) is more convenient because it lets CC do the right
thing and pass the right flags to the assembler, but not passing
$(CFLAGS) to $(CC) in this case prevents relevant compiler options
that may (and should) affect the generated object file from being
passed to the assembler.  E.g., -Wa,-option, that should affect all
code that is assembled, is now dropped after your rearrangement.  Even
options such as -fPIC/-fpic on a number of platforms cause options
such as -KPIC to be passed to the assembler.  Taking CFLAGS out in
this case is wrong, very wrong.  Please put it back in.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva at {redhat dot com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva at {lsd dot ic dot unicamp dot br, gnu.org}
Free Software Evangelist                Professional serial bug killer


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]