#855: config/init/defaults.pm:  Profiling options are too specific to GCC
-----------------------+----------------------------------------------------
 Reporter:  jkeenan    |       Owner:  jkeenan          
     Type:  bug        |      Status:  assigned         
 Priority:  minor      |   Milestone:                   
Component:  configure  |     Version:  1.3.0            
 Severity:  medium     |    Keywords:  profile gcc debug
     Lang:             |       Patch:                   
 Platform:  all        |  
-----------------------+----------------------------------------------------
Changes (by jkeenan):

  * owner:  => jkeenan
  * status:  new => assigned


Comment:

 Replying to [comment:7 doughera]:
 {{{
 Since you don't know which compiler you have until the
 config::inter:progs step, this code should probably all
 be moved there from its current home of init::defaults.
 }}}
 Andy, I noticed that in inter::progs we '''already''' have some code for
 doing a "debugging build" of Parrot:
 {{{
     143 sub _get_debug {
     144     my ($conf, $ask) = @_;
     145     my $debug = 'n';
     146     $debug = 'y' if $conf->options->get('debugging');
     147     $debug = prompt( "Do you want a debugging build of Parrot?",
 $debug         )
     148         if $ask;
     149     return $debug;
     150 }
 ...
     157 sub _set_debug_and_warn {
     158     my ($conf, $debug) = @_;
     159     if ( $debug =~ /n/i ) {
     160         $conf->data->set(
     161             cc_debug   => '',
     162             link_debug => '',
     163             ld_debug   => ''
     164         );
     165     }
 }}}
 So it seems that whatever is currently being set in `init::defaults`, it
 is being overwritten in `inter::progs`.

 Is there any meaningful distinction between the `profile` configuration
 option handled in `init::defaults` and the `debugging` option handled in
 `inter::progs`?  Couldn't we collapse the two into each other?  And if we
 do so, which should be the name of the option: 'profile' or 'debugging'?

 (Also will the regex `m/sun|solaris/i` suffice for recognizing those
 compilers?)

 Thank you very much.

 kid51

-- 
Ticket URL: <https://trac.parrot.org/parrot/ticket/855#comment:8>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets

Reply via email to