zsh-users
 help / color / mirror / code / Atom feed
From: Cosmo <cosmo@uk.ibm.com>
Cc: Zsh users list <zsh-users@sunsite.dk>
Subject: Re: 4.2.0-pre-3
Date: Fri, 05 Mar 2004 15:25:43 +0000	[thread overview]
Message-ID: <40489BF7.3020001@uk.ibm.com> (raw)
In-Reply-To: <20681.1078496403@csr.com>

Peter Stephenson wrote:
> 
> 
> 
> I've uploaded 4.2.0-pre-3 to ftp.zsh.org.
> 
> Used autoconf 2.59 to try to improve matters on HPUX.

Unfortunately my HPSUX 11.11 seems to have a broken /bin/sh and this
part of configure gets the wrong PATH_SEPARATOR.

# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
   echo "#! /bin/sh" >conf$$.sh
   echo  "exit 0"   >>conf$$.sh
   chmod +x conf$$.sh
   if (PATH="/nonexistent;."; conf$$.sh) >/dev/null 2>&1; then
     PATH_SEPARATOR=';'
   else
     PATH_SEPARATOR=:
   fi
:  rm -f conf$$.sh
fi

Once that is broken, it can't find awk... and other bad things
happen. Manually setting PATH_SEPARATOR=: then gives me a slew of:

checking sys/time.h usability... no
checking sys/time.h presence... yes
configure: WARNING: sys/time.h: present but cannot be compiled
configure: WARNING: sys/time.h:     check for missing prerequisite headers?
configure: WARNING: sys/time.h: see the Autoconf documentation
configure: WARNING: sys/time.h:     section "Present But Cannot Be Compiled"
configure: WARNING: sys/time.h: proceeding with the preprocessor's result
configure: WARNING: sys/time.h: in the future, the compiler will take precedence
configure: WARNING:     ## ------------------------------------------ ##
configure: WARNING:     ## Report this to the AC_PACKAGE_NAME lists.  ##
configure: WARNING:     ## ------------------------------------------ ##
checking for sys/time.h... yes

For a number of header files.

First compilation then fails with:

         gcc -c -I.  -DHAVE_CONFIG_H -Wall -Wmissing-prototypes -O2  -o builtin.o builtin.c
In file included from system.h:110,
                  from zsh.mdh:13,
                  from builtin.c:33:
/usr/local/lib/gcc-lib/hppa2.0n-hp-hpux11.11/3.1/include/stdio.h:607: parse error before 
"_hpux_size_t"
/usr/local/lib/gcc-lib/hppa2.0n-hp-hpux11.11/3.1/include/stdio.h:608: parse error before 
"_hpux_size_t"
In file included from /usr/include/strings.h:14,
                  from system.h:203,
                  from zsh.mdh:13,
                  from builtin.c:33:
/usr/local/lib/gcc-lib/hppa2.0n-hp-hpux11.11/3.1/include/string.h:263: parse error before 
"_hpux_size_t"
/usr/local/lib/gcc-lib/hppa2.0n-hp-hpux11.11/3.1/include/string.h:315: parse error before 
"_hpux_size_t"

I didn't build or install the gcc 3.1 that is on this machine - I'll try alternatives.







Cosmo



  reply	other threads:[~2004-03-05 15:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 14:20 4.2.0-pre-3 Peter Stephenson
2004-03-05 15:25 ` Cosmo [this message]
2004-03-05 16:55   ` 4.2.0-pre-3 Cosmo
     [not found] <1078507368.18583.34.camel@sonic>
2004-03-05 17:34 ` 4.2.0-pre-3 Peter Stephenson
2004-03-08  9:15   ` 4.2.0-pre-3 Ibraheem Umaru-Mohammed

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=40489BF7.3020001@uk.ibm.com \
    --to=cosmo@uk.ibm.com \
    --cc=zsh-users@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).