4 use File::Basename qw(&basename &dirname);
6 # List explicitly here the variables you want Configure to
7 # generate. Metaconfig only looks for shell variables, so you
8 # have to mention them as if they were shell variables, not
9 # %Config entries. Thus you write
11 # to ensure Configure will look for $Config{startperl}.
14 # This forces PL files to create target in same directory as PL file.
15 # This is so that make depend always knows where to find PL derivatives.
17 $file = basename($0, '.PL');
18 $file .= '.com' if $^O eq 'VMS';
20 open OUT,">$file" or die "Can't create $file: $!";
22 # extract patchlevel.h information
24 open PATCH_LEVEL, "<../patchlevel.h" or die "Can't open patchlevel.h: $!";
26 my $patchlevel_date = (stat PATCH_LEVEL)[9];
28 while (<PATCH_LEVEL>) {
29 last if index($_, "static\tchar\t*local_patches[] = {") >= 0;
33 while (<PATCH_LEVEL>) {
39 $patches .= "'$_',\n" unless $_ eq 'NULL';
45 print "Extracting $file (with variable substitutions)\n";
47 # In this section, perl variables will be expanded during extraction.
48 # You can use $Config{...} to use Configure variables.
50 print OUT <<"!GROK!THIS!";
52 eval 'exec $Config{perlpath} -S \$0 \${1+"\$@"}'
53 if \$running_under_some_shell;
55 my \$patchlevel_date = $patchlevel_date;
56 my \@patches = ( $patches );
59 # In the following, perl variables are not expanded during extraction.
61 print OUT <<'!NO!SUBS!';
67 eval "use Mail::Send;";
68 $::HaveSend = ($@ eq "");
69 eval "use Mail::Util;";
70 $::HaveUtil = ($@ eq "");
79 my($Version) = "1.19";
81 # Changed in 1.06 to skip Mail::Send and Mail::Util if not available.
82 # Changed in 1.07 to see more sendmail execs, and added pipe output.
83 # Changed in 1.08 to use correct address for sendmail.
84 # Changed in 1.09 to close the REP file before calling it up in the editor.
85 # Also removed some old comments duplicated elsewhere.
86 # Changed in 1.10 to run under VMS without Mail::Send; also fixed
87 # temp filename generation.
88 # Changed in 1.11 to clean up some text and removed Mail::Send deactivator.
89 # Changed in 1.12 to check for editor errors, make save/send distinction
90 # clearer and add $ENV{REPLYTO}.
91 # Changed in 1.13 to hopefully make it more difficult to accidentally
93 # Changed in 1.14 to make the prompts a little more clear on providing
94 # helpful information. Also let file read fail gracefully.
95 # Changed in 1.15 to add warnings to stop people using perlbug for non-bugs.
96 # Also report selected environment variables.
97 # Changed in 1.16 to include @INC, and allow user to re-edit if no changes.
98 # Changed in 1.17 Win32 support added. GSAR 97-04-12
99 # Changed in 1.18 add '-ok' option for reporting build success. CFR 97-06-18
100 # Changed in 1.19 '-ok' default not '-v'
101 # add local patch information
102 # warn on '-ok' if this is an old system; add '-okay'
104 # TODO: - Allow the user to re-name the file on mail failure, and
105 # make sure failure (transmission-wise) of Mail::Send is
109 my( $file, $usefile, $cc, $address, $perlbug, $testaddress, $filename,
110 $subject, $from, $verbose, $ed,
111 $fh, $me, $Is_MSWin32, $Is_VMS, $msg, $body, $andcc, %REP, $ok);
115 if($::opt_h) { Help(); exit; }
117 if($::opt_d) { Dump(*STDOUT); exit; }
121 Please use perlbug interactively. If you want to
122 include a file, you can use the -f switch.
127 if(!-t STDOUT) { Dump(*STDOUT); exit; }
130 Edit() unless $usefile;
138 # -------- Setup --------
140 $Is_MSWin32 = $^O eq 'MSWin32';
141 $Is_VMS = $^O eq 'VMS';
143 getopts("dhva:s:b:f:r:e:SCc:to:");
146 # This comment is needed to notify metaconfig that we are
147 # using the $perladmin, $cf_by, and $cf_time definitions.
150 # -------- Configuration ---------
153 $perlbug = 'perlbug@perl.com';
157 $testaddress = 'perlbug-test@perl.com';
160 $address = $::opt_a || ($::opt_t ? $testaddress : $perlbug);
162 # Users address, used in message and in Reply-To header
163 $from = $::opt_r || "";
165 # Include verbose configuration information
166 $verbose = $::opt_v || 0;
168 # Subject of bug-report message
169 $subject = $::opt_s || "";
172 $usefile = ($::opt_f || 0);
174 # File to send as report
175 $file = $::opt_f || "";
178 $body = $::opt_b || "";
181 $ed = ( $::opt_e || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT} ||
182 ($Is_VMS ? "edit/tpu" : $Is_MSWin32 ? "notepad" : "vi")
185 # OK - send "OK" report for build on this system
188 if ( $::opt_o eq 'k' or $::opt_o eq 'kay' ) {
189 my $age = time - $patchlevel_date;
190 if ( $::opt_o eq 'k' and $age > 60 * 24 * 60 * 60 ) {
191 my $date = localtime $patchlevel_date;
193 \"perlbug -ok\" does not report on Perl versions which are more than
194 60 days old. This Perl version was constructed on $date.
195 If you really want to report this, use \"perlbug -okay\".
199 # force these options
200 $::opt_S = 1; # don't prompt for send
201 $::opt_C = 1; # don't send a copy to the local admin
203 $subject = "OK: perl $] on"
204 ." $::Config{'osname'} $::Config{'osvers'} $subject";
206 $body = "Perl reported to build OK on this system.\n";
215 # Possible administrator addresses, in order of confidence
216 # (Note that cf_email is not mentioned to metaconfig, since
217 # we don't really want it. We'll just take it if we have to.)
219 # This has to be after the $ok stuff above because of the way
220 # that $::opt_C is forced.
221 $cc = ($::opt_C ? "" : (
222 $::opt_c || $::Config{perladmin} || $::Config{cf_email} || $::Config{cf_by}
229 ? $ENV{'USER'} || $ENV{'LOGNAME'}
230 : eval { getpwuid($<) }) ); # May be missing
237 # Explain what perlbug is
240 This program provides an easy way to create a message reporting a bug
241 in perl, and e-mail it to $address. It is *NOT* intended for
242 sending test messages or simply verifying that perl works, *NOR* is it
243 intended for reporting bugs in third-party perl modules. It is *ONLY*
244 a means of reporting verifiable problems with the core perl distribution,
245 and any solutions to such problems, to the people who maintain perl.
247 If you're just looking for help with perl, try posting to the Usenet
248 newsgroup comp.lang.perl.misc. If you're looking for help with using
249 perl with CGI, try posting to comp.infosystems.www.programming.cgi.
255 # Prompt for subject of message, if needed
258 First of all, please provide a subject for the
259 message. It should be a concise description of
260 the bug or problem. "perl bug" or "perl problem"
261 is not a concise description.
270 while( $subject =~ /^\s*$/ ) {
271 print "\nPlease enter a subject: ";
281 # Prompt for return address, if needed
284 # Try and guess return address
288 $domain = Mail::Util::maildomain();
289 } elsif ($Is_MSWin32) {
290 $domain = $ENV{'USERDOMAIN'};
292 require Sys::Hostname;
293 $domain = Sys::Hostname::hostname();
295 $domain = `hostname`.".".`domainname`;
296 $domain =~ s/[\r\n]+//g;
303 } elsif ($Is_VMS && !$::Config{'d_socket'}) {
304 $guess = "$domain\:\:$me";
306 $guess = "$me\@$domain" if $domain;
307 $guess = "$me\@unknown.addresss" unless $domain;
310 $guess = $ENV{'REPLYTO'} if defined($ENV{'REPLYTO'});
311 $guess = $ENV{"REPLY-TO"} if defined($ENV{'REPLY-TO'});
318 Your e-mail address will be useful if you need to be contacted. If the
319 default shown is not your full internet e-mail address, please correct it.
326 So that you may be contacted if necessary, please enter
327 your full internet e-mail address here.
332 if ( $ok && $guess ne '' ) {
338 print "Your address [$guess]: ";
343 if($from eq "") { $from = $guess }
348 #if( $from =~ /^(.*)\@(.*)$/ ) {
353 if( $from eq $cc or $me eq $cc ) {
354 # Try not to copy ourselves
359 # Prompt for administrator address, unless an override was given
360 if( !$::opt_C and !$::opt_c ) {
364 A copy of this report can be sent to your local
365 perl administrator. If the address is wrong, please
366 correct it, or enter 'none' or 'yourself' to not send
371 print "Local perl administrator [$cc]: ";
373 my($entry) = scalar(<>);
378 if($me eq $cc) { $cc = "" }
383 if($cc =~ /^(none|yourself|me|myself|ourselves)$/i) { $cc = "" }
385 $andcc = " and $cc" if $cc;
389 # Prompt for editor, if no override is given
390 if(! $::opt_e and ! $::opt_f and ! $::opt_b) {
394 Now you need to supply the bug report. Try to make
395 the report concise but descriptive. Include any
396 relevant detail. If you are reporting something
397 that does not work as you think it should, please
398 try to include example of both the actual
399 result, and what you expected.
401 Some information about your local
402 perl configuration will automatically be included
403 at the end of the report. If you are using any
404 unusual version of perl, please try and confirm
405 exactly which versions are relevant.
407 You will probably want to use an editor to enter
408 the report. If "$ed" is the editor you want
409 to use, then just press Enter, otherwise type in
410 the name of the editor you would like to use.
412 If you would like to use a prepared file, type
413 "file", and you will be asked for the filename.
417 print "Editor [$ed]: ";
419 my($entry) =scalar(<>);
423 if($entry eq "file") {
425 } elsif($entry ne "") {
431 # Generate scratch file to edit report in
434 my($dir) = ($Is_VMS ? 'sys$scratch:' :
435 (($Is_MSWin32 && $ENV{'TEMP'}) ? $ENV{'TEMP'} : '/tmp/'));
436 $filename = "bugrep0$$";
437 $dir .= "\\" if $Is_MSWin32 and $dir !~ m|[\\/]$|;
438 $filename++ while -e "$dir$filename";
439 $filename = "$dir$filename";
443 # Prompt for file to read report from, if needed
445 if( $usefile and ! $file) {
449 What is the name of the file that contains your report?
455 my($entry) = scalar(<>);
461 No filename? I'll let you go back and choose an editor again.
467 if(!-f $entry or !-r $entry) {
470 I'm sorry, but I can't read from `$entry'. Maybe you mistyped the name of
471 the file? If you don't want to send a file, just enter a blank line and you
472 can get back to the editor selection.
484 open(REP,">$filename");
486 my $reptype = $ok ? "success" : "bug";
489 This is a $reptype report for perl from $from,
490 generated with the help of perlbug $Version running under perl $].
497 open(F,"<$file") or die "Unable to read report file from `$file': $!\n";
505 -----------------------------------------------------------------
506 [Please enter your report here]
510 [Please do not change anything below this line]
511 -----------------------------------------------------------------
518 # read in the report template once so that
519 # we can track whether the user does any editing.
520 # yes, *all* whitespace is ignored.
521 open(REP, "<$filename");
536 Site configuration information for perl $]:
540 if( $::Config{cf_by} and $::Config{cf_time}) {
541 print OUT "Configured by $::Config{cf_by} at $::Config{cf_time}.\n\n";
544 print OUT Config::myconfig;
547 print OUT join "\n\t", "\nLocally applied patches:", @patches;
563 Environment for perl $]:
566 (qw(PATH LD_LIBRARY_PATH
569 grep { /^(?:PERL|LC_)/ } keys %ENV)) {
571 exists $ENV{$env} ? "=$ENV{$env}" : ' (unset)',
575 print OUT "\nComplete configuration data for perl $]:\n\n";
577 foreach (sort keys %::Config) {
578 $value = $::Config{$_};
580 print OUT "$_='$value'\n";
592 Please make sure that the name of the editor you want to use is correct.
595 print "Editor [$ed]: ";
597 my($entry) =scalar(<>);
606 if(!$usefile and !$body) {
607 my $sts = system("$ed $filename");
609 #print "\nUnable to run editor!\n";
612 The editor you chose (`$ed') could apparently not be run!
613 Did you mistype the name of your editor? If so, please
614 correct it here, otherwise just press Enter.
617 print "Editor [$ed]: ";
619 my($entry) =scalar(<>);
629 You may want to save your report to a file, so you can edit and mail it
637 # Check that we have a report that has some, eh, report in it.
641 open(REP, "<$filename");
642 # a strange way to check whether any significant editing
643 # have been done: check whether any new non-empty lines
644 # have been added. Yes, the below code ignores *any* space
648 $unseen++ if ($_ ne '' and not exists $REP{$_});
651 while ($unseen == 0) {
654 I am sorry but it looks like you did not report anything.
657 print "Action (Retry Edit/Cancel) ";
658 my ($action) = scalar(<>);
659 if ($action =~ /^[re]/i) { # <R>etry <E>dit
661 } elsif ($action =~ /^[cq]/i) { # <C>ancel, <Q>uit
669 1 while unlink($filename); # remove all versions under VMS
670 print "\nCancelling.\n";
676 # Report is done, prompt for further action
683 Now that you have completed your report, would you like to send
684 the message to $address$andcc, display the message on
685 the screen, re-edit it, or cancel without sending anything?
686 You may also save the message as a file to mail at another time.
690 print "Action (Send/Display/Edit/Cancel/Save to File): ";
691 my($action) = scalar(<>);
694 if( $action =~ /^(f|sa)/i ) { # <F>ile/<Sa>ve
695 print "\n\nName of file to save message in [perlbug.rep]: ";
696 my($file) = scalar(<>);
698 if($file eq "") { $file = "perlbug.rep" }
701 open(REP,"<$filename");
702 print FILE "To: $address\nSubject: $subject\n";
703 print FILE "Cc: $cc\n" if $cc;
704 print FILE "Reply-To: $from\n" if $from;
706 while(<REP>) { print FILE }
710 print "\nMessage saved in `$file'.\n";
713 } elsif( $action =~ /^(d|l|sh)/i ) { # <D>isplay, <L>ist, <Sh>ow
714 # Display the message
715 open(REP,"<$filename");
716 while(<REP>) { print $_ }
718 } elsif( $action =~ /^se/i ) { # <S>end
721 Are you certain you want to send this message?
722 Please type \"yes\" if you are: ";
723 my($reply) = scalar(<STDIN>);
725 if( $reply eq "yes" ) {
730 That wasn't a clear "yes", so I won't send your message. If you are sure
731 your message should be sent, type in "yes" (without the quotes) at the
737 } elsif( $action =~ /^[er]/i ) { # <E>dit, <R>e-edit
740 #system("$ed $filename");
741 } elsif( $action =~ /^[qc]/i ) { # <C>ancel, <Q>uit
743 } elsif( $action =~ /^s/ ) {
746 I'm sorry, but I didn't understand that. Please type "send" or "save".
757 # Message has been accepted for transmission -- Send the message
761 $msg = new Mail::Send Subject => $subject, To => $address;
763 $msg->cc($cc) if $cc;
764 $msg->add("Reply-To",$from) if $from;
768 open(REP,"<$filename");
769 while(<REP>) { print $fh $_ }
774 print "\nMessage sent.\n";
777 if ( ($address =~ /@/ and $address !~ /^\w+%"/) or
778 ($cc =~ /@/ and $cc !~ /^\w+%"/) ){
780 foreach (qw[ IN MX SMTP UCX PONY WINS ],'') {
781 $prefix = "$_%",last if $ENV{"MAIL\$PROTOCOL_$_"};
783 $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/;
784 $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/;
786 $subject =~ s/"/""/g; $address =~ s/"/""/g; $cc =~ s/"/""/g;
787 my($sts) = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]);
788 if ($sts) { die "Can't spawn off mail\n\t(leaving bug report in $filename): $sts\n;" }
792 foreach (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail))
794 $sendmail = $_, last if -e $_;
797 if ($^O eq 'os2' and $sendmail eq "") {
798 my $path = $ENV{PATH};
800 my @path = split /$Config{path_sep}/, $path;
802 $sendmail = "$_/sendmail", last
804 $sendmail = "$_/sendmail.exe", last
805 if -e "$_/sendmail.exe";
809 paraprint(<<"EOF"), die "\n" if $sendmail eq "";
811 I am terribly sorry, but I cannot find sendmail, or a close equivalent, and
812 the perl package Mail::Send has not been installed, so I can't send your bug
813 report. We apologize for the inconvenience.
815 So you may attempt to find some way of sending your message, it has
816 been left in the file `$filename'.
820 open(SENDMAIL,"|$sendmail -t") || die "'|$sendmail -t' failed: $|";
821 print SENDMAIL "To: $address\n";
822 print SENDMAIL "Subject: $subject\n";
823 print SENDMAIL "Cc: $cc\n" if $cc;
824 print SENDMAIL "Reply-To: $from\n" if $from;
825 print SENDMAIL "\n\n";
826 open(REP,"<$filename");
827 while(<REP>) { print SENDMAIL $_ }
830 if (close(SENDMAIL)) {
831 print "\nMessage sent.\n";
833 warn "\nSendmail returned status '",$?>>8,"'\n";
839 1 while unlink($filename); # remove all versions under VMS
846 A program to help generate bug reports about perl5, and mail them.
847 It is designed to be used interactively. Normally no arguments will
851 $0 [-v] [-a address] [-s subject] [-b body | -f file ]
852 [-r returnaddress] [-e editor] [-c adminaddress | -C] [-S] [-t] [-h]
854 Simplest usage: run "$0", and follow the prompts.
858 -v Include Verbose configuration data in the report
859 -f File containing the body of the report. Use this to
860 quickly send a prepared message.
861 -S Send without asking for confirmation.
862 -a Address to send the report to. Defaults to `$address'.
863 -c Address to send copy of report to. Defaults to `$cc'.
864 -C Don't send copy to administrator.
865 -s Subject to include with the message. You will be prompted
866 if you don't supply one on the command line.
867 -b Body of the report. If not included on the command line, or
868 in a file with -f, you will get a chance to edit the message.
869 -r Your return address. The program will ask you to confirm
870 this if you don't give it here.
872 -t Test mode. The target address defaults to `$testaddress'.
873 -d Data mode (the default if you redirect or pipe output.)
874 This prints out your configuration data, without mailing
875 anything. You can use this with -v to get more complete data.
876 -ok Report successful build on this system to perl porters
877 (use alone or with -v).
878 -okay As -ok but also report on older systems.
879 -h Print this help message.
885 my @paragraphs = split /\n{2,}/, "@_";
887 for (@paragraphs) { # implicit local $_
897 ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
905 perlbug - how to submit bug reports on Perl
909 B<perlbug> S<[ B<-v> ]> S<[ B<-a> I<address> ]> S<[ B<-s> I<subject> ]>
910 S<[ B<-b> I<body> | B<-f> I<file> ]> S<[ B<-r> I<returnaddress> ]>
911 S<[ B<-e> I<editor> ]> S<[ B<-c> I<adminaddress> | B<-C> ]>
912 S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-h> ]>
914 B<perlbug> S<[ B<-v> ]> S<[ B<-r> I<returnaddress> ]> S<[ B<-ok> | B<okay> ]>
918 A program to help generate bug reports about perl or the modules that
919 come with it, and mail them.
921 If you have found a bug with a non-standard port (one that was not part
922 of the I<standard distribution>), a binary distribution, or a
923 non-standard module (such as Tk, CGI, etc), then please see the
924 documentation that came with that distribution to determine the correct
925 place to report bugs.
927 C<perlbug> is designed to be used interactively. Normally no arguments
928 will be needed. Simply run it, and follow the prompts.
930 If you are unable to run B<perlbug> (most likely because you don't have
931 a working setup to send mail that perlbug recognizes), you may have to
932 compose your own report, and email it to B<perlbug@perl.com>. You might
933 find the B<-d> option useful to get summary information in that case.
935 In any case, when reporting a bug, please make sure you have run through
940 =item What version of perl you are running?
942 Type C<perl -v> at the command line to find out.
944 =item Are you running the latest released version of perl?
946 Look at http://www.perl.com/ to find out. If it is not the latest
947 released version, get that one and see whether your bug has been
948 fixed. Note that bug reports about old versions of perl, especially
949 those prior to the 5.0 release, are likely to fall upon deaf ears.
950 You are on your own if you continue to use perl1 .. perl4.
952 =item Are you sure what you have is a bug?
954 A significant number of the bug reports we get turn out to be documented
955 features in perl. Make sure the behavior you are witnessing doesn't fall
956 under that category, by glancing through the documentation that comes
957 with perl (we'll admit this is no mean task, given the sheer volume of
958 it all, but at least have a look at the sections that I<seem> relevant).
960 Be aware of the familiar traps that perl programmers of various hues
961 fall into. See L<perltrap>.
963 Try to study the problem under the perl debugger, if necessary.
966 =item Do you have a proper test case?
968 The easier it is to reproduce your bug, the more likely it will be
969 fixed, because if no one can duplicate the problem, no one can fix it.
970 A good test case has most of these attributes: fewest possible number
971 of lines; few dependencies on external commands, modules, or
972 libraries; runs on most platforms unimpeded; and is self-documenting.
974 A good test case is almost always a good candidate to be on the perl
975 test suite. If you have the time, consider making your test case so
976 that it will readily fit into the standard test suite.
978 =item Can you describe the bug in plain English?
980 The easier it is to understand a reproducible bug, the more likely it
981 will be fixed. Anything you can provide by way of insight into the
982 problem helps a great deal. In other words, try to analyse the
983 problem to the extent you feel qualified and report your discoveries.
985 =item Can you fix the bug yourself?
987 A bug report which I<includes a patch to fix it> will almost
988 definitely be fixed. Use the C<diff> program to generate your patches
989 (C<diff> is being maintained by the GNU folks as part of the B<diffutils>
990 package, so you should be able to get it from any of the GNU software
991 repositories). If you do submit a patch, the cool-dude counter at
992 perlbug@perl.com will register you as a savior of the world. Your
993 patch may be returned with requests for changes, or requests for more
994 detailed explanations about your fix.
996 Here are some clues for creating quality patches: Use the B<-c> or
997 B<-u> switches to the diff program (to create a so-called context or
998 unified diff). Make sure the patch is not reversed (the first
999 argument to diff is typically the original file, the second argument
1000 your changed file). Make sure you test your patch by applying it with
1001 the C<patch> program before you send it on its way. Try to follow the
1002 same style as the code you are trying to patch. Make sure your patch
1003 really does work (C<make test>, if the thing you're patching supports
1006 =item Can you use C<perlbug> to submit the report?
1008 B<perlbug> will, amongst other things, ensure your report includes
1009 crucial information about your version of perl. If C<perlbug> is unable
1010 to mail your report after you have typed it in, you may have to compose
1011 the message yourself, add the output produced by C<perlbug -d> and email
1012 it to B<perlbug@perl.com>. If, for some reason, you cannot run
1013 C<perlbug> at all on your system, be sure to include the entire output
1014 produced by running C<perl -V> (note the uppercase V).
1018 Having done your bit, please be prepared to wait, to be told the bug
1019 is in your code, or even to get no reply at all. The perl maintainers
1020 are busy folks, so if your problem is a small one or if it is difficult
1021 to understand or already known, they may not respond with a personal reply.
1022 If it is important to you that your bug be fixed, do monitor the
1023 C<Changes> file in any development releases since the time you submitted
1024 the bug, and encourage the maintainers with kind words (but never any
1025 flames!). Feel free to resend your bug report if the next released
1026 version of perl comes out and your bug is still present.
1034 Address to send the report to. Defaults to `perlbug@perl.com'.
1038 Body of the report. If not included on the command line, or
1039 in a file with B<-f>, you will get a chance to edit the message.
1043 Don't send copy to administrator.
1047 Address to send copy of report to. Defaults to the address of the
1048 local perl administrator (recorded when perl was built).
1052 Data mode (the default if you redirect or pipe output). This prints out
1053 your configuration data, without mailing anything. You can use this
1054 with B<-v> to get more complete data.
1062 File containing the body of the report. Use this to quickly send a
1067 Prints a brief summary of the options.
1071 Report successful build on this system to perl porters. Forces B<-S>
1072 and B<-C>. Forces and supplies values for B<-s> and B<-b>. Only
1073 prompts for a return address if it cannot guess it (for use with
1074 B<make>). Honors return address specified with B<-r>. You can use this
1075 with B<-v> to get more complete data. Only makes a report if this
1076 system is less than 60 days old.
1080 As B<-ok> except it will report on older systems.
1084 Your return address. The program will ask you to confirm its default
1085 if you don't use this option.
1089 Send without asking for confirmation.
1093 Subject to include with the message. You will be prompted if you don't
1094 supply one on the command line.
1098 Test mode. The target address defaults to `perlbug-test@perl.com'.
1102 Include verbose configuration data in the report.
1108 Kenneth Albanowski (E<lt>kjahds@kjahds.comE<gt>), subsequently I<doc>tored
1109 by Gurusamy Sarathy (E<lt>gsar@umich.eduE<gt>), Tom Christiansen
1110 (E<lt>tchrist@perl.comE<gt>), Nathan Torkington (E<lt>gnat@frii.comE<gt>),
1111 Charles F. Randall (E<lt>cfr@pobox.comE<gt>) and
1112 Mike Guy (E<lt>mjtg@cam.a.ukE<gt>).
1116 perl(1), perldebug(1), perltrap(1), diff(1), patch(1)
1120 None known (guess what must have been used to report them?)
1126 close OUT or die "Can't close $file: $!";
1127 chmod 0755, $file or die "Can't reset permissions for $file: $!\n";
1128 exec("$Config{'eunicefix'} $file") if $Config{'eunicefix'} ne ':';