Sorry , a lot of other work. I try running bisect.pl script But bisect.pl script finds not the correct configuration settings Not a valid compile gcc .
If I try manual running ./Configure -ds -Dusedevel -Dusedl All correct (11:22) RS12 : PDKUZM | ~/ussport/perl/perl-git :> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");' We are not bisecting. HEAD is now at 716a866437... Fix locale failures introduced 5 hours ago Can't exec "ccache": EDC5129I No such file or directory. at /tmp/YlJeWxnMCk line 886. (I see you are using the Korn shell. Some ksh's blow up on Configure, mainly on older exotic systems. If yours does, try the Bourne shell instead.) First let's make sure your kit is complete. Checking... Locating common programs... Checking compatibility between /bin/echo and builtin echo (if any)... Symbolic links are supported. Checking how to test for symbolic links... Your builtin 'test -h' may be broken. Trying external '/bin/test -h'. You can test for symbolic links with '/bin/test -h'. Checking for cross-compile No targethost for running compiler tests against defined, running locally Good, your tr supports [:lower:] and [:upper:] to convert case. Using [:upper:] and [:lower:] to convert case. aix esix4 lynxos sco_2_3_3 aix_3 fps midnightbsd sco_2_3_4 aix_4 freebsd mips solaris_2 altos486 freemint mirbsd stellar amigaos gnu mpc sunos_4_0 atheos gnukfreebsd ncr_tower sunos_4_1 aux_3 gnuknetbsd netbsd super-ux bitrig greenhills newsos4 svr4 bsdos haiku nonstopux svr5 catamount hpux openbsd ti1500 convexos i386 opus ultrix_4 cxux interix os2 umips cygwin irix_4 os390 unicos darwin irix_5 os400 unicosmk dcosx irix_6 posix-bc unisysdynix dec_osf irix_6_0 qnx utekv dos_djgpp irix_6_1 riscos uwin dragonfly isc sco vos dynix isc_2 sco_2_3_0 dynixptx linux-android sco_2_3_1 epix linux sco_2_3_2 Which of these apply, if any? [os390] Operating system name? [os390] Operating system version? [25.00] Installation prefix to use? (~name ok) [/usr/local] AFS does not seem to be running... What installation prefix should I use for installing files? (~name ok) [/usr/local] Getting the current patchlevel... Build a threading Perl? [n] Build Perl for multiplicity? [n] Use which C compiler? [cc] FSUM3007 -l is not a valid option. Uh-oh, the C compiler 'cc' doesn't seem to be working. gcc: ./trygcc 25: .: ./Configure 4553: FSUM7351 not found FSUM3007 -l is not a valid option. Uh-oh, the C compiler 'cc' doesn't seem to be working. You need to find a working C compiler. Either (purchase and) install the C compiler supplied by your OS vendor, or for a free C compiler try http://gcc.gnu.org/ I cannot continue any further, aborting. HEAD is now at 716a866437 Fix locale failures introduced 5 hours ago skipping - could not build config.sh at /tmp/YlJeWxnMCk line 1241. Runner returned 32000 for end revision, which is a skip at Porting/bisect.pl line 234. That took 20 seconds. В Ср., 18/04/2018 в 20:08 -0600, Karl Williamson пишет: On 04/17/2018 01:11 AM, Yaroslav Kuzmin wrote: Yes . I can actually reasonably bisect. Using the git for z/OS Ok. I have it set up in the branch smoke-me/khw-yaroslav That branch is different from blead because it changes the history so that things that cause EBCDIC not to compile were fixed up. Otherwise the bisect would keep finding compilation errors, and not work properly. To run the bisection do something like git clone ... bisect cd bisect git checkout smoke-me/khw-yaroslav /path/to/a/functioning/perl/Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");' This tool has never been run AFAIK on an EBCDIC machine. Let's cross our fingers that it works. If it works, after some length of time, it will print a result. To watch its progress, I pipe it to tee. above-command | tee ../bisect.out And then in another window, I do this tail -f bisect.out | grep steps I don't know how much of that will work on z/OS. It can be tricky (at least for me) to get the command exactly right. I tested the above-command on my machine (but I don't have the bug). If I screwed up and it says the end commit works, you can add the --expect-fail parameter. Or you can play around until it works. The file with the tool contains its pod ================================ Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll Free Number: +1 855.577.4323 Contact Customer Support: https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - http://www.rocketsoftware.com/manage-your-email-preferences Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy ================================ This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.