This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Strange make [Error 255] (cygwin bug?)


Bert,

Please keep discussions on the list, so they appear in the archives, where
other people can benefit from them.  Also, please make sure your mailer
honors the Reply-To: field.

More replies below.

On Wed, 24 Sep 2003, Fodor Bertalan wrote:

> Thank you for your advices.
>
> I was not really sure where to put this line, anyway I put it into
> config.make without the '@' as INSTALL = (echo $$SHELL && echo $$PATH) ;
> $(SHELL) $(stepdir)/../bin/install-dot-exe.sh -c
>
> Then the line with the error was executed as:
> ((echo $SHELL && echo $PATH) ; /bin/sh /netrel/src/lilypond-2.0.0-1/stepmake/stepmake/../bin/install-dot-exe.sh -c -d /netrel/inst/lilypond-2.0.0-1/usr/share/lilypond/2.0.0/tex/ || true) ...
>
> Is this correct?

Well, I meant something like

	@(echo $$SHELL && echo $$PATH)
	(/bin/sh /netrel/src/lilypond-2.0.0-1/stepmake/stepmake/../bin/install-dot-exe.sh -c -d /netrel/inst/lilypond-2.0.0-1/usr/share/lilypond/2.0.0/tex/ || true) ...

(you can lose the '@').  This way you'd know if make can run a subshell,
and what the values of the variables in that subshell are.  You could also
try to invoke the subshell as '/bin/sh -c "echo $$SHELL && echo $$PATH"'
(that would make it slighly less dependent on what $SHELL and $MAKE_MODE
are set to).

> But the line was just not run. The next line in the log is:
> make[2]: *** [local-install-outfiles] Error 255

Hmm.  You could try to add a "-x" flag to /bin/sh, to see exactly where it
breaks.  Another possibility is to break up the long line into multiple
lines in the makefile (at each &&, which is implied by the make semantics
anyway) -- perhaps it's some sort of buffer overflow in make.

BTW, does the Makefile have CR/LF line endings?  Is it on a text or binary
mount?

> In previous lines
> The SHELL looked like: /bin/sh
> The PATH looked like: /bin:/usr/local/bin:/netrel/bin:/lib:/bin:/usr/local/lib/qt2/bin:/opt/kde2/bin:/opt/kde2/lib:/usr/local/lib/qt2/bin:/usr/X11R6/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin:/cygdrive/c/imagemagick:/cygdrive/c/prog/perl/bin/:/cygdrive/c/texmf/miktex/bin/:/cygdrive/c/PROG/RATIONAL/RATION~1/NUTCROOT/mksnt:/cygdrive/c/WINDOWS/system32:/cygdrive/c/WINDOWS:/cygdrive/c/WINDOWS/System32/Wbem:/cygdrive/c/Prog/Rational/common:/cygdrive/c/Prog/Rational/Rose/TopLink/:/cygdrive/c/Prog/Rational/Rational Test:/cygdrive/c/Program Files/Unisys/RoseXMLTools:/cygdrive/c/prog/ATT/Graphviz/bin:/cygdrive/c/prog/ATT/Graphviz/bin/tools:/cygdrive/c/gs/gs7.00/bin:/cygdrive/c/gs/gs7.00/lib:/cygdrive/c/Program Files/Common Files/Roxio Shared/DLLShared:/cygdrive/c/Program Files/Common Files/GIS/Tools:/cygdrive/c/Prog/ObjectStudio/dllw32:/usr/X11R6/bin

I don't see anything wrong with that (nor with your cygcheck output), but
that's really why these messages should go to the list, where there's more
expertise, and perhaps someone will notice something I missed.
	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

Attachment: cygcheck.log
Description: Binary data

--
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/

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]