zsh-users
 help / color / mirror / code / Atom feed
From: "Juergen A. Erhard" <jae@laden.ilk.de>
To: sweth@bivwood.com
Cc: zsh-users@math.gatech.edu
Subject: Re: problems installing zsh on x86
Date: Thu, 10 Apr 1997 20:03:39 -0100	[thread overview]
Message-ID: <199704102103.UAA00300@Laden2.ilk.de> (raw)
In-Reply-To: <v03102001af6a6e9942d8@[168.143.9.115]> (message from Sweth Chandramouli on Fri, 4 Apr 1997 03:51:26 -0500)

-----BEGIN PGP SIGNED MESSAGE-----

It probably has been covered by someone else... but anyway. I'm
assuming the littlest possible working knowledge of Unix here...

All the others have (rightly) said you gotta make certain gcc is on
your PATH. Test this by just saying 'gcc --version' (that is, type
it... but you knew that, I guess ;-)

If it says anything to the effect that it (the currently running
shell) can't find gcc, then gcc is NOT in your path. Put a line

  PATH=/usr/local/bin:$PATH

in your ~/.profile. (Make sure /usr/local/bin is the directory
containing gcc... if it ain't replace it).

Okay, try again...

Oh, and first do a 'make clean' in the directory zsh's source resides
in (you may try this before doing this PATH dance... I noticed the run
of configure you've given is from cache... I am not an autoconf
expert, but it just MIGHT be the problem... especially if gcc IS on
your PATH already).

Anyway, hope I could help (and nobody beat me to it ;-)

Bye, J

- -- 
Juergen A. Erhard (that ue is actually \"u (TeX) or &uuml; (HTML/SGML))
eMail: jae@laden.ilk.de                             |
snailMail: Belfortstr. 6; 76133 Karlsruhe; GERMANY  |  pros do it for money,
phone: +49 721 27326                                |  amateurs out of love.
WWW: http://members.tripod.com/~Juergen_Erhard/     |

-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: noconv
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQEVAwUBM0w4NgIG66LugGzRAQH7sAf/SenhwXhrfHiBLnF2AFl5N4M5cJFmmDLv
0aIua+T3xTXDjfvIW+fxoSLDoQ8ejTWJhkoIJAi698CXSgizKf1XgFBFsgxU3l1h
wDP8V6hDmEOX6Sao8+/rRhBokUG/4vgGu4aeXqPBao0cg9W1pJVGDrBiYOWbeY8E
hbxBcoVVVNrdeQR4atdKfIn8tTIBpkaHvN0aYQPmmvMmch0gpRozDh1WOwhXaoTq
hA7Ck+UQ9ov3m4XLPPx+ncfCvhRo7RvJtKMEhZ6OJzA7KVtbuWNUud8hJAOktGbE
d8HAwMHguka9P1XHxKbGY0POhxA7ZgzrDw3tuwEi2fIsblPcEWm+5Q==
=odRR
-----END PGP SIGNATURE-----


  parent reply	other threads:[~1997-04-10 18:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-04  8:51 Sweth Chandramouli
1997-04-04 11:04 ` Chavdar Ivanov
1997-04-04 13:13   ` Hrvoje Niksic
1997-04-04 18:23     ` Stefan Monnier
1997-04-04 12:55 ` Hrvoje Niksic
1997-04-10 21:03 ` Juergen A. Erhard [this message]
1997-04-10 21:39   ` Sweth Chandramouli
1997-04-11 14:01     ` Zefram
1997-04-11 21:06       ` Sweth Chandramouli
1997-04-11 21:31         ` Zoltan T. Hidvegi

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=199704102103.UAA00300@Laden2.ilk.de \
    --to=jae@laden.ilk.de \
    --cc=sweth@bivwood.com \
    --cc=zsh-users@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).