FSUM this error code
FSUM7351 :
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZA8C0/SPTWQ919
FSUM3228 :
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/BPXZA8C0/SPTOB63317
It turns out that the variable ($ccflags) is not disclosed and transmitted in
the form of direct
Can show in logs what string to take the test c99 ?
Option is supported by the compiler xlc (c99).
-g Generates information for debugging tools. The
information is produced in DWARF format.
------------------------------------------------------------------------
Yaroslav Kuzmin
Developer C/C++ ,z/OS , Linux
3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia
Tel: +7.922.2.38.33.38
Email: [email protected]
Web: www.rocketsoftware.com
________________________________________
От: Craig A. Berry <[email protected]>
Отправлено: 10 декабря 2014 г. 23:37
Кому: Karl Williamson
Копия: Yaroslav Kuzmin; Perl5 Porters; perl-mvs; H.Merijn Brand
Тема: Re: Smoke [ebcdic] v5.21.6-568-ga9f7116 FAIL(Xc) os/390 23.00 (2817/)
On Wed, Dec 10, 2014 at 11:52 AM, Karl Williamson
<[email protected]> wrote:
> We still have the problem of the smoke not running DEBUGGING. Below is
> extracted from the log file Yaroslav posted. I searched for the FSUM error
> codes online, and found no extra detail beyond the text in the accompanying
> messages.
>
> Configuration: -Dusedevel -DDEBUGGING
> ------------------------------------------------------------------------------
> make distclean ...
> Copy Policy.sh ...
> Configure ...FSUM3228 c99: Input file $ccflags not found.
> gcc: ./trygcc 25: .: ./Configure 4518: FSUM7351 not found
> FSUM3228 c99: Input file $ccflags not found.
> Unable to configure perl in this configuration
> Finished smoking a9f71162e1a364b73a353378b8b0a5ab95a462ae
> v5.21.6-568-ga9f7116 ebcdic
I don't think the FSUM details would tell you much (not that I even
know what FSUM is). It's determined that it can't use your C compiler
and is trying to figure out whether it can use gcc instead. Search
for "trygcc" in Configure. The basic problem is why it now thinks
(with -DDEBUGGING) that the C compiler won't work. The only thing I
can think of is that -DDEBUGGING also modifies the optimization flags
and whatever it adds (-g for example) may not be compatible with this
compiler.
================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■
+1 800.966.3270 ■ +1 781.577.4321
Unsubscribe From Commercial Email – [email protected]
Manage Your Subscription Preferences -
http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html
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.
