zsh-workers
 help / color / mirror / code / Atom feed
From: "Ken Moorley" <kmoorley@cms.aust.com>
To: <zsh-workers@sunsite.dk>
Subject: RE: Help with compile problem
Date: Wed, 13 Feb 2002 11:48:47 +1100	[thread overview]
Message-ID: <005101c1b428$31d7c3c0$450000c0@cms.aust.com> (raw)
In-Reply-To: <Pine.BSF.4.40.0202122237320.98397-100000@brasslantern.com>

I successfully installed GNU gawk and sed but get the same result!

I was able to compile zsh 4.0.4 using gcc 2.9.5.2, is there any thing
uniquie about 3.0.3 that would cause the problem although gawk and sed
compiled OK with gcc 3.0.3


Ken

> -----Original Message-----
> From: lantern@brasslantern.com [mailto:lantern@brasslantern.com]On
> Behalf Of Bart Schaefer
> Sent: Wednesday, 13 February 2002 9:47 am
> To: Ken Moorley
> Subject: RE: Help with compile problem
>
>
> On Wed, 13 Feb 2002, Ken Moorley wrote:
>
> > Tried from scratch, tried make distclean all with the same result!
>
> What we (please send to zsh-workers@sunsite.dk, not just to me; I don't
> have a SCO system but someone else might) need to see is the "make" output
> from that clean build.  Some things were obviously not getting rebuilt
> before, but it's hard to tell why during what may be an incremental
> compilation.
>
> A possible cause of the problem is that configure is finding nawk as the
> awk-equivalent on your system; it might be mishandling the awk scripts
> that are used to construct some of the Makefiles.  It'd be best if you
> could get GNU awk (or make sure it's first in your $PATH if you already
> have it).
>
> It's also possible that your sed is not working the way the zsh Makefiles
> expect.
>


       reply	other threads:[~2002-02-13  0:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.BSF.4.40.0202122237320.98397-100000@brasslantern.com>
2002-02-13  0:48 ` Ken Moorley [this message]
2002-02-13 22:35 ` Ken Moorley
2002-02-13 23:58   ` Bart Schaefer
2002-02-14  0:13     ` Ken Moorley
2002-02-14  0:19       ` Bart Schaefer
2002-02-14  1:44         ` Ken Moorley

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='005101c1b428$31d7c3c0$450000c0@cms.aust.com' \
    --to=kmoorley@cms.aust.com \
    --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).