zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Ken Moorley <kmoorley@cms.aust.com>
Cc: zsh-workers@sunsite.dk
Subject: RE: Help with compile problem
Date: Wed, 13 Feb 2002 23:58:17 +0000 (GMT)	[thread overview]
Message-ID: <Pine.BSF.4.40.0202132315320.10405-100000@brasslantern.com> (raw)
In-Reply-To: <006601c1b4de$b19a3fa0$450000c0@cms.aust.com>

On Thu, 14 Feb 2002, Ken Moorley wrote:

> I was able to compile zsh 4.0.4 using gcc 2.9.5.2, is there any thing unique
> about 3.0.3 that would cause the problem
[...]
> I have attached the configure and make output text for both versions which
> might give some one a clue.

Diffing the make output, there are lines like this in the 3.1.9 build:

-gawk -f ../Src/makepro.awk builtin.c Src > builtin.syms
-(echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < builtin.syms) \
-       > builtin.epro
-(echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < builtin.syms) \
-       > `echo builtin.epro | sed 's/\.epro$/.pro/'`

Those lines are missing in the 4.0.4 build, and the build fails because
the files generated by those commands are not present.

Unfortunately, I have no idea why changing compilers would affect the make
dependencies, or otherwise cause make to fail to execute those commands.
What happens if you explicitly give the command

	cd Src; make builtin.syms

??


  reply	other threads:[~2002-02-13 23:58 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
2002-02-13 22:35 ` Ken Moorley
2002-02-13 23:58   ` Bart Schaefer [this message]
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=Pine.BSF.4.40.0202132315320.10405-100000@brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=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).