Bug 240784

Summary:	mail-filter/libmilter: C(XX)FLAGS are ignored (at src_configure/compile)
Product:	Gentoo Linux	Reporter:	Diego Elio Pettenò (RETIRED) <flameeyes>
Component:	New packages	Assignee:	Alin Năstac (RETIRED) <mrness>
Status:	RESOLVED CANTFIX
Severity:	normal	CC:	net-mail+disabled
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Diego Elio Pettenò (RETIRED) gentoo-dev

2008-10-09 21:18:32 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 Alin Năstac (RETIRED) gentoo-dev

2008-10-12 17:09:19 UTC

This is a case of "set in stone" false positive.

Sorry, but I cannot do anything about it, given the rather unorthodox way in which sendmail.org build its libraries/programs (they set variables such as CFLAGS or ENVDEFS through a m4 script :-/).

Anyway, you are free to fix it yourself if you think you can do it... :-P
In the meantime, closed as CANTFIX.