From: Chavdar Ivanov <ci@delcam.com>
To: Matthew Lovell <lovell@fc.hp.com>
Cc: "Zsh User's List" <zsh-users@math.gatech.edu>
Subject: Re: Help with compiling 3.1.4 on HPUX 10.20
Date: Sat, 22 Aug 1998 07:00:56 -0400 (EDT) [thread overview]
Message-ID: <Pine.HPX.4.02.9808220653070.1559-100000@marge> (raw)
In-Reply-To: <13789.43827.684548.946200@hatchet.fc.hp.com>
On Fri, 21 Aug 1998, Matthew Lovell wrote:
> Hi,
>
> I grabbed zsh-3.1.4 earlier today and have tried compiling under both
> gcc and HP's ansic. I seem to have some header problem, but I'm at
> somewhat of a loss.
>
> I would appreciated any help/advice you could offer.
>
> cc: "watch.c", line 130: error 1588: "ut_xtime" undefined.
> cc: "watch.c", line 130: error 1531: Invalid member of struct or union.
> cc: "watch.c", line 144: error 1531: Invalid member of struct or union.
> cc: "watch.c", line 144: error 1563: Expression in if must be scalar.
> cc: "watch.c", line 158: error 1531: Invalid member of struct or union.
> cc: "watch.c", line 417: error 1588: "ut_xtime" undefined.
> cc: "watch.c", line 417: error 1531: Invalid member of struct or union.
> cc: "watch.c", line 417: error 1531: Invalid member of struct or union.
> cc: "watch.c", line 417: error 1563: Expression in if must be scalar.
> cc: "watch.c", line 419: error 1531: Invalid member of struct or union.
> cc: "watch.c", line 419: error 1531: Invalid member of struct or union.
>
> Thanks!
>
> --
>
> Matthew Lovell voice: (970) 898-6264
> Hewlett-Packard FSL fax: (970) 898-2510
> 3404 E. Harmony Rd. MS A0 location: 3UR4
> Fort Collins, CO 80528-9599 mailto:lovell@fc.hp.com
>
>
I had this a few months ago when I first got 3.1.4 compiled under HP-UX
10.20; I do not remember what did I do at the time; I suspect I just used
gcc instead of HP cc ; I don't quite managed to grasp the sequence of
#if's and #defines just before the redefinition of ut_time as ut_xtime;
however, brute
#undef REAL_UTMPX_FILE
before
#if !defined(WATCH_STRUCT_UTMP) && defined(REAL_UTMPX_FILE) &&
defined(HAVE_STRUCT_UTMPX)
sorted the problem for me. ( I haven't tested the functionality provided
by this part of the shell, though; it seems to work OK. )
Also I can't fathom why when I compiled zsh-3.1.4 today for this test both
with gcc 2.8.1 and cc, I got over 700k stripped executables, while on the
1st of June my executable was just 548k...
-------------------------that's my version of the compiler-----------
marge# what /usr/bin/cc
/tmp/zsh-3.1.4/Src
/usr/bin/cc:
LINT A.10.32.16 CXREF A.10.32.16
HP92453-01 A.10.32.17 HP C Compiler
/usr/lib/libc: $Revision: 76.3 $
--------------------------------------------------------------------
Regards,
Chavdar Ivanov | Talbot Way, Small Heath Business Park
Delcam UK Limited | Birmingham B10 0HJ, United Kingdom
Customer Support Dept. | (+44)121-6831014
prev parent reply other threads:[~1998-08-22 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-08-21 17:15 Matthew Lovell
1998-08-22 11:00 ` Chavdar Ivanov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.HPX.4.02.9808220653070.1559-100000@marge \
--to=ci@delcam.com \
--cc=lovell@fc.hp.com \
--cc=zsh-users@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).