zsh-workers
 help / color / mirror / code / Atom feed
From: Rob.Hooft@EMBL-Heidelberg.de
To: Zoltan Hidvegi <hzoli@cs.elte.hu>
Cc: Rob.Hooft@stork.EMBL-Heidelberg.DE, zsh-workers@math.gatech.edu
Subject: Re: DEC Unix 3.2d / 3.0pre6
Date: Mon, 12 Aug 1996 09:32:10 +0200 (MET DST)	[thread overview]
Message-ID: <199608120732.JAA08809@nu> (raw)
In-Reply-To: <199608120404.GAA10280@hzoli.ppp.cs.elte.hu>

>>>>> "ZH" == Zoltan Hidvegi <hzoli@cs.elte.hu> writes:

 >> So it seems under DU4.0 even gcc doesn't need the ioctl prototype
 >> in prototypes.h.  Removing the section at lines 104--110 in
 >> prototypes.h creates a working binary. I'm not sure how to detect
 >> this situation, so I'm in no position to generate a patch.

 ZH> Unfortunately I do not have access to DEC Unix 4.x so I cannot
 ZH> write such a test without some help.  The simplest solution would
 ZH> be a test for some predefined macro so that these prototypes are
 ZH> only defined for older DEC Unix versions.

Officially gcc-2.7.2 does not support DU4.0 yet, but I fear even if
the next version of gcc does officially support it, there will be no
differences in the predefined symbols. Certainly at this moment there
is no difference, nor is there any version-indication:

   nu[102]hooft% /nu1/hooft/lib/gcc-lib/alpha-dec-osf4.0/2.7.2.f.1/cpp -dM /dev/null
   #define SYSTYPE_BSD 1 
   #define _LONGLONG 1 
   #define __alpha__ 1 
   #define __osf__ 1 
   #define _SYSTYPE_BSD 1 
   #define __alpha 1 
   #define unix 1 

"uname -a" does the trick, but that is an ugly test...

   alpha1[101]hooft% uname -a
   OSF1 alpha1.embl-heidelberg.de V3.2 148 alpha
   nu[103]hooft% uname -a
   OSF1 nu.embl-heidelberg.de V4.0 386 alpha

Do you have any other hints?

-- 
=== Rob.Hooft@EMBL-Heidelberg.DE   http://www.Sander.EMBL-Heidelberg.DE/rob/ ==
==== In need of protein modeling?  http://www.Sander.EMBL-Heidelberg.DE/whatif/
Validation of protein structures?  http://biotech.EMBL-Heidelberg.DE:8400/ ====
== PGPid 0xFA19277D == Use Linux!  Free Software Rules The World! =============


      reply	other threads:[~1996-08-12  7:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-08-05 17:12 Rob.Hooft
1996-08-12  4:04 ` Zoltan Hidvegi
1996-08-12  7:32   ` Rob.Hooft [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=199608120732.JAA08809@nu \
    --to=rob.hooft@embl-heidelberg.de \
    --cc=Rob.Hooft@stork.EMBL-Heidelberg.DE \
    --cc=hzoli@cs.elte.hu \
    --cc=zsh-workers@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).