[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Problems with $(shell xxx) using uWin
From: |
James Kanze |
Subject: |
Problems with $(shell xxx) using uWin |
Date: |
Fri, 02 Jun 2006 22:47:02 +0200 |
User-agent: |
Thunderbird 1.5.0.4 (X11/20060516) |
I've recently installed (built from sources) a copy of GNU make
(version 3.81) on a Windows XP machine, where I am trying to use
it with the Korn shell under uWin. (I used the standard Windows
"shell" to build make, using the build)w32.bat script.) It
crashes, apparently every time I try to use $(shell ...). The
incrimating makefile contains:
currentDir = $(shell pwd)
componentName = $(notdir $(currentDir))
target = $(componentName).exe
all : $(target)
(There's a lot more in the actual makefile, but this is enough
to provoke the crash). If I invoke make -d on this makefile,
the output is:
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for Windows32
find_and_set_shell path search set default_shell =
C:/UWIN/usr/bin/sh.exe
Reading makefiles...
Reading makefile `GNUmakefile'...
CreateProcess(NULL,sh C:\UWIN\usr\bin\pwd,...)
/C/UWIN\usr\bin\pwd: line 4: uwin\usr\bin\pwd: not
found
I then get a Windows pop-up saying that make.exe has encountered
a problem, and asking if I want to send a bug report to
Microsoft.
If I use -d on a makefile with just:
config :
@echo $(SHELL)
The output will end with:
...
Must remake target `config'.
CreateProcess(C:\UWIN\usr\bin\echo.exe,echo C:/UWIN/usr/bin/sh.exe,...)
Putting child 0x0088e1d8 (config) PID 8974304 on the chain.
Live child 0x0088e1d8 (config) PID 8974304
Main thread handle = 0x000007ac
C:/UWIN/usr/bin/sh.exe
Reaping winning child 0x0088e1d8 PID 8974304
Removing child 0x0088e1d8 PID 8974304 from chain.
Successfully remade target file
`config'.
(Using an external command, instead of the shell built-in pwd,
in the first example, doesn't change anything.)
Does anyone have any ideas what could be wrong?
(Another wierd problem: when I redirect the output of make to a
file, i.e. "make >make.log 2>&1", everything works, the colors
for new text in the window change. To black on black, which I
have trouble reading. I have to open the properties pop-up on
the window, and change them back, and every thing works as
normal again. But it must rank as one of the wierdest problems
I've ever seen -- especially as it only happens with GNU make.)
--
James Kanze address@hidden
Conseils en informatique orientée objet/
Beratung in objektorientierter Datenverarbeitung
9 place Sémard, 78210 St.-Cyr-l'École, France +33 (0)1 30 23 00 34
- Problems with $(shell xxx) using uWin,
James Kanze <=
- Re: Problems with $(shell xxx) using uWin, Eli Zaretskii, 2006/06/03
- Message not available
- Re: Problems with $(shell xxx) using uWin, Eli Zaretskii, 2006/06/03
- Re: Problems with $(shell xxx) using uWin, James Kanze, 2006/06/03
- Re: Problems with $(shell xxx) using uWin, Earnie Boyd, 2006/06/04
- Re: Problems with $(shell xxx) using uWin, Eli Zaretskii, 2006/06/04
- Re: Problems with $(shell xxx) using uWin, James Kanze, 2006/06/05
- Re: Problems with $(shell xxx) using uWin, Eli Zaretskii, 2006/06/05
- Re: Problems with $(shell xxx) using uWin, Earnie Boyd, 2006/06/05