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; }
119 Please use perlbug interactively. If you want to
120 include a file, you can use the -f switch.
125 if($::opt_d or !-t STDOUT) { Dump(*STDOUT); exit; }
128 Edit() unless $usefile;
136 # -------- Setup --------
138 $Is_MSWin32 = $^O eq 'MSWin32';
139 $Is_VMS = $^O eq 'VMS';
141 getopts("dhva:s:b:f:r:e:SCc:to:");
144 # This comment is needed to notify metaconfig that we are
145 # using the $perladmin, $cf_by, and $cf_time definitions.
148 # -------- Configuration ---------
151 $perlbug = 'perlbug@perl.com';
155 $testaddress = 'perlbug-test@perl.com';
158 $address = $::opt_a || ($::opt_t ? $testaddress : $perlbug);
160 # Users address, used in message and in Reply-To header
161 $from = $::opt_r || "";
163 # Include verbose configuration information
164 $verbose = $::opt_v || 0;
166 # Subject of bug-report message
167 $subject = $::opt_s || "";
170 $usefile = ($::opt_f || 0);
172 # File to send as report
173 $file = $::opt_f || "";
176 $body = $::opt_b || "";
179 $ed = ( $::opt_e || $ENV{VISUAL} || $ENV{EDITOR} || $ENV{EDIT} ||
180 ($Is_VMS ? "edit/tpu" : $Is_MSWin32 ? "notepad" : "vi")
183 # OK - send "OK" report for build on this system
186 if ( $::opt_o eq 'k' or $::opt_o eq 'kay' ) {
187 my $age = time - $patchlevel_date;
188 if ( $::opt_o eq 'k' and $age > 60 * 24 * 60 * 60 ) {
189 my $date = localtime $patchlevel_date;
191 \"perlbug -ok\" does not report on Perl versions which are more than
192 60 days old. This Perl version was constructed on $date.
193 If you really want to report this, use \"perlbug -okay\".
197 # force these options
198 $::opt_S = 1; # don't prompt for send
199 $::opt_C = 1; # don't send a copy to the local admin
201 $subject = "OK: perl $] on"
202 ." $::Config{'osname'} $::Config{'osvers'} $subject";
204 $body = "Perl reported to build OK on this system.\n";
213 # Possible administrator addresses, in order of confidence
214 # (Note that cf_email is not mentioned to metaconfig, since
215 # we don't really want it. We'll just take it if we have to.)
217 # This has to be after the $ok stuff above because of the way
218 # that $::opt_C is forced.
219 $cc = ($::opt_C ? "" : (
220 $::opt_c || $::Config{perladmin} || $::Config{cf_email} || $::Config{cf_by}
227 ? $ENV{'USER'} || $ENV{'LOGNAME'}
228 : eval { getpwuid($<) }) ); # May be missing
235 # Explain what perlbug is
238 This program provides an easy way to create a message reporting a bug
239 in perl, and e-mail it to $address. It is *NOT* intended for
240 sending test messages or simply verifying that perl works, *NOR* is it
241 intended for reporting bugs in third-party perl modules. It is *ONLY*
242 a means of reporting verifiable problems with the core perl distribution,
243 and any solutions to such problems, to the people who maintain perl.
245 If you're just looking for help with perl, try posting to the Usenet
246 newsgroup comp.lang.perl.misc. If you're looking for help with using
247 perl with CGI, try posting to comp.infosystems.www.programming.cgi.
253 # Prompt for subject of message, if needed
256 First of all, please provide a subject for the
257 message. It should be a concise description of
258 the bug or problem. "perl bug" or "perl problem"
259 is not a concise description.
268 while( $subject =~ /^\s*$/ ) {
269 print "\nPlease enter a subject: ";
279 # Prompt for return address, if needed
282 # Try and guess return address
286 $domain = Mail::Util::maildomain();
287 } elsif ($Is_MSWin32) {
288 $domain = $ENV{'USERDOMAIN'};
290 require Sys::Hostname;
291 $domain = Sys::Hostname::hostname();
293 $domain = `hostname`.".".`domainname`;
294 $domain =~ s/[\r\n]+//g;
301 } elsif ($Is_VMS && !$::Config{'d_socket'}) {
302 $guess = "$domain\:\:$me";
304 $guess = "$me\@$domain" if $domain;
305 $guess = "$me\@unknown.addresss" unless $domain;
308 $guess = $ENV{'REPLYTO'} if defined($ENV{'REPLYTO'});
309 $guess = $ENV{"REPLY-TO"} if defined($ENV{'REPLY-TO'});
316 Your e-mail address will be useful if you need to be contacted. If the
317 default shown is not your full internet e-mail address, please correct it.
324 So that you may be contacted if necessary, please enter
325 your full internet e-mail address here.
330 if ( $ok && $guess ne '' ) {
336 print "Your address [$guess]: ";
341 if($from eq "") { $from = $guess }
346 #if( $from =~ /^(.*)\@(.*)$/ ) {
351 if( $from eq $cc or $me eq $cc ) {
352 # Try not to copy ourselves
357 # Prompt for administrator address, unless an override was given
358 if( !$::opt_C and !$::opt_c ) {
362 A copy of this report can be sent to your local
363 perl administrator. If the address is wrong, please
364 correct it, or enter 'none' or 'yourself' to not send
369 print "Local perl administrator [$cc]: ";
371 my($entry) = scalar(<>);
376 if($me eq $cc) { $cc = "" }
381 if($cc =~ /^(none|yourself|me|myself|ourselves)$/i) { $cc = "" }
383 $andcc = " and $cc" if $cc;
387 # Prompt for editor, if no override is given
388 if(! $::opt_e and ! $::opt_f and ! $::opt_b) {
392 Now you need to supply the bug report. Try to make
393 the report concise but descriptive. Include any
394 relevant detail. If you are reporting something
395 that does not work as you think it should, please
396 try to include example of both the actual
397 result, and what you expected.
399 Some information about your local
400 perl configuration will automatically be included
401 at the end of the report. If you are using any
402 unusual version of perl, please try and confirm
403 exactly which versions are relevant.
405 You will probably want to use an editor to enter
406 the report. If "$ed" is the editor you want
407 to use, then just press Enter, otherwise type in
408 the name of the editor you would like to use.
410 If you would like to use a prepared file, type
411 "file", and you will be asked for the filename.
415 print "Editor [$ed]: ";
417 my($entry) =scalar(<>);
421 if($entry eq "file") {
423 } elsif($entry ne "") {
429 # Generate scratch file to edit report in
432 my($dir) = ($Is_VMS ? 'sys$scratch:' :
433 (($Is_MSWin32 && $ENV{'TEMP'}) ? $ENV{'TEMP'} : '/tmp/'));
434 $filename = "bugrep0$$";
435 $dir .= "\\" if $Is_MSWin32 and $dir !~ m|[\\/]$|;
436 $filename++ while -e "$dir$filename";
437 $filename = "$dir$filename";
441 # Prompt for file to read report from, if needed
443 if( $usefile and ! $file) {
447 What is the name of the file that contains your report?
453 my($entry) = scalar(<>);
459 No filename? I'll let you go back and choose an editor again.
465 if(!-f $entry or !-r $entry) {
468 I'm sorry, but I can't read from `$entry'. Maybe you mistyped the name of
469 the file? If you don't want to send a file, just enter a blank line and you
470 can get back to the editor selection.
482 open(REP,">$filename");
484 my $reptype = $ok ? "success" : "bug";
487 This is a $reptype report for perl from $from,
488 generated with the help of perlbug $Version running under perl $].
495 open(F,"<$file") or die "Unable to read report file from `$file': $!\n";
503 -----------------------------------------------------------------
504 [Please enter your report here]
508 [Please do not change anything below this line]
509 -----------------------------------------------------------------
516 # read in the report template once so that
517 # we can track whether the user does any editing.
518 # yes, *all* whitespace is ignored.
519 open(REP, "<$filename");
534 Site configuration information for perl $]:
538 if( $::Config{cf_by} and $::Config{cf_time}) {
539 print OUT "Configured by $::Config{cf_by} at $::Config{cf_time}.\n\n";
542 print OUT Config::myconfig;
545 print OUT join "\n\t", "\nLocally applied patches:", @patches;
561 Environment for perl $]:
564 (qw(PATH LD_LIBRARY_PATH
567 grep { /^(?:PERL|LC_)/ } keys %ENV)) {
569 exists $ENV{$env} ? "=$ENV{$env}" : ' (unset)',
573 print OUT "\nComplete configuration data for perl $]:\n\n";
575 foreach (sort keys %::Config) {
576 $value = $::Config{$_};
578 print OUT "$_='$value'\n";
590 Please make sure that the name of the editor you want to use is correct.
593 print "Editor [$ed]: ";
595 my($entry) =scalar(<>);
604 if(!$usefile and !$body) {
605 my $sts = system("$ed $filename");
607 #print "\nUnable to run editor!\n";
610 The editor you chose (`$ed') could apparently not be run!
611 Did you mistype the name of your editor? If so, please
612 correct it here, otherwise just press Enter.
615 print "Editor [$ed]: ";
617 my($entry) =scalar(<>);
627 You may want to save your report to a file, so you can edit and mail it
635 # Check that we have a report that has some, eh, report in it.
639 open(REP, "<$filename");
640 # a strange way to check whether any significant editing
641 # have been done: check whether any new non-empty lines
642 # have been added. Yes, the below code ignores *any* space
646 $unseen++ if ($_ ne '' and not exists $REP{$_});
649 while ($unseen == 0) {
652 I am sorry but it looks like you did not report anything.
655 print "Action (Retry Edit/Cancel) ";
656 my ($action) = scalar(<>);
657 if ($action =~ /^[re]/i) { # <R>etry <E>dit
659 } elsif ($action =~ /^[cq]/i) { # <C>ancel, <Q>uit
667 1 while unlink($filename); # remove all versions under VMS
668 print "\nCancelling.\n";
674 # Report is done, prompt for further action
681 Now that you have completed your report, would you like to send
682 the message to $address$andcc, display the message on
683 the screen, re-edit it, or cancel without sending anything?
684 You may also save the message as a file to mail at another time.
688 print "Action (Send/Display/Edit/Cancel/Save to File): ";
689 my($action) = scalar(<>);
692 if( $action =~ /^(f|sa)/i ) { # <F>ile/<Sa>ve
693 print "\n\nName of file to save message in [perlbug.rep]: ";
694 my($file) = scalar(<>);
696 if($file eq "") { $file = "perlbug.rep" }
699 open(REP,"<$filename");
700 print FILE "To: $address\nSubject: $subject\n";
701 print FILE "Cc: $cc\n" if $cc;
702 print FILE "Reply-To: $from\n" if $from;
704 while(<REP>) { print FILE }
708 print "\nMessage saved in `$file'.\n";
711 } elsif( $action =~ /^(d|l|sh)/i ) { # <D>isplay, <L>ist, <Sh>ow
712 # Display the message
713 open(REP,"<$filename");
714 while(<REP>) { print $_ }
716 } elsif( $action =~ /^se/i ) { # <S>end
719 Are you certain you want to send this message?
720 Please type \"yes\" if you are: ";
721 my($reply) = scalar(<STDIN>);
723 if( $reply eq "yes" ) {
728 That wasn't a clear "yes", so I won't send your message. If you are sure
729 your message should be sent, type in "yes" (without the quotes) at the
735 } elsif( $action =~ /^[er]/i ) { # <E>dit, <R>e-edit
738 #system("$ed $filename");
739 } elsif( $action =~ /^[qc]/i ) { # <C>ancel, <Q>uit
741 } elsif( $action =~ /^s/ ) {
744 I'm sorry, but I didn't understand that. Please type "send" or "save".
755 # Message has been accepted for transmission -- Send the message
759 $msg = new Mail::Send Subject => $subject, To => $address;
761 $msg->cc($cc) if $cc;
762 $msg->add("Reply-To",$from) if $from;
766 open(REP,"<$filename");
767 while(<REP>) { print $fh $_ }
772 print "\nMessage sent.\n";
775 if ( ($address =~ /@/ and $address !~ /^\w+%"/) or
776 ($cc =~ /@/ and $cc !~ /^\w+%"/) ){
778 foreach (qw[ IN MX SMTP UCX PONY WINS ],'') {
779 $prefix = "$_%",last if $ENV{"MAIL\$PROTOCOL_$_"};
781 $address = qq[${prefix}"$address"] unless $address =~ /^\w+%"/;
782 $cc = qq[${prefix}"$cc"] unless !$cc || $cc =~ /^\w+%"/;
784 $subject =~ s/"/""/g; $address =~ s/"/""/g; $cc =~ s/"/""/g;
785 my($sts) = system(qq[mail/Subject="$subject" $filename. "$address","$cc"]);
786 if ($sts) { die "Can't spawn off mail\n\t(leaving bug report in $filename): $sts\n;" }
790 foreach (qw(/usr/lib/sendmail /usr/sbin/sendmail /usr/ucblib/sendmail))
792 $sendmail = $_, last if -e $_;
795 if ($^O eq 'os2' and $sendmail eq "") {
796 my $path = $ENV{PATH};
798 my @path = split /$Config{path_sep}/, $path;
800 $sendmail = "$_/sendmail", last
802 $sendmail = "$_/sendmail.exe", last
803 if -e "$_/sendmail.exe";
807 paraprint(<<"EOF"), die "\n" if $sendmail eq "";
809 I am terribly sorry, but I cannot find sendmail, or a close equivalent, and
810 the perl package Mail::Send has not been installed, so I can't send your bug
811 report. We apologize for the inconvenience.
813 So you may attempt to find some way of sending your message, it has
814 been left in the file `$filename'.
818 open(SENDMAIL,"|$sendmail -t") || die "'|$sendmail -t' failed: $|";
819 print SENDMAIL "To: $address\n";
820 print SENDMAIL "Subject: $subject\n";
821 print SENDMAIL "Cc: $cc\n" if $cc;
822 print SENDMAIL "Reply-To: $from\n" if $from;
823 print SENDMAIL "\n\n";
824 open(REP,"<$filename");
825 while(<REP>) { print SENDMAIL $_ }
828 if (close(SENDMAIL)) {
829 print "\nMessage sent.\n";
831 warn "\nSendmail returned status '",$?>>8,"'\n";
837 1 while unlink($filename); # remove all versions under VMS
844 A program to help generate bug reports about perl5, and mail them.
845 It is designed to be used interactively. Normally no arguments will
849 $0 [-v] [-a address] [-s subject] [-b body | -f file ]
850 [-r returnaddress] [-e editor] [-c adminaddress | -C] [-S] [-t] [-h]
852 Simplest usage: run "$0", and follow the prompts.
856 -v Include Verbose configuration data in the report
857 -f File containing the body of the report. Use this to
858 quickly send a prepared message.
859 -S Send without asking for confirmation.
860 -a Address to send the report to. Defaults to `$address'.
861 -c Address to send copy of report to. Defaults to `$cc'.
862 -C Don't send copy to administrator.
863 -s Subject to include with the message. You will be prompted
864 if you don't supply one on the command line.
865 -b Body of the report. If not included on the command line, or
866 in a file with -f, you will get a chance to edit the message.
867 -r Your return address. The program will ask you to confirm
868 this if you don't give it here.
870 -t Test mode. The target address defaults to `$testaddress'.
871 -d Data mode (the default if you redirect or pipe output.)
872 This prints out your configuration data, without mailing
873 anything. You can use this with -v to get more complete data.
874 -ok Report successful build on this system to perl porters
875 (use alone or with -v).
876 -okay As -ok but also report on older systems.
877 -h Print this help message.
883 my @paragraphs = split /\n{2,}/, "@_";
885 for (@paragraphs) { # implicit local $_
895 ^<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< ~~
903 perlbug - how to submit bug reports on Perl
907 B<perlbug> S<[ B<-v> ]> S<[ B<-a> I<address> ]> S<[ B<-s> I<subject> ]>
908 S<[ B<-b> I<body> | B<-f> I<file> ]> S<[ B<-r> I<returnaddress> ]>
909 S<[ B<-e> I<editor> ]> S<[ B<-c> I<adminaddress> | B<-C> ]>
910 S<[ B<-S> ]> S<[ B<-t> ]> S<[ B<-d> ]> S<[ B<-h> ]>
912 B<perlbug> S<[ B<-v> ]> S<[ B<-r> I<returnaddress> ]> S<[ B<-ok> | B<okay> ]>
916 A program to help generate bug reports about perl or the modules that
917 come with it, and mail them.
919 If you have found a bug with a non-standard port (one that was not part
920 of the I<standard distribution>), a binary distribution, or a
921 non-standard module (such as Tk, CGI, etc), then please see the
922 documentation that came with that distribution to determine the correct
923 place to report bugs.
925 C<perlbug> is designed to be used interactively. Normally no arguments
926 will be needed. Simply run it, and follow the prompts.
928 If you are unable to run B<perlbug> (most likely because you don't have
929 a working setup to send mail that perlbug recognizes), you may have to
930 compose your own report, and email it to B<perlbug@perl.com>. You might
931 find the B<-d> option useful to get summary information in that case.
933 In any case, when reporting a bug, please make sure you have run through
938 =item What version of perl you are running?
940 Type C<perl -v> at the command line to find out.
942 =item Are you running the latest released version of perl?
944 Look at http://www.perl.com/ to find out. If it is not the latest
945 released version, get that one and see whether your bug has been
946 fixed. Note that bug reports about old versions of perl, especially
947 those prior to the 5.0 release, are likely to fall upon deaf ears.
948 You are on your own if you continue to use perl1 .. perl4.
950 =item Are you sure what you have is a bug?
952 A significant number of the bug reports we get turn out to be documented
953 features in perl. Make sure the behavior you are witnessing doesn't fall
954 under that category, by glancing through the documentation that comes
955 with perl (we'll admit this is no mean task, given the sheer volume of
956 it all, but at least have a look at the sections that I<seem> relevant).
958 Be aware of the familiar traps that perl programmers of various hues
959 fall into. See L<perltrap>.
961 Try to study the problem under the perl debugger, if necessary.
964 =item Do you have a proper test case?
966 The easier it is to reproduce your bug, the more likely it will be
967 fixed, because if no one can duplicate the problem, no one can fix it.
968 A good test case has most of these attributes: fewest possible number
969 of lines; few dependencies on external commands, modules, or
970 libraries; runs on most platforms unimpeded; and is self-documenting.
972 A good test case is almost always a good candidate to be on the perl
973 test suite. If you have the time, consider making your test case so
974 that it will readily fit into the standard test suite.
976 =item Can you describe the bug in plain English?
978 The easier it is to understand a reproducible bug, the more likely it
979 will be fixed. Anything you can provide by way of insight into the
980 problem helps a great deal. In other words, try to analyse the
981 problem to the extent you feel qualified and report your discoveries.
983 =item Can you fix the bug yourself?
985 A bug report which I<includes a patch to fix it> will almost
986 definitely be fixed. Use the C<diff> program to generate your patches
987 (C<diff> is being maintained by the GNU folks as part of the B<diffutils>
988 package, so you should be able to get it from any of the GNU software
989 repositories). If you do submit a patch, the cool-dude counter at
990 perlbug@perl.com will register you as a savior of the world. Your
991 patch may be returned with requests for changes, or requests for more
992 detailed explanations about your fix.
994 Here are some clues for creating quality patches: Use the B<-c> or
995 B<-u> switches to the diff program (to create a so-called context or
996 unified diff). Make sure the patch is not reversed (the first
997 argument to diff is typically the original file, the second argument
998 your changed file). Make sure you test your patch by applying it with
999 the C<patch> program before you send it on its way. Try to follow the
1000 same style as the code you are trying to patch. Make sure your patch
1001 really does work (C<make test>, if the thing you're patching supports
1004 =item Can you use C<perlbug> to submit the report?
1006 B<perlbug> will, amongst other things, ensure your report includes
1007 crucial information about your version of perl. If C<perlbug> is unable
1008 to mail your report after you have typed it in, you may have to compose
1009 the message yourself, add the output produced by C<perlbug -d> and email
1010 it to B<perlbug@perl.com>. If, for some reason, you cannot run
1011 C<perlbug> at all on your system, be sure to include the entire output
1012 produced by running C<perl -V> (note the uppercase V).
1016 Having done your bit, please be prepared to wait, to be told the bug
1017 is in your code, or even to get no reply at all. The perl maintainers
1018 are busy folks, so if your problem is a small one or if it is difficult
1019 to understand or already known, they may not respond with a personal reply.
1020 If it is important to you that your bug be fixed, do monitor the
1021 C<Changes> file in any development releases since the time you submitted
1022 the bug, and encourage the maintainers with kind words (but never any
1023 flames!). Feel free to resend your bug report if the next released
1024 version of perl comes out and your bug is still present.
1032 Address to send the report to. Defaults to `perlbug@perl.com'.
1036 Body of the report. If not included on the command line, or
1037 in a file with B<-f>, you will get a chance to edit the message.
1041 Don't send copy to administrator.
1045 Address to send copy of report to. Defaults to the address of the
1046 local perl administrator (recorded when perl was built).
1050 Data mode (the default if you redirect or pipe output). This prints out
1051 your configuration data, without mailing anything. You can use this
1052 with B<-v> to get more complete data.
1060 File containing the body of the report. Use this to quickly send a
1065 Prints a brief summary of the options.
1069 Report successful build on this system to perl porters. Forces B<-S>
1070 and B<-C>. Forces and supplies values for B<-s> and B<-b>. Only
1071 prompts for a return address if it cannot guess it (for use with
1072 B<make>). Honors return address specified with B<-r>. You can use this
1073 with B<-v> to get more complete data. Only makes a report if this
1074 system is less than 60 days old.
1078 As B<-ok> except it will report on older systems.
1082 Your return address. The program will ask you to confirm its default
1083 if you don't use this option.
1087 Send without asking for confirmation.
1091 Subject to include with the message. You will be prompted if you don't
1092 supply one on the command line.
1096 Test mode. The target address defaults to `perlbug-test@perl.com'.
1100 Include verbose configuration data in the report.
1106 Kenneth Albanowski (E<lt>kjahds@kjahds.comE<gt>), subsequently I<doc>tored
1107 by Gurusamy Sarathy (E<lt>gsar@umich.eduE<gt>), Tom Christiansen
1108 (E<lt>tchrist@perl.comE<gt>), Nathan Torkington (E<lt>gnat@frii.comE<gt>),
1109 Charles F. Randall (E<lt>cfr@pobox.comE<gt>) and
1110 Mike Guy (E<lt>mjtg@cam.a.ukE<gt>).
1114 perl(1), perldebug(1), perltrap(1), diff(1), patch(1)
1118 None known (guess what must have been used to report them?)
1124 close OUT or die "Can't close $file: $!";
1125 chmod 0755, $file or die "Can't reset permissions for $file: $!\n";
1126 exec("$Config{'eunicefix'} $file") if $Config{'eunicefix'} ne ':';