From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1074 invoked from network); 27 Jun 2001 11:21:26 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 Jun 2001 11:21:26 -0000 Received: (qmail 16216 invoked by alias); 27 Jun 2001 11:20:26 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15116 Received: (qmail 16195 invoked from network); 27 Jun 2001 11:20:25 -0000 X-Envelope-Sender-Is: Andrej.Borsenkow@mow.siemens.ru (at relayer goliath.siemens.de) From: "Andrej Borsenkow" To: "Timo Aaltonen" Cc: "ZSH Workers Mailing List" Subject: AIX - almost success. Date: Wed, 27 Jun 2001 15:21:01 +0400 Message-ID: <002a01c0fefb$3efe3f30$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2479.0006 Importance: Normal > > > > > > I'm still interested if other problems are fixed. > > > > > > They seem to be, at least it compiled ok. I had to remove > both termcap and > > > terminfo. > > > > > > > what about make check? > > ./C02cond.ztst: starting. > Test ./C02cond.ztst failed: bad status 1, expected 0 from: > sleep 1 > cat unmodified > touch newnewnew > if [[ $OSTYPE == "cygwin" ]]; then > print -u8 "Warning: not testing [[ -N file ]] (not supported on > Cygwin)" > true > else > [[ -N newnewnew && ! -N unmodified ]] > fi > Was testing: -N cond > ./C02cond.ztst: test failed. > That's O.K., you are on NFS. > > all the rest went fine > Nice. Could you do a favour and try clean configure/make/make check with LIBS=-ltermcap configure ... This should work OOTB (by avoiding curses); of course, not with GCC as usual. > > > Gcc 2.8.1 specs-file attached, but I have been using cc... > > > > > > > If you can spend some more time, I'd be interested in making it more > > GCC-friendly. > > Ok, that's fine. > > > btw, I tried the same numcodes-test with other OS's (Tru64, linux), and > they both failed (unresolved symbol numcodes), but maybe that's for a > reason, as it isn't tested when configure is run normally.. > What's up? It definitely works on Linux, Sven, do you have numcodes, boolcodes etc on Tru64? Timo, could you post exact program, cc invocation and error messages you get on Linux and Tru64? -andrej