Bug 100092 – profile USE flag broken in glibc-2.3.5-r1 and above

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Ryan Hill (RETIRED) 2005-07-23 21:09:40 UTC]

the glibc-2.3.5-r1 ebuild appends --enable-profiling to ${myconf} when the user
enables the profile use flag.

  use profile && myconf="${myconf} --enable-profiling"

but according to glibc the switch should actually be --enable-profile.

# ../glibc-2.3.5/configure --help

  [...]
  --enable-profile        build profiled library [default=yes]
  [...]

also, if this option is enabled by default, then the way the ebuild is set up
now will always build with profiling regardless of the USE flag.  ie. if the
user enables the USE flag then the switch is appended and if they disable it it
still defaults to on.  something like this might make more sense:

use profile || myconf="${myconf} --disable-profile"

[Comment 1 SpanKY 2005-08-06 21:13:12 UTC]

fixed in cvs

[Comment 2 Jakub Moc (RETIRED) 2005-08-10 06:49:53 UTC]

*** Bug 101979 has been marked as a duplicate of this bug. ***

[Comment 3 Jan Jitse Venselaar 2005-08-10 07:02:58 UTC]

The bug marked as duplicate of this bug, is not fixed yet.  
The bug was:  
 
In the recent glibc ebuilds, the profile use-flag was added.   
I found that it does not do anything, due to the --disable-profile flag passed  
to myconf, after the --enable-profile setting by the use flag.   
The disabling occurs at line 893 in the glibc-2.3.5-r1 ebuild, the enabling at  
line 857.  
 
Reproducible: Always 
Steps to Reproduce: 
1. set profile in use-flafs  
2. compile glibc  
  
Actual Results:   
No profile enabled glibc (checked by stopping the build after configuring and  
checking the config.in)  
 
Expected Results:   
profiled build of glibc 

[Comment 4 SpanKY 2005-08-10 10:29:55 UTC]

will review

[Comment 5 Jeremy Huddleston (RETIRED) 2005-08-10 15:27:47 UTC]

fixed in cvs, thanks.