%% "vivek" <[EMAIL PROTECTED]> writes:
v> When 'make' program is invoked with -C option, then it decends into
v> that directory but the 'PWD' variable still refers to the path from
v> where the 'make' was invoked rather than the path of the directory
v> it decends into.
PWD is not a varia
Hi,
When 'make' program is invoked with -C option, then it decends into that
directory but the 'PWD' variable still refers to the path from where the
'make' was invoked rather than the path of the directory it decends into.
With regards
Vivek Gupta
_
I've been using automatic prerequisites for years (I noticed the
current documentation puts a set -e in front so command failures
will be treated as errors...
One of the problems is
make clean
or
make -n
will start making the prerequisites...
What I've done is:
ifneq (,$(fi
%% "Darren Hiebert (Contractor)" <[EMAIL PROTECTED]> writes:
dh> As recorded in this message:
dh> http://lists.gnu.org/archive/html/bug-make/2005-02/msg00012.html
dh> On 16 Feb 2005, Paul D. Smith wrote:
>> The time has come, and past, to get GNU make 3.81 out the door. Here is
>>
As recorded in this message:
http://lists.gnu.org/archive/html/bug-make/2005-02/msg00012.html
On 16 Feb 2005, Paul D. Smith wrote:
The time has come, and past, to get GNU make 3.81 out the door. Here is
the schedule I am committing to: there WILL be a release of GNU make
3.81 on or about M
Google says:
http://lists.gnu.org/archive/html/bug-make/2003-08/msg6.html
> I believe this has been fixed in version 3.80.
-
Martin's Outlook, BlueArc Engineering
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of [E
Hi,
We are compiling our source code using a
Diab comliper.
We use Recursive Make.
Attached Makefile calls
Makefile.swan2.
We are facing the following
error:
gmake: expand.c:489:
allocated_variable_append: Assertion 'current_variable_set_list->next != 0'
failed.
Aborted
Could you plea