On Thu, 2015-11-26 at 10:02 +0530, Jay Aurabind wrote:
> Make 3.81 will finish the build in 27 minutes. With the same
> conditions for make 4, it takes 1 hour.
Most likely it's this bug: https://savannah.gnu.org/bugs/index.php?44555
___
Bug-make mailin
On Mon, 2016-01-04 at 08:07 +0800, 積丹尼 Dan Jacobson wrote:
> PATH=$$PATH:../v4
> PATH=$(PATH):../v4
> PATH=/home/jidanni/bin:/usr/bin:/bin:../v4
> PATH+=:../v4
>
> Is to use the third version,
> as the first will cause "ATH",
> the second a recursive error,
> and the fourth a blank in PATH that wi
On Tue, 2016-02-09 at 18:57 +0100, Enrico Scholz wrote:
> to pass down *all* environment variables given on cmdline to sub
> -makes, I used to write
>
> | export ${MAKEOVERRIDES}
Why are you doing this? Make always provides all the command-line
variables you set to all sub-makes. You don't need
On Tue, 2016-02-09 at 20:18 +0100, Enrico Scholz wrote:
> GNU make 4.0 seems to implement the behavior described in its
> documentation:
>
> > 5.7.2 Communicating Variables to a Sub-`make'
> > ...
> > `make' exports a variable only if it is either defined in the environment
> > initially or set on
Hi all.
Sorry I've been a bit incommunicado. Many things IRL going on: some
good, some not so good. Nothing devastating, but all requiring time
and attention.
At this time I expect to have some free(-ish) time in early March and I
want to clear up some outstanding bugs and make a new release of
On Fri, 2016-02-19 at 09:18 +, Yan Zhao OL Liu wrote:
> Recently I got a problem in using make.
> My code segment is below:
> $(RELEASE_DIR)/temp/%.o: %.cpp
> ${CC} ${CFLAGS} -c -o $@ $<;
> For the above code, I just want all the generated object files
> redirected to $(RELEASE_DIR)/temp
On Wed, 2016-02-17 at 12:52 -0500, Paul Smith wrote:
> At this time I expect to have some free(-ish) time in early March and
> I want to clear up some outstanding bugs and make a new release of GNU
> make during that time.
I've been thinking about updating the autotools prerequisi
Hi; please be sure to use the mailing lists, rather than emailing to me
directly. Also, for these lists we prefer inline replies rather than
top-posting. Thx!
> From: Paul Smith
> > $(RELEASE_DIR)/temp/%.o: %.cpp
> > ${CC} ${CFLAGS} -c -o $@ $<;
>
> > For the
Something that seems to be a constant source of confusion for users is
the fact that GNU make expands the entire recipe first, before it starts
any rules. Consider this recipe:
all:
@echo hi
@$(info there)
You would expect to see:
hi
there
but in reality, since make e
On Mon, 2016-03-14 at 10:50 -0600, Brian Vandenberg wrote:
> In Solaris it can sometimes be painful to get newer versions of auto
> -tools. At a minimum, please double-check OpenCSW to make sure the
> version you switch to is at least equal to if not lower than the
> latest version they have build
On Mon, 2016-03-14 at 10:24 -0600, Brian Vandenberg wrote:
> This could be remedied by making it fork before recipe expansion so
> the expansion happened in a sub-process. On the plus side it
> eliminates concerns of macros slowing down the parent make process
> but it breaks backward compatibilit
On Mon, 2016-03-14 at 10:36 -0700, Zoltan wrote:
> I don't particularly see a reason to change current behavior, but if
> you want to, how about implementing it like a "delayed" expansion
> except for recipe lines, so instead of $(...whatever), it would
> be written $$(...whatever...) in ord
On Mon, 2016-03-14 at 11:07 -0700, Zoltan wrote:
> Not exactly escaping '$' with '$$'. From your example of $(info ...), I'm
> actually suggesting to escape '$(' with '$$('. So not quite the same thing at
> all. And this is already implemented, and already "explained," so no extra
> work there.
On Mon, 2016-03-14 at 11:55 -0700, Zoltan wrote:
> > I was looking through the parsing code a week ago. As of 4.1 it treats ${
> > and
> > $( as meaning exactly the same thing. In our build we use the convention
> > $()
> > for macro calls and ${} for variable expansions, but the opposite could
On Tue, 2016-03-15 at 17:48 +, Eric DeCosta wrote:
> Sure, easy enough loop around looking at the return value from
> unlink, sleeping for 0.1 sec and trying again if unlink fails. There
> still should be some maximum amount of time to try before giving up.
> Do you think 3 seconds is too lon
On Tue, 2016-03-15 at 10:50 +, John Marshall wrote:
> Reposting as it would be nice to have this trivial documentation fix
> in the upcoming release.
Fixed for the next release (not pushed yet but in my repo), thanks.
___
Bug-make mailing list
Bug-m
On Wed, 2016-03-30 at 17:37 +0900, Luke Allardyce wrote:
> posixos.c needs to be excluded and w32os.c is missing from the w32 lib
> when cross building for windows, I got things working with the
> following
Thanks, I'll fix it. Cheers!
___
Bug-make mai
On Sat, 2016-04-02 at 13:49 -0700, David Boyce wrote:
> I've always believed and observed that $(CURDIR) returns an absolute
> path but can't find it spelled out anywhere in the docs. Would it be
> possible to insert the word "absolute" at the strategic point to
> clarify this?
We use getcwd(3) to
On Tue, 2016-04-05 at 11:25 +1000, Leo Carreon wrote:
> I expect that this addition will enable the use of the new Visual C++
> 2015 Build Tools without the need for the Visual Studio IDE.
Is it important to have a Visual Studio project to build GNU make?
isn't it sufficient to use the build_w32.b
On Wed, 2016-04-06 at 13:28 -0700, Dale Stimson wrote:
> I suggest the patch below. I have tested this and it works for me.
Ah, that was my bad with a recent change. It only shows up if your
makefile path is sufficiently long, which unfortunately none of the
regression test suite paths are. Tha
GNU make is a tool which controls the generation of executables and
other non-source files of a program from the program's source files.
You can learn more at: http://www.gnu.org/software/make/
---
On Thu, 2016-04-21 at 08:29 +0100, Tristan Wibberley wrote:
> x86-64 x86 armel: %=build/%/main.o: main.c ; true
> factors :: path=subst : prerequisites ; recipe
Almost all the syntax you suggest that uses "=" is not possible, because
it already has a well-defined meaning: it defines target-specif
On Sun, 2016-04-24 at 11:45 +0200, h.becker wrote:
> Build on VMS (V8.3/Alpha) fails with:
> $ @makefile
> ...
> Compiling function...
>
> # define vfork fork
> ...^
> %CC-W-MACROREDEF, The redefinition of the macro "vfork" conflicts with
> a current definition because one is object-
On Wed, 2016-04-27 at 15:25 -0400, Alfred M. Szmidt wrote:
> What are the intended semantics of the following snippet,
>
> target: foo=zork
> target:
> ifeq ($(foo),zork)
> @echo "zork zork"
> else
> @echo "bork bork"
> endif
>
> I'm think
On Wed, 2016-04-27 at 08:45 -0700, Paul Eggert wrote:
> Attached is a patch that fixes the following minor glitches that I
> found when building GNU Make 4.1.90 with GCC warnings enabled:
Thanks Paul. I applied most of these. The fixes for glob, getopt,
getloadavg, and hash I didn't apply as th
On Sun, 2016-04-24 at 10:01 +0300, Eli Zaretskii wrote:
> Isn't it also true that the ABI for loaded modules has changed in this
> version? I see that the gmk_floc object now has a new member
> 'offset'. Should this be called out in NEWS?
You're right. I reverted this change (or rather, I modif
On Mon, 2016-05-09 at 23:52 +0800, Jesse wrote:
> I wrote a c++ program which contains "auto".
> And I've wrote the makefile: g++ -std=c++11 ...
> However, it still remind of "..does not name a type ..."
> I've searched on the net for solution but gain nothing.
> I think it might be a bug in m
On Wed, 2016-05-18 at 10:04 +0900, Rakesh Mishra wrote:
> in order to install gromacs 454 in opensuse os on linux. but it is
> creating the problem at the cmake step. How can install this gromacs
> version.
This list is for bugs with GNU make. If you're having problems with
cmake, you should cont
rg (6):
Set up for running tests on VMS.
[SV 42447]: VMS simulate exporting symbols
[SV 41758]: Fix archive support for VMS.
Update README.VMS and move news to the NEWS file
Fix VMS implicit rules and UNIX paths.
Fix bs-nl handling, exit and Environment for
On Wed, 2016-05-25 at 09:19 -0700, Raymond Dubler wrote:
> What I need is:
> 1. no warning that blah.d is missing
> 2. same functionality as include blah.d, ie display error and
> terminate of failure
>
> Unless I am missing something in the manual, this is not provided with
> make.
>
> What
On Mon, 2016-05-23 at 12:31 +0200, Andreas Schwab wrote:
> What does it mean that the features/output-sync test always times out?
I don't know. It never does that for me. Can you give me more details
about your system?
Unfortunately this code is tricky because I'm trying to ensure that
targets
On Sat, 2016-05-28 at 16:09 -0700, Josh Triplett wrote:
> If make's own stdout/stderr refers to a PTY, make could create PTYs in
> place of pipes, collect output that way, and synchronize it to its own
> stdout/stderr as it does now.
Just for clarity: GNU make doesn't use pipes to collect output,
On Tue, 2016-05-31 at 11:14 +0900, Luke Allardyce wrote:
> GCC complains about unused parameters and an ambiguous-looking if-else
> in getopt.c
The getopt.c contained in the GNU make release is actually copied from
gnulib: I don't want to modify/maintain my own version of these files.
For the ne
On Tue, 2016-05-31 at 15:06 -0700, Josh Triplett wrote:
> However, if programs start observing those variables, that seems
> highly likely to lead to potential breakage in makefiles, for one key
> reason: those variables remain in the environment even for programs
> run with stdout/stderr redirecte
Hi all; due to the issue related to double-colon rules I plan to make a
4.2.1 release, probably tonight, containing that fix (which appears to
work OK) and a few other cleanups as already committed.
If there are other quick-fix things appropriate for a 4.2.1 release let
me know.
_
mps on MS-Windows
Jeremy Devenport (1):
* main.c (main): [SV 48009] Reset stack limit for make re-exec.
Luke Allardyce (1):
[SV 48037] Fix MinGW build with Posix configury tools
Paul Smith (5):
* w32/pathstuff.c: [SV 47996] Use ISBLANK() not isblank().
* DELETE_ON_ERRO
On Thu, 2016-06-16 at 18:35 -0600, Erasmo Aguilera wrote:
> I am working on a project with two directory trees: one for sources
> and another for output files. I run mingw-make from the source tree
> and add the output tree root to VPATH so that their files can be found
> when acting as prerequisit
On Mon, 2016-07-04 at 23:21 -0300, Bruno Pezzi wrote:
> I know it's not recomended to do, but it's a project from college
> and I can't finnish because of it. What am I supposed to do?
This list is for help with the GNU make program itself; your problem
appears to be compiling (a variation of) th
On Thu, 2016-07-14 at 15:40 -0700, sgardell wrote:
> But when I try to build across makefiles in parallel then I see two
> different things:
> 1) If I turn on any sort of output sync it gets dramatically slower.
> Sometimes slower than our -j1 time!
I recommend trying with the latest release, G
On Sun, 2016-07-17 at 15:48 +, Gardell, Steven wrote:
> OK. Thanks! I will try the latest version.
>
> FWIW, I am measuring is total wall clock time to complete the build.
> (date; gmake... ; date) This goes up substantially with all sync modes
> other than "none" if gmake has parallel invoca
On Sun, 2016-07-24 at 17:48 -0500, Ryan Bissell wrote:
> I had a need to read up on these error messages:
>
> > ‘missing target pattern. Stop.’
> > ‘multiple target patterns. Stop.’
> > ‘target pattern contains no `%'. Stop.’
> > ‘mixed implicit and static pattern rules. Stop.’
>
>
> The manual
On Wed, 2016-07-27 at 21:39 +0800, Lei Zhang wrote:
> The problem is, somehow Make defaults CXX to g++ instead of c++, so
> my solution doesn't work. While CC already defaults to cc, is there
> any specific reason for CXX not to default to c++?
The POSIX spec defines that "cc" be a C compiler, and
On Tue, 2016-09-13 at 23:24 +0200, orsobianco9 wrote:
> the make program reports the following error.
> 'This program was compiled for i686-pc-linux-gnu
> Report bugs to '
In general it's better to run your test case that you want to send to
the mailing list with LANG=C as most GNU make developer
On Wed, 2016-09-14 at 15:16 -0700, Philip Guenther wrote:
> On Wed, Sep 14, 2016 at 3:13 PM, Paul D. Smith
> wrote:
> ...
> > Probably an example like this would help make the doc more clear.
>
> There *is* an example like that in the doc in at least version 4.2.1!
Oh. Yeah. Hah!
___
Please keep the mailing list CC'd on replies: it's likely someone there
will be able to help in case I'm not available. Also in general we
prefer interleaved replies rather than top-posting (putting your reply
first then including the entire message you're replying to afterward) on
the mailing lis
On Tue, 2016-09-20 at 15:28 +, Pietro wrote:
> Hi,
>
> I have noticed that there is a difference between the two scenarios
> listed below:
>
> i) make CC=arm-linux-gnueabihf-gcc CPPFLAGS=[..]
>
> ii) export CPPFLAGS=[..] [RET]
> make CC=arm-linux-gnueabihf-gcc
>
> I was told that the d
On Fri, 2016-09-23 at 05:52 -0700, David Boyce wrote:
> I still think that's a good plan, except that now I find out it ends
> up exporting anyway. I'm sure it's too late to change now but is
> there a reason for this (unfortunate IMHO) behavior?
I can't tell you: this behavior has existed since t
On Fri, 2016-09-23 at 16:09 -0700, David Boyce wrote:
> "Macros defined by the MAKEFLAGS environment variable and macros
> defined in the makefile(s) shall not be added to the environment of
> make if they are not already in its environment."
That text is not in the currently published version of
On Sun, 2016-09-25 at 11:26 -0700, David Boyce wrote:
> While the behavior of setting MAKEFLAGS in the makefile may be
> undefined, its behavior when encountered in environment seems to be
> made clear by this statement and GNU make still seems wrong there:
I've filed an enhancement request for co
On Thu, 2016-10-06 at 10:26 -0700, Kyle Rose wrote:
> all: $(addprefix target,1 2 3 4 5 6 7 8 9 10)
> @echo glob: $(wildcard target*)
>
> target%:
> touch $@
>
> To wit:
>
> $ make
> touch target1
> touch target2
> touch target3
> touch target4
> touch target5
> touch target6
> touch tar
On Thu, 2016-10-06 at 11:47 -0700, Kyle Rose wrote:
> On Thu, Oct 6, 2016 at 11:38 AM, Paul Smith wrote:
> > You should include the version of GNU make that you're using; my
> > version works as expected:
> >
> > $ make --version
> > GNU Make 4.2.1
>
>
On Thu, 2016-10-06 at 10:26 -0700, Kyle Rose wrote:
> This is not a weird or contrived use case: this is wildcard not
> finding targets in a recipe executed after they've been built as
> explicit prerequisites.
I discovered the difference. If you put the makefile in a different
directory, like th
On Fri, 2016-10-07 at 00:10 +, Martin Dorey wrote:
> ... then I failed to find any source that invalidates that cache, be
> it the whole cache, just one directory or one entry in that directory.
I'd have to reread that code to be sure but I don't think that's how it
works. I think that what's
On Mon, 2016-11-07 at 01:35 +0200, Jaak Ristioja wrote:
> Some time ago I submitted a bunch of stuff to the issue tracker at
> https://savannah.gnu.org/bugs/?group=make but there doesn't seem to
> be much activity there.
Hi Jaak. Thanks for those, I did see them. I hope to have some time
between
On Wed, 2016-11-09 at 19:29 +0200, Jaak Ristioja wrote:
> GNU Make seems to randomly crash on an Raspberry Pi 2 with
>
> INTERNAL: Exiting with 2 jobserver tokens available; should be 5!
>
> or similar when emerging Gentoo Linux packages using multiple jobs
> (e.g. -j5). The kernel log then ha
On Wed, 2016-11-09 at 21:31 +0200, Jaak Ristioja wrote:
> I'm attaching[*] the core and the binaries for 4.2.1, but I don't
> know how to debug it myself.
It's unlikely anyone here will be able to help debug a random ARM core
file (for sure I can't). At the very least we would need a stacktrace
f
On Wed, 2016-11-09 at 22:42 +0200, Jaak Ristioja wrote:
> I have no ARM experience myself. I don't even know where to look for
> ABI
> documentation. This is the best I can currently get from the core:
>
> (gdb) thread apply all bt full
>
> Thread 1 (LWP 15210):
> #0 0x0d33b0bc in ?? ()
> No sym
On Fri, 2016-11-11 at 12:28 +0100, Paolo Bonzini wrote:
> Paul, any news?
I expect to carve out a chunk of time to work on GNU make maintenance
next month, and will try to put out a new release. These updates are
in my queue to look at.
Thanks!
___
Bu
On Sat, 2016-11-12 at 13:06 +0200, Jaak Ristioja wrote:
> I'm guessing that PATH_MAX is 4096 on most Linux systems, while the stack is
> 8192.
There's no way the stack is so small. Virtually no userspace program
can run with an 8k stack, regardless of whether they use alloca() or
not.
I think yo
On Fri, 2016-11-11 at 19:41 +0200, Jaak Ristioja wrote:
> After examining about 10 more core files, these all point to job.c:519
> and job.c:537, similarly to the above:
>
> #0 0x00c2bd74 in child_error (child=0x0, exit_code=0, exit_sig=0,
> coredump=0, ignored=0) at job.c:519
> pre =
On Sun, 2016-11-20 at 00:03 +0200, Jaak Ristioja wrote:
> So I guess I'll attempt to recompile glibc and run valgrind on the
> parent "make -j5" process and see whether that turns up anything. If
> not, then I'll try the -fsanitize=address approach. I expect all of this
> to take some time (and per
On Sat, 2016-11-19 at 18:49 +0100, Michael Stapelberg wrote:
> With this change, users who have their editor misconfigured when writing
> Makefiles without using 8 spaces for one TAB character will also get a
> friendly error message.
I'm not a fan of this change.
Make's "missing separator" is re
On Tue, 2016-11-29 at 17:54 +0100, Bruno Haible wrote:
> So, the problem will be fixed if you add the option
> --flag=DB:2:c-format
> to the variable XGETTEXT_OPTIONS in the file po/Makevars.
Ah! I had no idea that existed! I forget that xgettext works on the
un-preprocessed source code so it
I have generated a new 4096-bit RSA GPG key and am switching to it from
my old key.
All future signatures for GNU make releases and announcements will be
created using the new key. The old key was not compromised and can
continue to be used safely but future correspondence should be encrypted
usi
Hi all; I believe that the NO_FLOAT compile option in GNU make is not
really relevant anymore and I'd like to remove it just to clean up a bit
of code. I don't know of any system where you can't declare variables
of type double or float and I'm not aware of any situation in which this
would make a
Hi all (especially Eli! :)).
A bug https://savannah.gnu.org/bugs/?49115 came in about the way we
parse filenames in the read.c:parse_file_seq. There is a loop that's
supposed to chop a string into individual filenames, and each time
through the loop we search for the end of the string like this:
I should have provided more details, sorry about that.
On Sun, 2016-12-18 at 19:33 +0200, Eli Zaretskii wrote:
> > However the content of the if-statement looks weird to me as well; I've
> > checked and it's been like this almost forever though. We're trying to
> > find the end of the current pat
On Sun, 2016-12-18 at 22:10 +0200, Eli Zaretskii wrote:
> > Maybe it would be clearer what the issue was if we removed the second
> > colon:
> >
> > foo:/bar ; @echo hi
> >
> > In UNIX this would be "foo : /bar ; @echo hi" which is a valid rule.
>
> On Windows, this is ambiguous, i.e. it invok
On Wed, 2016-12-28 at 08:49 -0600, Tianyi Zhang wrote:
> When I am installing lucida, I experience such bugs here. I am using 64bit
> computer.
> "
> This program built for x86_64-pc-linux-gnu
> Report bugs to
> Faile to install Apache Thrift
> make[1]: *** [all] Error 1
> make[1]: Leaving direc
On Thu, 2017-02-02 at 16:53 +0100, Stefan Tauner wrote:
> I don't know why it behaves differently with slashes in the goal and
> would love to hear a rationale for that (and it being mentioned in
> the documentation ;)
> The current documentation reads as follows (emphasis mine):
> > By default, th
On Wed, 2017-02-08 at 13:48 +, Raz Manor wrote:
> I created a makefile using instructions for this post: http://make.mad
> -scientist.net/papers/advanced-auto-dependency-generation/
> To test it, I make all my files, then deleted one .d file and touched
> one of the header files present in that
On Thu, 2017-02-09 at 08:16 +, Raz Manor wrote:
> Unfortunately I can't send you my makefile as it gives up company IP.
I wasn't suggesting you send your makefile: we don't have the time or
energy to understand and debug an entire make environment :). I was
suggesting you create a small sampl
On Sun, 2017-02-12 at 12:11 +, Raz Manor wrote:
> OK, I got it. I used .SECONDARY instead of .PRECIOUS to preserve the
> .d and .o files. I did it because I still wanted files to be deleted
> if they were stopped mid-build. Is there a way to get both of the
> behaviors?
The sample auto-dep mak
On Mon, 2017-02-13 at 20:43 -0800, ruchi wrote:
> NUMJOBS := 24
> MAKEFLAGS := -j3 -l36
>
> SUBDIRS := a \
> b \
> c
>
> .PHONY $(SUBDIRS)
> $(SUBDIRS) : $(SOME_INITIAL_WORK)
> c : a b
> $(SUBDIRS):
> @echo "=> Working on '$@' for '$(ARCH)'..."
>
On Mon, 2017-02-13 at 22:22 -0800, ruchi wrote:
> Hi Paul
> Thanks for looking into it.
I'm not sure what aspect of your mail software is causing your messages
to be sent twice, about 8 minutes apart, but it would be helpful if you
could disable it.
> It would be difficult for me to share the exa
On Tue, 2017-03-14 at 14:19 +0300, Aleksey Fedotov wrote:
> I've stumbled upon a peculiar issue, which made make to deadlock.
Yes, this is not good. One simple (simplistic) fix is to obtain the
translation of fatal error messages early and store them away, and then
use that version when generatin
On Sun, 2017-03-19 at 01:51 +, Alejandro García Vallejo wrote:
> bar: $(@:%r=foo%z)
> @echo End
>
> foobaz:
> @echo The
>
> """
> GNU Make Output:
> End
>
> Make fails to read $@ (aka, it's empty).
That's not a bug; that's defined behavior. From the GNU make manual:
https:
Before you go too far with performance improvements you should really
move to the latest version of GNU make (4.2.1) or even try the current
Git HEAD (but you'll need to install autotools etc. to build from Git).
It's less useful to be doing performance testing with a version of make
that old.
O
On Sat, 2017-03-18 at 22:49 -0700, brenorg wrote:
> > I'd prefer to investigate improving the existing parser, rather than
> > create a completely separate parser path.
>
> I could agree if the difference were 10x or more. But I believe 2x a
> reasonable gain from removing so many features. From w
On Wed, 2017-05-24 at 19:40 +1200, Jonny Grant wrote:
> Shouldn't Make exit after the missing file?
>
> Make appears to be carrying on, and then treating the makefile as a target.
Info here:
https://www.gnu.org/software/make/manual/html_node/Remaking-Makefiles.html
_
> X-Mailer: NIMS ModWeb Module
I don't know what this is, but it generates pretty seriously malformed
SMTP messages :-/.
Using the Win32 port of GNU make 3.79.1 on Windows 2000 with either the =
Cygwin shell, or the MKS sh.exe, or even the Windows cmd.exe I get a =
hang when running the follo
"Verrol L. Adams" <[EMAIL PROTECTED]> writes:
> hi, i have been using the following on HP-UX with their make and
> clearmake (part of Clearcase) without problem:
> ${MOD_CPP}: ${@F.o=.cpp}
I don't believe you. Probably you mean this:
${MOD_CPP}: $${@F.o=.cpp}
(note the double-$).
> Any
My previous message should have given the URL as:
ftp://alpha.gnu.org/gnu/make/make-3.80rc2.tar.gz
ftp://alpha.gnu.org/gnu/make/make-3.80rc2.tar.bz2
not "alpha.ftp.org". Sums in my previous email are correct. Sorry for
the confusion :(
--
Hi;
After looking at the code I've determined that passing the "o" is not
sufficiently safe. There are sections of the eval() function which call
variable_expand(), which will reset the variable_buffer setup. So if
you put any of those in your expansion text you'll be sad.
So, I'm going with m
%% Regarding [[EMAIL PROTECTED]: SHELL query/bug]; you wrote:
sb> I'm using make v3.78.1 under MS-Windows2k
sb> The problem I'm having is that it just doesn't seem to pick up the
sb> shell that I've specified in my environment variables.
sb> I've tried combinations of SHELL and MAKESHELL
On Monday, 6 November, Eli Zaretskii ([EMAIL PROTECTED]) wrote:
> As far as Make is concerned, I think you can say "SHELL=mysql -e" and
> have it your way, no?
No. Make is hardcoded to add the -c option; every command make invokes is run
with "$(SHELL) -c ".
___
On Tue, 2006-11-28 at 18:45 -0800, Martin Dorey wrote:
> > Using heap, which requires a system call to get more memory
>
> (It doesn't affect the main point of Paul's reply but just for academic
> interest) no it doesn't:
> Even in less contrived applications, brk isn't called anything like as
>
On Tue, 2006-11-28 at 03:48 -0800, rocky john wrote:
> I am amateur at linux .i am trying to install nagios-2.6.i
> went through documentations after executing commands
> make install -commandmode
> make install -config
> I got
On Wed, 2006-11-29 at 05:49 -0800, Howard Chu wrote:
> Some modern mallocs are good, but stack-based allocation is still better
> a lot of the time. Especially for temporary variables that are just
> going to be discarded after a few computations.
Right. And remember it's not just the code man
On Wed, 2006-11-29 at 13:22 +, Jon Grant wrote:
> > 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 i
On Thu, 2006-11-30 at 22:51 +, Jon Grant wrote:
> 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.
I might need to reopen that bug; there definitely was a change in
behavior WRT
On Thu, 2006-11-30 at 16:52 -0800, Martin Dorey wrote:
> Works for me if I remove the two close-parentheses and replace the white
> space with underscores. Open-parenthesis fine, close-parenthesis bad.
> Weird. Close-parenthesis is also bad with Debian sarge's make-3.80.
I suspect that has to d
On Thu, 2006-11-30 at 18:30 -0800, Martin Dorey wrote:
> -rw-rw-r-- 1 martind software 0 2006-11-30 16:44 bracket()
> [EMAIL PROTECTED]:~/tmp/make-2006-11-30$ make 'bracket()'.t
> make: *** No rule to make target `bracket().t'. Stop.
That seems to be a bug. I can reproduce it. On the other han
On Fri, 2006-12-01 at 13:08 -0800, david baker wrote:
> I'm forwarding a note I sent to Karl Berry <[EMAIL PROTECTED]> which he
> advised to be sent to you. Additionally I am attaching screen shots of
> the actions I took and published on linuxquestions.org and the
> Makefile.in from LPRng-3.8
On Fri, 2006-12-01 at 13:08 -0800, david baker wrote:
> I'm forwarding a note I sent to Karl Berry <[EMAIL PROTECTED]> which he
> advised to be sent to you. Additionally I am attaching screen shots of
> the actions I took and published on linuxquestions.org and the
> Makefile.in from LPRng-3.8
On Tue, 2006-12-05 at 00:35 +0100, sofia wrote:
> I'm trying to install the packages Net-Pcap0.14 but it's impossible to
> do "make",it reports:
>
> /usr/bin/ld: /usr/local/lib/libpcap.a(pcap-linux.o): no se puede usar la
> reubicación R_X86_64_32 contra `a local symbol' cuando se hace un objeto
On Mon, 2006-12-11 at 15:36 +0100, Sombat Ketrat wrote:
> the error msg. is
> ---
> GNUmakefile:3: *** Sorry, your version of GNU make (3.81) is too old.
> You need one that defines the CURDIR variable. Stop.
> ---
> ifneq (default,$(origin CURDIR))
> $(error Sorry, your version of GNU make ($(M
On Tue, 2006-12-12 at 06:29 +0200, Eli Zaretskii wrote:
> But this test could be defeated if CURDIR was defined in the
> environment, right? If so, the test should make sure CURDIR doesn't
> come from the environment.
I was assuming that if it was defined, someone set it. But I guess
you're rig
I can only assume you're trying to prove a point by making this bug
report virtually unintelligible, with no concrete suggestions for
improvement. Well played. Unfortunately for your point, there's a good
reason for make's behavior.
Pattern rules only match if make can successfully create all th
On Wed, 2006-12-20 at 23:43 -0500, Shannon Coffey wrote:
> I am attempting to compile GCL on a Macintosh.
This list is for bugs with the GNU make program itself. If you're
having problems building some particular software you should find a
mailing list dedicated to that software and ask there f
601 - 700 of 1502 matches
Mail list logo
