bug-ncurses
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Building ncurses on z/OS


From: Thomas Dickey
Subject: Re: [PATCH] Building ncurses on z/OS
Date: Sat, 31 Oct 2020 16:02:43 -0400
User-agent: NeoMutt/20170113 (1.7.2)

On Fri, Oct 30, 2020 at 03:16:56PM -0500, Steven Pitman wrote:
> Hi,
> 
> As you mentioned for 3), which was for misc/run_tic.in, this change is not 
> actually needed. Please ignore.

The basic problem with (2), ifdef'ing sgtty.h, is that the configure
script failed on most of the termios checks because the -Qunused-arguments
flag was still in that version of the configure script.
 
> > 2) ./include/MKterm.h.awk.in: The included header doesn't exist on z/OS, 
> 
> > so do not include it when compiling on this platform
> 
> ...but that branch of the ifdef would be used if the machine doesn't
> have termios (POSIX).  It would help if I had a copy of the config.status
> and config.log from configuring ncurses.

That causes the checks which compile and link a test program to fail:
--------------------------------------------------------------------------------
configure:8572: /home/pitman/ncurses/tools/compiler/xlclang -o conftest -qascii 
-qarch=10 -Qunused-arguments   conftest.c  >&5
FSUM3212 xlclang: Command option -Q is incorrect for z/OS platform - ignored.
 IEW2456E 9207 SYMBOL nused-arguments UNRESOLVED.  MEMBER COULD NOT BE INCLUDED 
          FROM THE DESIGNATED CALL LIBRARY.                                     
FSUM3065 The LINKEDIT step ended with return code 8.
configure:8575: $? = 3
configure: program exited with status 3
configure: failed program was:
#line 8558 "configure"
--------------------------------------------------------------------------------
In tonight's patch I have an improved check for clang's options which
should solve both (1) and (2).

-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]