[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Force -O0 flags, inhibit the default -O2 flags

From: Bob Friesenhahn
Subject: Re: Force -O0 flags, inhibit the default -O2 flags
Date: Tue, 27 Sep 2005 18:36:25 -0500 (CDT)

On Tue, 27 Sep 2005, Harald Dunkel wrote:
So the user has to write

        make CFLAGS= CXXFLAGS= install

to get the default flags (AM_CXXFLAGS, etc.) provided by the developer?
Sorry, but this is weird. Are there any other flags the user has to
reset to get the flags specified by the developer? Actually the
developer doesn't know, because maybe the next version of autoconf
redefines even more variables that he thought he had set savely in his And surely the user doesn't know, either.

In my experience, the package developer is often the least qualified to judge compiler flags. It is very rare that specific flags are necessary for a package to work correctly. It is far more common that the package developer enforces flags which don't work at all with the installer's compiler and cause a complete failure.

Bob Friesenhahn
GraphicsMagick Maintainer,

reply via email to

[Prev in Thread] Current Thread [Next in Thread]