zsh-workers
 help / color / mirror / code / Atom feed
From: Borsenkow Andrej <Andrej.Borsenkow@mow.siemens.ru>
To: travis@jedi.net
Cc: zsh-workers@sunsite.dk
Subject: Re: Compile errors for zsh 4.0.4 on Aix  4.3.3
Date: 09 May 2002 19:05:35 +0400	[thread overview]
Message-ID: <1020956741.26762.12.camel@localhost.localdomain> (raw)
In-Reply-To: <20020509090819.A10978@yoda.jedi.net>


В Чтв, 09.05.2002, в 18:08, travis@jedi.net написал:
> The Etc/MACHINES file said you want more info on this error.
> Here it is.  I have attached two of the relevant files.
> Please let me know if you need more.
> 
> make[3]: Entering directory `/home/travis/aixbin/zsh-4.0.4/Src/Modules'
> cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o parameter.o parameter.c
> echo '' parameter.o | sed 's" " Modules/"g' >> ../../Src/stamp-modobjs.tmp
> cc -qlanglvl=ansi -c -I.  -DHAVE_CONFIG_H -O  -o termcap.o termcap.c
> "termcap.c", line 71.13: 1506-334 (S) Identifier boolcodes has already been defined on line 1342 of "/usr/include/term.h".
>

Thank you for feedback but unfortunately it is not the info that helps.
It appears exactly the problem as mentioned in Etc/MACHINES - when
configure tests for boolcodes & Co it does not find them  (because they
are missing in library or at least not exported) so it decides to use
local versions. And this clashes with declaration in term.h. What was
meant was some hint how to detect this condition.

Proper way to fix it would be

- use something like _zsh_boolcodes internally
- check for both declaration and availablility
- on well-behaving systems simply do #define _zsh_boolcodes boolcodes
- on bad systems leave _zsh_boolcodes as local definition.

Unfortunately (proper) test for declaration is missing in autoconf 2.13
and honestly speaking I am reluctant to backport it from autoconf 2.5x.
If anybody feels like doing it - he is welcome.

And I know that current 4.0 maintainer is reluctant to forget 2.13
compatibility :-)

-andrej

_PLEASE_ next time when you send 1000+ lines to list at least compress
them. Much better is first ask if this is really needed.


  parent reply	other threads:[~2002-05-09 15:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-09 14:08 travis
2002-05-09 15:03 ` Bart Schaefer
2002-05-09 15:05 ` Borsenkow Andrej [this message]
2002-05-09 15:31   ` Borsenkow Andrej
2002-05-09 15:45     ` Borsenkow Andrej
2002-05-09 15:56     ` Bart Schaefer
2002-05-09 15:08 ` Bart Schaefer
2002-05-09 15:17   ` Borsenkow Andrej
2002-05-10 23:01   ` Albert Chin

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=1020956741.26762.12.camel@localhost.localdomain \
    --to=andrej.borsenkow@mow.siemens.ru \
    --cc=travis@jedi.net \
    --cc=zsh-workers@sunsite.dk \
    /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).