<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>240280</bug_id>
          
          <creation_ts>2008-10-06 13:36 0000</creation_ts>
          <short_desc>dev-util/git: C(XX)FLAGS are ignored (at src_configure/compile)</short_desc>
          <delta_ts>2008-11-24 01:23:42 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>flameeyes@gentoo.org</reporter>
          <assigned_to>ferdy@gentoo.org</assigned_to>
          <cc>robbat2@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>flameeyes@gentoo.org</who>
            <bug_when>2008-10-06 13:36:11 0000</bug_when>
            <thetext>I don&apos;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&apos;s not respecting CFLAGS (or CXXFLAGS) properly.

Please look into it, since it&apos;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 &quot;set in stone&quot; in the build system during src_unpack/src_prepare. While QA has not as of this moment expressed to me a preference, I&apos;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 &apos;$(CFLAGS)&apos;, single quoted, so that the CFLAGS variable is picked up;
- use &apos;$(OPTCFLAGS)&apos; in the sed and then use make OPTCFLAGS=$CFLAGS.

Thanks,
Diego</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>robbat2@gentoo.org</who>
            <bug_when>2008-11-24 01:23:42 0000</bug_when>
            <thetext>Fixed in ~arch tip ebuild of CVS.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>