On Sep 8, 8:18 pm, David Kirkby <david.kir...@onetel.net> wrote: > If CFLAGS is not being passed to the compiler (which is what I thought > before), and LDFLAGS is passed to the compiler, then this could > explain why you need to set LDFLAGS.
>From Autoconf manual: If a compiler option affects only the behavior of the preprocessor (e.g., -D name), it should be put into CPPFLAGS instead. If it affects only the linker (e.g., -L directory), it should be put into LDFLAGS instead. If it affects only the compiler proper, CFLAGS is the natural home for it. If an option affects multiple phases of the compiler, though, matters get tricky. One approach to put such options directly into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS and LDFLAGS, but not into CFLAGS. So, a compiler option may affect the link phase and in that case it may go into LDFLAGS not in CFLAGS. Another option is to change CC, but I would say that is a bit more dangerous. Juanjo --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
