zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: ams104@york.ac.uk (Alan Stephenson), zsh-workers@math.gatech.edu
Subject: Re: Building zsh-3.0.0 SGI IRIX 5.3
Date: Mon, 14 Oct 1996 03:01:41 -0700	[thread overview]
Message-ID: <961014030142.ZM2470@candle.brasslantern.com> (raw)
In-Reply-To: ams104@york.ac.uk (Alan Stephenson) "Building zsh-3.0.0 SGI IRIX 5.3" (Oct 14, 10:02am)

On Oct 14, 10:02am, Alan Stephenson wrote:
} Subject: Building zsh-3.0.0 SGI IRIX 5.3
}
} Probably something silly, but:
} 
}   The configure script supplied is determined to think I'm
} cross-compiling. Even if I persuade it I'm not, by hacking the script,
} the following occurs during the operation of `make':
} 
} ...
}         sed -n -f ./makepro.sed zle_utils.c > zle_utils.pro
}         sed -n -f ./makepro.sed zle_vi.c > zle_vi.pro
}         sed -n -f ./makepro.sed zle_word.c > zle_word.pro
}         nawk -f ./signames.awk /usr/include/sys/signal.h > signames.h
}         gcc -c -I.. -I. -I.  -DHAVE_CONFIG_H (-xansi -rdata_shared -p0
} -g0 -s -O2 -32) ansi2knr.c
} UX:sh (sh): ERROR: sh: Syntax error at line 1: `(' unexpected
} *** Error code 2 (bu21)
} *** Error code 1 (bu21)
} 
}   Not really sure what's going on here. Should the gcc line have the
} brackets?

Multiple questions arise.

Why is ansi2knr.c being compiled?  Both gcc and the IRIX C compiler are
ansi, so configure should NOT think K&R conversion is needed.

Why are the IRIX 5.3 native C compiler options -xansi -rdata_shared etc.
being passed to gcc?  *Nothing* about configure should have worked with
that combination.

} I've done the `reporter' thing, too. Hope you can help me.

Normally "reporter" would only help debug a problem with zsh itself, not
with the build process, but in this case it actually sheds some light.

What the heck is this stuff doing in your environment?

[...]
} CFLAGS="\'(-xansi -rdata_shared -p0 -g0 -s -O2 -32)\'"
} CPP="/lib/cpp"
[...]
} export CFLAGS
} export CPP
[...]

The parens in your failed build are coming from that CFLAGS environment
variable, which it looks as though you attempted to create as an array
(with parens around the value); but arrays aren't exported in zsh, so
somehow or other you got the parens into the value itself instead.

Or something; I'm gussing wildly here.

Get those out of your environment.  They'll screw up every compile you
attempt, zsh or anything else.  If there's an option to IRIX's `make'
to tell it to NOT import variables from the environment when processing
makefiles, start using it habitually.

unset CFLAGS
unset CPP
rm config.cache
configure
make


-- 
Bart Schaefer                             Brass Lantern Enterprises
http://www.well.com/user/barts            http://www.nbn.com/people/lantern

New male in /home/schaefer:
>N  2 Justin William Schaefer  Sat May 11 03:43  53/4040  "Happy Birthday"


  parent reply	other threads:[~1996-10-14 10:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-14  9:02 Alan Stephenson
1996-10-14  9:24 ` Peter Stephenson
1996-10-14  9:52   ` Hrvoje Niksic
1996-10-14 15:29   ` Richard Coleman
1996-10-14 10:01 ` Bart Schaefer [this message]
1996-10-14 10:07   ` Hrvoje Niksic
1996-10-14  9:33 Alan Stephenson

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=961014030142.ZM2470@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=ams104@york.ac.uk \
    --cc=schaefer@nbn.com \
    --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).