Hi Lane; please try to use a descriptive subject line for your email,
relating to the problem you're having. Including the version of GNU
make is very important (thanks!) but better reserved for the body of
your message, along with other critical information like the type of
system you're running
Hi,
I have a problem need someone help me out. I use the GNU make utility to
compile a Oracle Pro*C file into executable, but no matter how I play around
the make file, I could not keep the middle temporary C file which is created by
Pro*C compiler and this middle file was always automatically
This bug has been fixed in CVS. The fix will be available in the next
release of GNU make.
--
---
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://m
= a
/tmp>cat test.bug
all:
echo $(var)
/tmp>make -f make.bug x
make -f test.bug
make: expand.c:489: allocated_variable_append: Assertion
`current_variable_set_list->next != 0' failed.
Abort
Exit 134
/tmp>make --ver
GNU Make version 3.79.1, by Richard Stallman and Roland McG
%% [EMAIL PROTECTED] (Kai =?iso-8859-15?q?Gro=DFjohann?=) writes:
k> My suggestion: from (make)Recursion or one of its subnodes, add a
k> pointer to (make)Phony Targets. (And vice versa.)
OK.
--
---
Paul D. Smith
There is a node (make)Phony Targets in the info file which contains a
lot of useful information for recursively running make in subdirs.
However, there is no link to this information from the main node
which talks about subdirs, namely (make)Recursion.
My suggestion: from (make)Recursion or one o
Scripsit [EMAIL PROTECTED]
> make: my_make.mak: No such file or directory (ENOENT)
> Even invokation without any option and an existing 'Makefile'
> delivers a corresponding message.
> What can I do?
You need to tell something about the environment you run make
in. Which operating system? Did yo
Hi programmers,
trying to invoke make.exe with the option '-f my_make.mak' leads to the following
error message:
make: my_make.mak: No such file or directory (ENOENT)
Even invokation without any option and an existing 'Makefile' delivers a corresponding
message.
What can I do?
Kind regards
Fra
When trying to use gmake version 3.79.1 on a Dell 1GHz system running
Windows 2000, I'm seeing many of the following messages:
make: *** Warning: File `lcd.d' has modification time in the future
(2001-06-27 14:03:10 > 2001-06-27 14:03:09)
.
.
LOTS OF MAKE OUTPUT
.
.
make: warning: Clock skew det
Hello,
I have just finished translation of GNU make 3.79.1 to Danish.
During my testing of the translation I have found that some
messages which I suppose should be translated, are not marked for
translation.
The untranslated messages are:
- The arguments to the calls of the function log_acces
%% "Danny Turrin" <[EMAIL PROTECTED]> writes:
dt> Here is the bug: Makefile:21: *** commands commence before first
dt> target. Stop.
dt> ifeq (SunOS,$(SYSTYPE))
dt> ifeq ($(SYSVERS),570)
dt> SUBDIRS=sparcv8 sparcv9
dt> @echo sparcv89 > /home/dturrin/tdmf/Comp.log
Th
Hi,
Here is the bug:Makefile:21: *** commands commence before first target.
Stop.
I hope I can give you all the correct info...
All I am trying to do is add two traces in a Makefile (see below) using the
"@echo" command. The first trace seems to compile just fine, but the second
one is not
The method described in the manual is not the best one.
See my page below for a description of a more advanced method of
dependency tracking, which doesn't have this problem.
--
---
Paul D. Smith <[EMAIL PROTECTED]>
Hi,
I am not really shure if the problem I found should be called a bug,
but I thing I should tell the problem to improve usability of make.
I use make Version 3.79.1 under
- Linux / Intel Pentium
- HP-UX / HP-RISC
but I don't think that makes any difference.
I wrote some complex make
%% [EMAIL PROTECTED] writes:
rw> Sorry for the missing information, but I use (a part of ) the
rw> precompiled cygwin toolset
Ah. The Cygwin version of GNU make is not identical to the standard GNU
make distributed by the FSF. You should talk to the people at Cygwin
about it.
I know next
Dear Paul,
Sorry for the missing information, but I use (a part of ) the precompiled cygwin
toolset,
I was pleasantly surprised that make 3.79 did not pass the /cygdrive/c in the
pathname,
but this VPATH problem remained.
Reading your mail, I may have addressed the problem to the wrong people
If you've built your Windows version of make for Windows32 then I think
this is (or should be) all handled automatically.
See the README.W32 file for a discussion of how GNU make tries to handle
drive specifiers.
--
---
Hi,
I am a very happy user of the gnu tools. I encountered a problem I hope
you have a solution for.
I have software that is built on Unix machines and on PCs and use cygwin to
emulate the Unix environment. I use native compilers, and for the PC this
is the CL compiler from Microsoft's visual
18 matches
Mail list logo
