public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: Fodor Bertalan <fodber@freemail.hu>
Cc: cygwin@cygwin.com
Subject: RE: Strange make [Error 255] (cygwin bug?)
Date: Wed, 24 Sep 2003 19:47:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0309241541210.8775@slinky.cs.nyu.edu> (raw)
In-Reply-To: <000801c382bb$22016d80$8006fea9@bertigep>

On Wed, 24 Sep 2003, Fodor Bertalan wrote:

> > It's possible your $SHELL or $PATH is set to something weird in make.
> > Error 255 usually means that a command was not found.
>
> I don't think so. This long line is not the first command. The others work
> perfectly.
> $SHELL is set to /bin/sh -- you can see it.
> $PATH is also set to a normal value
>
> Bert

I meant the values of $PATH and $SHELL *inside* make.

Try inserting the following before that command:

	@(echo $$SHELL && echo $$PATH)

and see what it prints.

Also, what is MAKE_MODE set to in your environment?  What version of make
are you using?  What version of Cygwin?  Please attach (as an uncompressed
text *attachment*) the output of "cygcheck -svr" to your message, as
suggested in <http://cygwin.com/problems.html> -- it will contain all the
above information.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  parent reply	other threads:[~2003-09-24 19:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24  9:45 Fodor Bertalan
2003-09-24 18:27 ` Igor Pechtchanski
2003-09-24 18:10   ` Fodor Bertalan
2003-09-24 18:12     ` Fodor Bertalan
2003-09-24 19:47     ` Igor Pechtchanski [this message]
     [not found] <000b01c382de$67fb2a10$8006fea9@bertigep>
2003-09-24 21:20 ` Igor Pechtchanski
2003-09-24 22:05   ` Fodor Bertalan
2003-09-24 22:18     ` Igor Pechtchanski
2003-09-25  7:30       ` Fodor Bertalan
2003-09-25 12:46         ` Igor Pechtchanski
2003-09-25 13:12           ` Corinna Vinschen
2003-09-25 13:40             ` Igor Pechtchanski
2003-09-25 13:41               ` Corinna Vinschen
2003-09-25 13:54                 ` Christopher Faylor
2003-09-25 15:50                   ` Bertalan Fodor
2003-09-26  8:54                     ` Corinna Vinschen
2003-09-26 15:28                       ` Christopher Faylor
2003-09-26 18:02                         ` Corinna Vinschen
2003-09-27 14:05                           ` Jan Nieuwenhuizen
2003-09-27 16:11                             ` Christopher Faylor
2003-09-26  8:38                   ` Jan Nieuwenhuizen
2003-09-26  8:48                     ` Corinna Vinschen
2003-09-26 15:27                       ` Christopher Faylor

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.GSO.4.56.0309241541210.8775@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin@cygwin.com \
    --cc=fodber@freemail.hu \
    /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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).