[bug #45050] Invalid read / heap overflow in unescape_char()

Follow-up Comment #1, bug #45050 (project make): after some check, I believe that the problem is in the code: char * unescape_char(char *string, int c) { . /* here, s can point to 0, however, after ++, the s might skip the 0 and continue reading "wild memory" */ *(p++) = *(s++);

[bug #62858] error: too few arguments to function ‘find_in_given_path’

Triage Status: None ___ Follow-up Comments: --- Date: Wed 03 Aug 2022 02:35:36 PM UTC By: chen System: Ubuntu 20.04 Lastest master or 4.3 tag code build step: $ ./bootstrap $ ./con

[bug #62858] error: too few arguments to function ‘find_in_given_path’

Follow-up Comment #2, bug #62858 (project make): [comment #1 comment #1:] ... > > If you want to build from Git, then make sure you have the latest version from Git. After checking, yeah, my repo is an old one, and I forget to pull. Thank you!

[bug #62858] error: too few arguments to function ‘find_in_given_path’

Follow-up Comment #3, bug #62858 (project make): Just as @psmith pointed out, some functions in gnulib changed their signature, e.g: find_in_given_path(), In case if someone need to build 4.3 release from git repo, please try these steps: 1. In a dir: $dir1, $ git clone https://git.savannah.g

[bug #18641] GNUmake 3.81, $(error ) sometimes unable to stop make process

Follow-up Comment #3, bug #18641 (project make): Thanks a lot for your reply, Paul. You catch my meaning right. I believe that the "include warning suppression" is expected for nearly every person using GNUmake. People use the ``gcc -M' technique mentioned in GNU make manual to generate .d files

[bug #21231] $(wildcard ) function sometimes fails very strangely

URL: Summary: $(wildcard ) function sometimes fails very strangely Project: make Submitted by: chjfth Submitted on: Wednesday 10/03/2007 at 09:51 Severity: 3 - Normal It

[bug #21231] $(wildcard ) function sometimes fails very strangely

Follow-up Comment #2, bug #21231 (project make): Thank you for your comment on Friday 11/23/07. As you said, putting out.txt in a subdir does not exhibit the problem -- that's right. However, I encountered that $(wildcard ) problem in my real-world makefiles when out.txt(other name may be used th

Re: make- target specific variables

On Tue, Sep 08, 2009 at 10:12:52AM +0530, Venkata Rajasekharu wrote: > Hi all, > > makefile: > - > > VAR = 1 $< 1 > all : VAR += 2 $< 2 > > all: makefile > echo $(VAR) > > --- > > bash-3.00$ make > 1 1 2 makefile 2 > > Since VAR is a recursively def

[bug #18641] GNUmake 3.81, $(error ) sometimes unable to stop make process

URL: Summary: GNUmake 3.81, $(error ) sometimes unable to stop make process Project: make Submitted by: chjfth Submitted on: Saturday 12/30/2006 at 22:03 Severity: 3 - Normal

[bug #17245] $(notdir foo/) should return . instead of blank

Follow-up Comment #1, bug #17245 (project make): Well, if you need such functionality, you can write your own function: MyNotDir_1 = $(if $(patsubst %/,,$1),$(notdir $1),.)#OK MyNotDir = $(foreach v,$1,$(call MyNotDir_1,$v)) Now, MyNotDir acts as you expect. I've tested it on make 3.

[bug #18641] GNUmake 3.81, $(error ) sometimes unable to stop make process

Follow-up Comment #1, bug #18641 (project make): [2007-01-04] Well, with the help of Martin Dorey, I've got to know that this bug has nothing to do with make's $(error ) function, but a make behavior change for ``-include '' directive. Since I used ``-include $(_p_SubprjsMade)'' instead of ``inc

[bug #18755] exported var-define and var-define from command line should appear in $(shell ) env

URL: Summary: exported var-define and var-define from command line should appear in $(shell ) env Project: make Submitted by: chjfth Submitted on: Thursday 01/11/07 at 10:23 Severity

Re: RE: [bug #18641] GNUmake 3.81, $(error ) sometimes unable to stop make process

ion of ${MAKE} -f $(_p_mk_MakeSubPrjs) fails. >Suggest rewriting the last two lines as: > > @${MAKE} -f $(_p_mk_MakeSubPrjs) && \ > touch $@ > >(echo -n "" > $@ is fine - touch $@ is just more usual and shorter.) > >This way, the parent