zsh-users
 help / color / mirror / code / Atom feed
From: Stefan Berglund <sbl@dd.chalmers.se>
To: zsh Users <zsh-users@math.gatech.edu>
Subject: Re: Problem compiling on Sun SPARC 5
Date: Mon, 31 Jan 2000 23:40:42 +0100	[thread overview]
Message-ID: <20000131234042.A8335@dd.chalmers.se> (raw)
In-Reply-To: <000401bf6c36$26f6b740$450000c0@ken-moorley>; from kmoorley@cms.aust.com on Tue, Feb 01, 2000 at 08:57:22AM +1100

On Tue, Feb 01, 2000 at 08:57:22AM +1100, Ken Moorley wrote:
> Can anyone help with the following compile error:-
> 
> Solaris 2.6 on SPARCstation 5
> 
> gcc version 2.7.2.3

A tad old...
These problems _might_ come from that the compiler is built with a
older version of the OS. I have seen strange things with old gcc and
newer versions of Solaris than it was built with.

gcc is up at version 2.95.2 so it is time to upgrade anyway ;)
If you don't want to build from source visit www.sunfreeware.com and
grab a prebuilt solaris-package.

> gcc -c -I. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DHAVE_CONFIG_H -Wall 
> -Wno-implicit -Wmissing-prototypes -O2  -o builtin.o builtin.c
> In file included from /usr/include/sys/wait.h:24,
>                  from system.h:232,
>                  from zsh.mdh:6,
>                  from builtin.c:30:
> /usr/include/sys/resource.h:148: warning: `struct rlimit64' declared inside
> parameter list
> /usr/include/sys/resource.h:148: warning: its scope is only this definition
> or declaration,
> /usr/include/sys/resource.h:148: warning: which is probably not what you
> want.
> /usr/include/sys/resource.h:149: warning: `struct rlimit64' declared inside
> parameter list

I looked at this include file and I don't see any problems with it
unless struct rlimit64 is never declared. That might happen if
_LARGEFILE64_SOURCE isn't defined as it should be and that
_FILE_OFFSET_BITS is defined to 64.
If this is the case the first encounter of struct rlimit64 is inside
the prototypes at line 148 and 149 which makes the warnings 
understandable.
This is probably not your real problem anyway.

> builtin.c: In function `bin_cd':
> builtin.c:714: invalid operands to binary !=

This is where it chokes, the rest is just warnings. It complains about
that != haven't got valid operands, that is something that returns a
value. This implies a bug/typo in the source, but I find that unlikely
as most people here is probably compiling the same sources with gcc so
it should have surfaced earlier.
Look at line 714 in builtin.c and see if you can see what it's trying
to do.
BTW. which version did you try to compile? 

-- 
Stefan Berglund                       | sbl@dd.chalmers.se
System Administrator @dd.chalmers.se  | Tel: +46 31 772 32 43
Chalmers University of Technology, Engineering Physics
------------------------------------
Life - the ultimate practical joke |   pgp key available from keyservers


  reply	other threads:[~2000-01-31 22:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-31 21:57 Ken Moorley
2000-01-31 22:40 ` Stefan Berglund [this message]
2000-02-01 11:21 ` Alexandre Duret-Lutz

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=20000131234042.A8335@dd.chalmers.se \
    --to=sbl@dd.chalmers.se \
    --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).