Bug 240790 – mail-mta/exim: C(XX)FLAGS are ignored (at src_configure/compile)

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Diego Elio Pettenò (RETIRED) 2008-10-09 21:20:25 UTC]

I don't know the build system for this program (and this is a generic bug template so I cannot tell you which program exactly is), but my tests shows that it's not respecting CFLAGS (or CXXFLAGS) properly.

Please look into it, since it's important to respect user CFLAGS and CXXFLAGS.

Warning: this bug might look like a false positive because you actually have your CFLAGS being used; this happens if the CFLAGS are "set in stone" in the build system during src_unpack/src_prepare. While QA has not as of this moment expressed to me a preference, I'd sincerely suggest to avoid the set-in-stone approach, so that ebuild commands could work to reproduce the actual results.

To avoid the set in stone approach:

- consider just changing CFLAGS= to CFLAGS+= if the build system enables warnings;
- if the buildsystem does not use CFLAGS variable at all, in the sed use '$(CFLAGS)', single quoted, so that the CFLAGS variable is picked up;
- use '$(OPTCFLAGS)' in the sed and then use make OPTCFLAGS=$CFLAGS.

Thanks,
Diego

[Comment 1 Colin Morey (RETIRED) 2008-12-07 14:31:41 UTC]

Diego,
    do you have any specific results for exim? as as far as I can see, CFLAGS should be being respected happily.

Cheers,

Colin

[Comment 2 Torsten Veller (RETIRED) 2009-06-24 13:33:16 UTC]

Reassign to net-mail herd as peitolm retires

[Comment 3 Fabian Groffen 2009-07-02 20:27:44 UTC]

Diego can you please provide how this can be verified?  The build system hides in it's output cflags stuff by default, but it does use it.  I committed a small change to exim-4.69-r2 to be more verbose during compilation, but it all looks ok to me.

I'm closing this bug to get a better idea of what's left to be done for Exim.  If you have more information, please reopen.