Hello
Could a short option be added for the following make option please?
--warn-undefined-variables Warn when an undefined variable is referenced.
I propose -u
Please keep my email address in any replies.
Best regards, Jon
___
Bug-make mailing
Hello
I am interested to know if anyway to see the line number in the
output. I've got some huge makefiles, and is hard to track down the
line with the error sometimes. I include an example below.
On Windows this looks like:
c:\make -f test.mk
unknown-exe
process_begin: CreateProcess(NULL,
On 6 May 2011 16:25, Eli Zaretskii e...@gnu.org wrote:
Date: Thu, 5 May 2011 22:30:04 +0100
From: Jon Grant j...@jguk.org
c:\make -f test.mk
unknown-exe
process_begin: CreateProcess(NULL, unknown-exe, ...) failed.
make (e=2): The system cannot find the file specified.
make: [build] Error 2
Hello
Eli Zaretskii wrote, On 06/05/11 21:23:
Date: Fri, 6 May 2011 21:01:24 +0100
From: Jon Grantj...@jguk.org
Cc: bug-make@gnu.org
Sorry, perhaps I was unclear. I am interested in the test.mk:5 text.
I don't mind the specific details or error code which is output later
in the line. Just the
Hello
I noticed that the all: target must be at the top of a makefile,
unless explicitly built by make all. Is this expected? It seems
quite limiting..
I'm running GNU Make 3.81, built for Windows32.
Please retain my email address in any replies.
Best regards, Jon
Output:
C:\make
system
Hello Paul
On 26 April 2011 13:34, Paul Smith psm...@gnu.org wrote:
On Tue, 2011-04-26 at 13:31 +0100, Jon Grant wrote:
I noticed that the all: target must be at the top of a makefile,
unless explicitly built by make all. Is this expected? It seems
quite limiting..
There is nothing special
Hello
I am using make 3.81 built for MinGW.
How easy to output the Makefile.mak:line for each command that fails to start?
I saw this function is what outputs the error, but not sure how to get
file and line number info. Any ideas?
Thanks, Jon
shell_function_completed
if
Please see my other reply. You only need to email the mailing list once!
Jon
___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
Hi,
[...]
/usr/lib64/gcc/x86_64-suse-linux/4.1.2/../../../../x86_64-suse-linux/bin/ld:
prorex.o: relocation R_X86_64_32 against `a local symbol' can not be
used when making a shared object; recompile with -fPIC
prorex.o: could not read symbols: Bad value
collect2: ld returned 1 exit status
Hi there,
Paul Smith wrote on 14/10/07 22:17:
On Sun, 2007-10-14 at 18:33 +0100, Jon Grant wrote:
Do they get free'd up when make exits?
No. It's quite difficult to do this since the variables are static and
so are only visible within that function. In order to free them we'd
have to add
Paul Smith wrote on 14/10/07 17:39:
On Sun, 2007-10-14 at 20:40 +0800, Zhongxing Xu wrote:
In function library_search(),
libpatterns and buf is malloced memory in line 1486 and 1553
respectively.
They are not freed.
Is this true?
Correct, they are not freed--but no, this is not a memory
Hi.
You've emailed the GNU Make mailing list, you can get help about the qt
and qtbittorrent package from your provider.
However, your email included many of the possible answers to the problem
you are having with Qt, like setting $QTDIR correctly and reading the
conf.log. I suggest you
Would it be an idea to include the ARG_MAX size in the error message (if
that is generated by make? function.c:1738 func_shell). And even include
a copy of the text and environment when running in debug mode?
I had to breakup a codebase into several libraries to overcome the
Could we considering adding Makefile.mak to the default filename
permutations which are looked for?
rationale:
I often see Makefiles which are called Makefile.mak, because that is
the extension of other make(s) on different OSs. Also it is more
convenient on Windows because then it can be
Hi Ajay,
This program is built for i686-redhat-linux-gnu
report bugs to bug-make@gnu.org
Isn't that just the standard output ? You can see that text on make --help
make *** [all] Error2
This is the actual error. As you've not included the full output it is
not clear what the problem
Hi,
Paul Smith wrote on 11/05/07 20:15:
On Sat, 2007-04-28 at 15:26 +0100, Jon Grant wrote:
A wider query relating to these warnings is that since make 3.81 is
released now, could we change make to use const's instead of #define'd
values, and inline functions instead of #define macro
Hi Alexander,
Thanks for getting back to us with that backtrace. Unfortunately the
debug symbols seem to be missing. I tried to get more info out myself of
your core file, but without the CVS binary I just get:
Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1.
Core was
Hi.
[EMAIL PROTECTED] wrote on 18/05/07 15:08:
I rebuilt it and the error came again. Using make from cvs 20070511, binutils 2.17.50.20070518 from
cvs, glibc from cvs 20070518, gcc-4.2.0, kernel 2.6.21.1, i686 (make 3.81 works). Using CFLAGS
-march=pentium4 -O2 -pipe -fomit-frame-pointer -s
Hi Pau. Thanks for your reply.
Please be sure that your LC_ALL and/or LANG variables are set to C
before running make check. I thought that I had modified this inside
the Perl scripts that drive the tests, but apparently I didn't get it
right; there was a bug report about it (this has been
Hello,
I noticed a few build warnings in CVS at present. Difficult to spot a
lot of the causes as there are many pre-processor macros in use.
A wider query relating to these warnings is that since make 3.81 is
released now, could we change make to use const's instead of #define'd
values,
Hello.
I just ran make check and got 33 failures. I'm running make 3.81, on a 6
month old Ubuntu Linux install.
They are all the same issue, the extra space. Not sure where the extra
space comes from, is anyone else seeing this?
Kind regards
Jon
*** work/features/include.base.2
File the bug report at this page:
http://savannah.gnu.org/projects/make/
___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
Hi Thomas,
Thanks for replying with the logs.
default_names tests that Make looks for default makefiles in the correct
order (GNUmakefile,makefile,Makefile). read.c:229 { GNUmakefile,
makefile, Makefile, 0 };
I suggest you file a bug report, I can't spot why why the sequence of
tests
Hi,
Turbo-parts elucidated on 01/03/07 22:03:
Hello, allways no targets specified and no makefile found. stop.
how can i change ?
Sounds like you have a problem with your project + build, check if there
is a Makefile in the directory; or explain the problem to the person
who provided you
Raheja, Himanshu elucidated on 09/02/07 20:12:
Hi Folks..!!
I am sorry to bug you again..
This should be the last one...
I was able to successfully run LPRng3.8.28 on my RED Hat Linux 4.4.
But as my company is already using 3.6.9d version and to avoid some
problems I am compiling the code
Hi,
[EMAIL PROTECTED] elucidated on 08/02/07 21:53:
i have some old (circa 1997) makefiles which run fine on current UNIX systems
with their versions of make. if i run gnu make as make -n then GNU make shows
the commands that will be executed just fine however, when i actually issue
the make
Hi
Dan Jacobson elucidated on 30/11/06 17:14:
$ cat Makefile
.PRECIOUS:.%.time
%.t:.%.time;
.%.time:%
bla bla bla
$ ls -1
Makefile
霧峰-桐林(有經朝陽科技大學) - Wufeng-Tonglin (Via Zhaoyang Technical University)
Well, no amount of quoting will enable me to
$ make '霧峰-桐林(有經朝陽科技大學) -
Martin Dorey elucidated on 30/11/06 21:32:
Isn't this more relevant? (Quoting from here on.)
Yeah, Looking at it again I can see that's likely the problem.
Jon
___
Bug-make mailing list
Bug-make@gnu.org
Hi,
Paul D. Smith elucidated on 29/11/06 02:27:
[...]
Finally, there is no way to detect an out of stack error and exit gracefully
with a warning as you suggest: the behavior of alloca() is undefined if you
run out of stack space (it doesn't just return NULL as malloc() etc. do).
Is it
Hi,
Why not build GNU Make? ;)
Cheers
Jon
___
Bug-make mailing list
Bug-make@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-make
30 matches
Mail list logo
