Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Re: Smoke [blead] v5.27.10-119-g5f6af817ad FAIL(XM) os/390 25.00 (2964/)
8 views
Skip to first unread message
Karl Williamson
Apr 13, 2018, 1:15:02 AM4/13/18
to Yaroslav Kuzmin, perl...@perl.org, perl5-...@perl.org, daily-bui...@perl.org
On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
>
> Smoke log available at https://drive.google.com/file/d/1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ
>
> Automated smoke report for branch blead 5.27.11 patch 5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
> RS12: 2964 (2964/)
> on os/390 - 25.00
> using c99 version
> smoketime 2 hours (average 1 hour)
>
> Summary: FAIL(XM)
>
The easiest way to find this is to run a bisection on the month or so's
commits that could have caused this. Does your machine have enough
throughput that it could do this?
And that means compiling perl at a given commit that's bad, and then
cleaning the directory, and running it again at the last known good
commit. Then running it yet again at the commit half way between these
two. Then repeating on the half of the original range where it changed.
We have a tool that will automatically do this. You set it going, and
let it run until it finds the offending commit.
I haven't brought this up before, because I thought your hardware was
too slow for this. But this instance would be relatively few commits,
so that it might be feasible.
I would furnish you the correct incantation to get it to work, after
having tested it on my machine.
>
> Smoke log available at https://drive.google.com/file/d/1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ
>
> Automated smoke report for branch blead 5.27.11 patch 5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
> RS12: 2964 (2964/)
> on os/390 - 25.00
> using c99 version
> smoketime 2 hours (average 1 hour)
>
> Summary: FAIL(XM)
>
The easiest way to find this is to run a bisection on the month or so's
commits that could have caused this. Does your machine have enough
throughput that it could do this?
And that means compiling perl at a given commit that's bad, and then
cleaning the directory, and running it again at the last known good
commit. Then running it yet again at the commit half way between these
two. Then repeating on the half of the original range where it changed.
We have a tool that will automatically do this. You set it going, and
let it run until it finds the offending commit.
I haven't brought this up before, because I thought your hardware was
too slow for this. But this instance would be relatively few commits,
so that it might be feasible.
I would furnish you the correct incantation to get it to work, after
having tested it on my machine.
Karl Williamson
Apr 17, 2018, 12:15:02 AM4/17/18
to Yaroslav Kuzmin, perl...@perl.org, perl5-...@perl.org, daily-bui...@perl.org
On 04/16/2018 05:28 AM, Yaroslav Kuzmin wrote:
>
>
> В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:
> Мощность есть, немного ))
Actually, I'm not so sure. I believe one needs git to do this. I
looked at the git web site, and couldn't find any evidence that it was
supported on non-ASCII platforms.
>
>> And that means compiling perl at a given commit that's bad, and then
>> cleaning the directory, and running it again at the last known good
>> commit. Then running it yet again at the commit half way between these
>> two. Then repeating on the half of the original range where it changed.
>> We have a tool that will automatically do this. You set it going, and
>> let it run until it finds the offending commit.
>>
>> I haven't brought this up before, because I thought your hardware was
>> too slow for this. But this instance would be relatively few commits,
>> so that it might be feasible.
>>
>> I would furnish you the correct incantation to get it to work, after
>> having tested it on my machine.
>
> ================================
> 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.
>
>
>
> В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:
>> On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
>>> Smoke log available at
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608&sdata=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D&reserved=0
>>> Smoke log available at
>>> Automated smoke report for branch blead 5.27.11 patch
>>> 5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
>>> RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2
>>> hours (average 1 hour) Summary: FAIL(XM)
>>
>>
>> The easiest way to find this is to run a bisection on the month or so's
>> commits that could have caused this. Does your machine have enough
>> throughput that it could do this?
>
> Yes. It can be done
>>> 5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
>>> RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2
>>> hours (average 1 hour) Summary: FAIL(XM)
>>
>>
>> The easiest way to find this is to run a bisection on the month or so's
>> commits that could have caused this. Does your machine have enough
>> throughput that it could do this?
>
> Мощность есть, немного ))
Actually, I'm not so sure. I believe one needs git to do this. I
looked at the git web site, and couldn't find any evidence that it was
supported on non-ASCII platforms.
>
>> And that means compiling perl at a given commit that's bad, and then
>> cleaning the directory, and running it again at the last known good
>> commit. Then running it yet again at the commit half way between these
>> two. Then repeating on the half of the original range where it changed.
>> We have a tool that will automatically do this. You set it going, and
>> let it run until it finds the offending commit.
>>
>> I haven't brought this up before, because I thought your hardware was
>> too slow for this. But this instance would be relatively few commits,
>> so that it might be feasible.
>>
>> I would furnish you the correct incantation to get it to work, after
>> having tested it on my machine.
>
> 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.
>
Karl Williamson
Apr 17, 2018, 3:00:11 AM4/17/18
to Yaroslav Kuzmin, perl...@perl.org, perl5-...@perl.org, daily-bui...@perl.org
On 04/17/2018 12:33 AM, Yaroslav Kuzmin wrote:
>
>
> В Пн., 16/04/2018 в 22:05 -0600, Karl Williamson пишет:
>
> But I am build perl in a separate maint-5.24-zos branch.
I don't understand if that means you can or cannot actually reasonably
bisect
>
>>>> And that means compiling perl at a given commit that's bad, and then
>>>> cleaning the directory, and running it again at the last known good
>>>> commit. Then running it yet again at the commit half way between
>>>> these two. Then repeating on the half of the original range where it
>>>> changed. We have a tool that will automatically do this. You set it
>>>> going, and let it run until it finds the offending commit. I haven't
>>>> brought this up before, because I thought your hardware was too slow
>>>> for this. But this instance would be relatively few commits, so that
>>>> it might be feasible. I would furnish you the correct incantation to
>>>> get it to work, after having tested it on my machine.
>>> ================================ Rocket Software, Inc. and
>>> subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll
>>> Free Number: +1 855.577.4323 Contact Customer Support:
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupport&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201&sdata=0r9Pp%2B3pf4ubny%2Fn7cslkZDwY9yXwSsFdj%2BZfhL3d8k%3D&reserved=0
>>> Privacy Policy -
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fcompany%2Flegal%2Fprivacy-policy&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201&sdata=CBVES67q0tkvhJFG96yBMk8ckX15R6sNS2IZPAg9eVw%3D&reserved=0
>
>
> В Пн., 16/04/2018 в 22:05 -0600, Karl Williamson пишет:
>> On 04/16/2018 05:28 AM, Yaroslav Kuzmin wrote:
>>> В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:
>>>> On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
>>>>> Smoke log available at
>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608&sdata=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D&reserved=0
>>>>> Automated smoke report for branch blead 5.27.11 patch
>>>>> 5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
>>>>> RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2
>>>>> hours (average 1 hour) Summary: FAIL(XM)
>>>> The easiest way to find this is to run a bisection on the month or
>>>> so's commits that could have caused this. Does your machine have
>>>> enough throughput that it could do this?
>>> Yes. It can be done Мощность есть, немного ))
>>
>>
>> Actually, I'm not so sure. I believe one needs git to do this. I
>> looked at the git web site, and couldn't find any evidence that it was
>> supported on non-ASCII platforms.
>>
>
> So http://www.rocketsoftware.com/zos-open-source/tools
>>> В Чт., 12/04/2018 в 23:02 -0600, Karl Williamson пишет:
>>>> On 04/12/2018 03:51 AM, Yaroslav Kuzmin wrote:
>>>>> Smoke log available at
>>>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Ffile%2Fd%2F1XHUAwq74zUMfS3Ps3WnMAvpSagcXFWxJ&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7Cc0296a68ef694e27e64b08d5a0fbd140%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636591925776871608&sdata=zXZiEaKzoIYbct%2Faq1sWv%2FB6jO%2FxN59gWPyllO6wNC0%3D&reserved=0
>>>>> Automated smoke report for branch blead 5.27.11 patch
>>>>> 5f6af817add6d2df3603e0e94b6eb27ba5fb3970 v5.27.10-119-g5f6af817ad
>>>>> RS12: 2964 (2964/) on os/390 - 25.00 using c99 version smoketime 2
>>>>> hours (average 1 hour) Summary: FAIL(XM)
>>>> The easiest way to find this is to run a bisection on the month or
>>>> so's commits that could have caused this. Does your machine have
>>>> enough throughput that it could do this?
>>> Yes. It can be done Мощность есть, немного ))
>>
>>
>> Actually, I'm not so sure. I believe one needs git to do this. I
>> looked at the git web site, and couldn't find any evidence that it was
>> supported on non-ASCII platforms.
>>
>
>
> But I am build perl in a separate maint-5.24-zos branch.
I don't understand if that means you can or cannot actually reasonably
bisect
>
>>>> And that means compiling perl at a given commit that's bad, and then
>>>> cleaning the directory, and running it again at the last known good
>>>> commit. Then running it yet again at the commit half way between
>>>> these two. Then repeating on the half of the original range where it
>>>> changed. We have a tool that will automatically do this. You set it
>>>> going, and let it run until it finds the offending commit. I haven't
>>>> brought this up before, because I thought your hardware was too slow
>>>> for this. But this instance would be relatively few commits, so that
>>>> it might be feasible. I would furnish you the correct incantation to
>>>> get it to work, after having tested it on my machine.
>>> ================================ Rocket Software, Inc. and
>>> subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ Main Office Toll
>>> Free Number: +1 855.577.4323 Contact Customer Support:
>>> Unsubscribe from Marketing Messages/Manage Your Subscription
>>> Preferences -
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferences&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201&sdata=E6Kr%2FLKMSn2qgaVK%2B5Ztc27mNePx7%2BUMKUXvryWoRJQ%3D&reserved=0
>>> Preferences -
>>> Privacy Policy -
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fcompany%2Flegal%2Fprivacy-policy&data=02%7C01%7Cykuzmin%40rocketsoftware.com%7C5e94c4d590014d80281708d5a41889a7%7C79544c1eed224879a082b67a9a672aae%7C0%7C0%7C636595347668561201&sdata=CBVES67q0tkvhJFG96yBMk8ckX15R6sNS2IZPAg9eVw%3D&reserved=0
Karl Williamson
Apr 18, 2018, 10:15:02 PM4/18/18
to Yaroslav Kuzmin, perl...@perl.org, perl5-...@perl.org, daily-bui...@perl.org
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
> 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
Dave Mitchell
Apr 25, 2018, 8:00:02 AM4/25/18
to Yaroslav Kuzmin, perl...@perl.org, pub...@khwilliamson.com, perl5-...@perl.org, daily-bui...@perl.org
On Wed, Apr 25, 2018 at 11:31:13AM +0000, Yaroslav Kuzmin wrote:
> So . I try running bisect.pl
>
> (16:23) RS12 : PDKUZM | ~/ussport/perl/perl-git
> :> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");'
> This checkout is not clean, found file(s):
> .gitattributes
> 1 modified, untracked, or other file(s)
> These files may not show in git status as they may be ignored.
> Can't run a bisect using a dirty directory containing Porting/bisect-runner.pl.
> That took 1 seconds.
>
> I can not remove this file. This file is very important for the system z/OS
Can't you just move .gitattributes to $GIT_DIR/info/attributes
(or whatever the z/OS equivalent is)?
https://git-scm.com/docs/gitattributes
--
"You may not work around any technical limitations in the software"
-- Windows Vista license
> So . I try running bisect.pl
>
> (16:23) RS12 : PDKUZM | ~/ussport/perl/perl-git
> :> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit (uc("\x{587}") ne "\x{535}\x{552}");'
> This checkout is not clean, found file(s):
> .gitattributes
> 1 modified, untracked, or other file(s)
> These files may not show in git status as they may be ignored.
> Can't run a bisect using a dirty directory containing Porting/bisect-runner.pl.
> That took 1 seconds.
>
> I can not remove this file. This file is very important for the system z/OS
Can't you just move .gitattributes to $GIT_DIR/info/attributes
(or whatever the z/OS equivalent is)?
https://git-scm.com/docs/gitattributes
--
"You may not work around any technical limitations in the software"
-- Windows Vista license
Karl Williamson
May 11, 2018, 1:30:02 PM5/11/18
to Yaroslav Kuzmin, perl...@perl.org, perl5-...@perl.org, daily-bui...@perl.org
On 05/11/2018 12:29 AM, Yaroslav Kuzmin wrote:
> 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
We don't understand why the below is getting gcc. But you should be
able to avoid this by adding -Dcc=xlc to the bisect command line (or
whatever compiler you're using)
>
> (11:22) RS12 : PDKUZM | ~/ussport/perl/perl-git
> :> perl Porting/bisect.pl --start 3b6c52ce7d --end 716a866437e -e 'exit
> 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 пишет:
> 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
We don't understand why the below is getting gcc. But you should be
able to avoid this by adding -Dcc=xlc to the bisect command line (or
whatever compiler you're using)
>
> (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 пишет:
0 new messages