zsh-workers
 help / color / mirror / code / Atom feed
From: Cosmo <cosmo@informix.com>
To: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: NCR compiler problems on NCR
Date: Wed, 11 Oct 2000 11:52:11 +0100	[thread overview]
Message-ID: <39E4465B.72D01FEB@informix.com> (raw)
In-Reply-To: <002f01c0329f$4026fe20$21c9ca95@mow.siemens.ru>

Andrej Borsenkow wrote:

> Better yet is a configure check that compiler can cast long long to int. As
> long as you are the only person who can reproduce it - would you mind to write
> a patch? Or at least would you take time to check if it works?

OK here's a patch that causes configure to not use long long with my broken NCR
compiler. Now ./configure works straight out of the box on this machine.

*** zsh/aczsh.m4-orig	Wed Sep  6 16:50:16 2000
--- zsh/aczsh.m4	Wed Oct 11 11:27:18 2000
***************
*** 84,89 ****
--- 84,90 ----
  dnl   Sets the variable given in the second argument to the first argument
  dnl   if the test worked, `no' otherwise.  Be careful testing this, as it
  dnl   may produce two words `long long' on an unquoted substitution.
+ dnl   Also check that the compiler does not mind it being cast to int.
  dnl   This macro does not produce messages as it may be run several times
  dnl   before finding the right type.
  dnl
***************
*** 97,102 ****
--- 98,104 ----
  main()
  {
    $1 foo = 0;
+   int bar = (int) foo;
    return sizeof($1) != 8;
  }
  ], $2="$1", $2=no,


  parent reply	other threads:[~2000-10-11 10:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-09 15:41 Cosmo
2000-10-09 16:26 ` Andrej Borsenkow
2000-10-10  9:36   ` Cosmo
2000-10-10  9:48     ` Andrej Borsenkow
2000-10-11  8:55       ` PATCH: " Andrej Borsenkow
2000-10-11 10:52       ` Cosmo [this message]
2000-10-11 12:27         ` Andrej Borsenkow

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=39E4465B.72D01FEB@informix.com \
    --to=cosmo@informix.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --cc=zsh-workers@sunsite.auc.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).