On Mon, 1 Jul 2024, Stefano Zampini wrote: > Il giorno lun 1 lug 2024 alle ore 16: 43 meator <meator. dev@ gmail. com> ha > scritto: > > > Thank you for your reply! > > > > On 7/1/24 4: 14 PM, Barry Smith wrote: 
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
 
ZjQcmQRYFpfptBannerEnd
On Mon, 1 Jul 2024, Stefano Zampini wrote:

> Il giorno lun 1 lug 2024 alle ore 16:43 meator <[email protected]> ha
> scritto:
> 
> > Thank you for your reply!
> >
> > On 7/1/24 4:14 PM, Barry Smith wrote:

> > We have had well over a decade of debates on this issue. I would
> > like to see a CFLAGS+=extra_flags option but that has been
> > resisted.  Instead Satish can tell you how to get what you want.

Current interface is 'replace' defaults.

Its a bad user interface when the defaults can't be over-ridden by
user. And invariably there are use cases when such a over-ride can be
required [perhaps fewer now than before]

However if CFLAGS+=extra_flags can be added to configure API [instead
of replacing the current default] that would be fine. So far its need
is minimal - esp with the availability of other easy alternatives.
[and making such change to configure , and managing its complexity is
a major task]

> > I admit it is not so standard, but Satish always opposed this.

> No need to hack the buildsystem, just use COPTFLAGS, CXXOPTFLAGS and
> FOPTFLAGS

Our configure interface has:

CPPFLAGS
CFLAGS
COPTFLAGS

in most cases - one can use CPPFLAGS instead of overriding CFLAGS

And Overriding COPTFLAGS (defaults) is easier than overriding CFLAGS -
as most users want to change opt flags - and not others.

However if none of the above is suitable for user needs, one can skip
listing these additional flags to configure - and directly list them
with make.

./configure

make CFLAGS='additional-flags'

Satish

Reply via email to