On 21.12.2012 18:12, Philip Martin wrote: > Branko Čibej <br...@wandisco.com> writes: > >> On 21.12.2012 18:03, Branko Čibej wrote: >>> On 21.12.2012 18:02, Philip Martin wrote: >>>> Branko Čibej <br...@wandisco.com> writes: >>>> >>>>> On 21.12.2012 16:36, Philip Martin wrote: >>>>>> So the build system used to strip -std=c89 and now does not. If I >>>>>> remove -std=c89 from SWIG_RB_COMPILE in Makefile the build works. >>>>> Thanks. Apparently I either missed that somehow, or this option came >>>>> from the Ruby compile flags, not ours. Will try to fix. >>>> I added it when I ran configure. >>> Oh. Dare I say, "don't do that"? :) >> Just to be clear: The intent of the changes is, amongst other things, >> that configure determines these kinds of flags and keeps them in a >> separate variable, precisely so that we don't have to strip them from >> anywhere. Of course, running "env CFLAGS=-ansi ./configure" defeats that. >> >> I'd prefer to not support that kind of usage. > trunk doesn't add a -std flag and I wanted to build with one. I'd like > a system that allows me to specify arbitrary flags that get used to > compile our code but that do not get used when compiling "other" > generated code.
Does "make EXTRA_CFLAGS=..." not give you exactly that? -- Brane -- Branko Čibej Director of Subversion | WANdisco | www.wandisco.com
