[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: Brian
Subject: Re: Force -O0 flags, inhibit the default -O2 flags
Date: Tue, 27 Sep 2005 19:38:04 -0600

We have several files which are not able to be optimized, and when our mac
mini tries to build the project it chokes up when attempting to do so. It
seems incorrect to say that the package developer is the least qualified to
judge compiler flags, and it also seems to avoid the point. The package
developer should be able to override the autotools, and the user should be
able to override the developer. It is not a matter of qualification, it is a
matter of the chain of command. Right now the chain of command is user -->
autotools --> developer. In reality it should be user --> developer -->

Thanks for the comments - a most distressing problem,

On 9/27/05, Bob Friesenhahn <address@hidden> wrote:
> 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
> ======================================
> Bob Friesenhahn
> address@hidden,
> GraphicsMagick Maintainer,

reply via email to

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