Re: Please check about the GIT problem.

on't have to cover the user name in the path. This > is because I changed it to a different account name. What I'm > currently using seems to be a problem with personally installing the > git in Korea. You seem to be having a problem building the Git project. This mailing

Re: Please check about the GIT problem.

On Sat, 6 Apr 2024 16:50:33 +0900 (KST) 12zz12 <12z...@kakao.com> wrote: > root@uk91-Korea:/home/u/다운로드# tar -zxf git-2.38.5.tar.gz > root@uk91-Korea:/home/u/다운로드# ls > git-2.38.5 git-2.38.5.tar.gz google-chrome-stable_current_amd64.deb > root@uk91-Korea:/home/u/다운로드# cd

Re: Problem setting a variable inside a target

-- Bahman On Tue, 2023-09-26 at 16:30 +, Ed L Wolf wrote: > The problem is that $(eval SUPPLIER_A2l := $(sort $(shell find > $(DIR_A2LGEN_SUPPLIER) -type f -name "*.a2l"))) runs before the > directory was created and the a2l files were copied to the directory. > Since this r

RE: Problem setting a variable inside a target

The problem is that $(eval SUPPLIER_A2l := $(sort $(shell find $(DIR_A2LGEN_SUPPLIER) -type f -name "*.a2l"))) runs before the directory was created and the a2l files were copied to the directory. Since this ran before the directory creation and copy of the a2l file SUPPLIER_A2L

Re: Problem setting a variable inside a target

ginal hierarchy of `*.a2l' files into `DIR_A2LGEN_SUPPLIER' which had made very difficult to tell Make how to make a target and when. Here's my further slimmed down version of your snippet. Let me know if that makes sense and whether it solves your problem. You can also view o

Re: Problem setting a variable inside a target

On Sun, 2023-09-24 at 17:23 +, Ed L Wolf wrote:     > > ifneq ($(wildcard $(DIR_SUPPLIER)),) > ... > > $(eval SUPPLIER_A2l := $(sort $(shell find $(DIR_A2LGEN_SUPPLIER) - > > type f -name "*.a2l")))  > ... > ifeq ($(SUPPLIER_A2l),"*.a2l") > Quickly skimming through your co

RE: Problem setting a variable inside a target

o "A2LSupplier folder not available" endif Ed L Wolf Technical Advisor - Embedded Software e.l.w...@cummins.com Cummins Inc. Mail Code: C7004 1460 National Road Columbus, Indiana 47201 United States -Original Message- From: Bahman Movaqar Sent: Tuesday, September 26, 2

Re: Problem setting a variable inside a target

Subject: RE: Problem setting a variable inside a target * EXTERNAL EMAIL * One more comment. For some reason SUPLLIER_A2l is blank Ed L Wolf Technical Advisor - Embedded Software e.l.w...@cummins.com Cummins Inc. Mail Code: C7004 1460 National Road Columbus, Indiana 47201 United States

RE: Problem setting a variable inside a target

@gnu.org Subject: RE: Problem setting a variable inside a target The following code response was Supplier folder detected Supplier folder detected but no a2l files present but the response should have been Supplier folder detected Supplier

RE: Problem setting a variable inside a target

@gnu.org Subject: Re: Problem setting a variable inside a target EXTERNAL SENDER: This email originated outside of Cummins. Do not click links or open attachments unless you verify the sender and know the content is safe. > The eval statement below highlighted in red is not working Perhaps yo

Re: Problem setting a variable inside a target

h I doubt you're going to get from find(1): mad@shuttle:~/tmp/wolf-2023-09-24$ find -name "*.a2l" mad@shuttle:~/tmp/wolf-2023-09-24$ From: bug-make-bounces+martin.dorey=hds@gnu.org on behalf of Ed L Wolf Sent: Sunday, September 24, 2023 10:23

Problem setting a variable inside a target

Hello I am having some trouble trying to set a variable inside a target. When reading the variable, it comes up blank. Below is my make file code. The eval statement below highlighted in red is not working. Can you provide some assistance please? I am using GNU Make 4.1 $(DIR_A2LGEN_SETUP)/McD

Re: GNU Make 4.4.0.90 on Manjaro 17 — bi-arch problem

e build details attached. I forgot about this one. I think I see the problem here, in configure.ac.

Re: GNU Make 4.4.0.90 on Manjaro 17 — bi-arch problem

On Manjaro Linux 17, installed from manjaro-kde-17.1.12-stable-x86_64.iso, in 32-bit mode, the build failure reported in https://lists.gnu.org/archive/html/bug-make/2022-10/msg00212.html still occurs. Find the build details attached. makeerror-manjaro17-32bit.tar.gz Description: application/co

Re: GNU make 4.3.92 on Manjaro 17 — bi-arch problem

On Tue, 2022-10-25 at 16:20 +0200, Bruno Haible wrote: > Unfortunately, it did not fix the problem. Find attached the details > of that failed build. Hm. The link test I added did fail, as expected, but somehow that did not translate to disabling Guile support. I must have messed up som

Re: GNU make 4.3.92 on Manjaro 17 — bi-arch problem

Guile, not just > assume that if we can find the header we're good to go. Unfortunately, it did not fix the problem. Find attached the details of that failed build. makeerror-manjaro17-32bit.tar.gz Description: application/compressed-tar

Re: GNU make 4.3.91 on Manjaro 17 — bi-arch problem

On Wed, 2022-10-19 at 02:20 +0200, Bruno Haible wrote: > The cause: > libguile-2.2.so happens to be installed only as 64-bit binaries, in > /usr/lib. > Not as 32-bit binaries, in /usr/lib32. Yet, /usr/include/guile/2.2/ > exists. I added extra configure checking to try to link with Guile, not just

GNU make 4.3.91 on Manjaro 17 — bi-arch problem

On Manjaro Linux 17, installed from manjaro-kde-17.1.12-stable-x86_64.iso, it is possible to build 64-bit binaries (with CC="gcc") or 32-bit binaries (with CC="gcc -m32"). With CC="gcc -32", the compilation fails: $ make ... gcc -m32 -I/usr/include/guile/2.2 -pthread -g -O2 -Wl,--export-dynamic

[bug #60960] Fix/report race problem if having multiple "alias" for the same target

Follow-up Comment #1, bug #60960 (project make): It's actually a very hard problem to know whether two paths are really the "same file" or not. That's why make uses a simple textual comparison and leaves it at that (it does try one trivial simplification: it treats the targ

[bug #60960] Fix/report race problem if having multiple "alias" for the same target

URL: <https://savannah.gnu.org/bugs/?60960> Summary: Fix/report race problem if having multiple "alias" for the same target Project: make Submitted by: None Submitted on: Thu 22 Jul 2021 01:49:14 PM UTC

Re: Catboost built problem

On Sat, 2019-06-08 at 03:40 +, Hossein Chegini wrote: > make -r -DUSE_ARCADIA_PYTHON=no -DOS_SDK=local > -DPYTHON_CONFIG=python3-config This is not a valid GNU make command line. When you set variables on the make command line you don't use -D; -D is not a valid option for GNU make. You just

Catboost built problem

Hi, Once I tried to compile the catboost with following command: I received the error : make -r -DUSE_ARCADIA_PYTHON=no -DOS_SDK=local -DPYTHON_CONFIG=python3-config [cid:image001.png@01D51E10.7A629A10] Would you please help me to resovel that. Cheers. __

Re: A problem with "-include"

I added back the mailing list, for completeness. On Sun, 2019-06-02 at 00:25 +0430, Arham Amouei wrote: > I just didn't like the fact that whenever I entered "make clean" the > make first updated depend.mk and then deleted it! Ah. It would have been good if your original questions had been more

Re: A problem with "-include"

On Sat, 2019-06-01 at 19:47 +0430, Arham Amouei wrote: > It seems to me that -include depend.mk in addition to including > depend.mk, executes the rule that depend.mk is its target. I'd like > to stop this behavior. Found nothing helpful in the manual for this > purpose. I saw your question on Sta

A problem with "-include"

Hi My makefile comes below. When the folder is clean and I enter make clean I receive mpicc -MM *.c > depend.mk rm -f *.o libfmd.so depend.mk It seems to me that -include depend.mk in addition to including depend.mk, executes the rule that depend.mk is its target. I'd like to stop this behavior.

Make-4.2.1 problem with $(SHELL) syntax

oshell, which naturally complains: /bin/sh: line 1: "This is a test": command not found I can fix the problem by explicitly running the shell under "env", as shown. And this fix is good enough, I imagine. However, perhaps there is some other finer poin

I am getting problem with native compilation linux :

i am getting error in native compilation ( using build root) h, --help Print this message and exit. -i, --ignore-errors Ignore errors from commands. -I DIRECTORY, --include-dir=DIRECTORY Search DIRECTORY for included makefiles. -j [

Re: Fwd: Re: Target-specific variable in subdirectory problem

Hi Sven, Le jeudi 03 août 2017 à 16:46 +0100, Sven C. Dack a écrit : > it's a common practise to create a Makefile for each subdirectory and > have it include definitions from a parent Makefile. That's probably why > you don't see that many directory-spanning features in make. It's easier > to man

Fwd: Re: Target-specific variable in subdirectory problem

some recipes which are located in subdirectories. I am not looking for the target-specific variable feature in filenames strictly matching the target in the current directory. I looked strange that no variable was defined when in a subdirectory. Anyway, it seems that a global variable would solve my probl

Re: Target-specific variable in subdirectory problem

Le jeudi 03 août 2017 à 15:06 +, Edward Welbourne a écrit : > Benjamin Cama (3 August 2017 17:00) > > Well, I tried: > > > >SUBDIR = $(dir $@) > >$(SUBDIR)/target-%: > > … > > > > But it doesn't work. But without a slash (which is already present at > > the end of $(SUB

Re: Target-specific variable in subdirectory problem

Le jeudi 03 août 2017 à 14:59 +0200, Benjamin Cama a écrit : > To further enhance my understanding of the “right” usage of Makefiles, > would you advise me to explicitly specify the subdirectory in the > target > definition? Because I feel that counting on pattern rules to match in > subdirectory i

Re: Target-specific variable in subdirectory problem

Le jeudi 03 août 2017 à 09:20 -0400, Kyle Rose a écrit : > On Aug 3, 2017 9:00 AM, "Benjamin Cama" wrote: > Anyway, it seems that a global variable would solve my problem, and > indeed it looks a bit more right this way: I can still get the stem in >

Re: Target-specific variable in subdirectory problem

On Aug 3, 2017 9:00 AM, "Benjamin Cama" wrote: Anyway, it seems that a global variable would solve my problem, and indeed it looks a bit more right this way: I can still get the stem in my recipe (with $*), and everything works as expected. It's just that the global namespace i

Re: Target-specific variable in subdirectory problem

; > prerequisite patterns and the file name. > > That's how "subdir/test-stem" can match a pattern "test-%" which you > normally would not expect it to match. Thanks for the reference. I actually kind of expected that it would match in subdirs in my particular cas

Re: Target-specific variable in subdirectory problem

> The example in his question makes very clear what he wants: he wants a > pattern-specific variable assignment. Most likely yes. If you look at the subject of this thread it says "Target-specific variable in subdirectory problem" so he probably only wants the variable to be set

Re: Target-specific variable in subdirectory problem

t's be fair here. What I meant by saying that you didn't respond is that you didn't respond to his initial e-mail containing his problem, but that you hopped onto my response, second-guessed me, told me I'm wrong when really it's just an opinion you're having, and

Re: Target-specific variable in subdirectory problem

On Wed, 2017-08-02 at 21:16 +0100, Sven C. Dack wrote: > I suggest you turn your attention towards him and ask him what he > wants. The example in his question makes very clear what he wants: he wants a pattern-specific variable assignment. The solution you provided was not a pattern-specific var

Re: Target-specific variable in subdirectory problem

Paul's interpretation appears to be the same as mine, and seems like the only straightforward interpretation of the OP's message. If that's the case (and Benjamin can tell us if it is not), I believe his message from 3:16 ET entirely explains the difference in behavior between test-% used in patter

Re: Target-specific variable in subdirectory problem

I suggest you turn your attention towards him and ask him what he wants. My example does exactly what I say it does. It's just not your place to tell me I'm wrong when you don't know what he wants his makefile to do and so far haven't responded to him and only to me. Or am I missing something

Re: Target-specific variable in subdirectory problem

On Wed, 2017-08-02 at 20:40 +0100, Sven C. Dack wrote: > It's my understanding that we don't actually know what Benjamin wants to > do, because nobody has asked. So I don't see how this would make me wrong. > >  From his mail am I assuming he wants his Makefile to print "BAR" for a > target "tes

Re: Target-specific variable in subdirectory problem

It's my understanding that we don't actually know what Benjamin wants to do, because nobody has asked. So I don't see how this would make me wrong. From his mail am I assuming he wants his Makefile to print "BAR" for a target "test-stem" as well as "subdir/test-stem", which is what he will get

Re: Target-specific variable in subdirectory problem

On Wed, 2017-08-02 at 20:03 +0100, Sven C. Dack wrote: > Hello, > > try it with the following rules: > > test-%: $(eval FOO = BAR) > test-%: > echo $(FOO) No, this doesn't do what the OP wants. The eval in the prerequisites of the pattern is expanded immediately so this is identical to wri

Re: Target-specific variable in subdirectory problem

On Wed, Aug 2, 2017 at 3:03 PM, Sven C. Dack wrote: > Hello, > > try it with the following rules: > > test-%: $(eval FOO = BAR) > test-%: > echo $(FOO) FOO is a global variable in this case. Not sure what you're trying to demonstrate here. Kyle __

Re: Target-specific variable in subdirectory problem

Hello, try it with the following rules: test-%: $(eval FOO = BAR) test-%: echo $(FOO) $ make test-stem echo BAR BAR $ make subdir/test-stem echo BAR BAR I cannot tell you why it fails in your example. My guess is that it's just not good practise to use a plain assignment for a prerequisit

Re: Target-specific variable in subdirectory problem

Benjamin Cama (2 August 2017 12:19) > I may be doing something wrong, but the following Makefile gives me > strange results: the target-specific variable does not apply when used > for a target in a subdirectory. > >test-%: FOO = BAR >test-%: >echo $(FOO) > > E.g.: >

Target-specific variable in subdirectory problem

Hi, I may be doing something wrong, but the following Makefile gives me strange results: the target-specific variable does not apply when used for a target in a subdirectory. test-%: FOO = BAR test-%: echo $(FOO) E.g.: $ make test-stem ech

problem report of features/output-sync fails

Hi, I'd like to explain about a problem in features/output-sync test program. There were several reports about this problem in the past of this mailing list, but the source of problem is not recognized yet. This time, I'd like to drill it down to make it clear. The problem is: $

Re: A Severe Problem with Make

ie (19 July 2017 19:19) I use Ubuntu Linux on my system. I have downloaded and tried to install the make-4.2.1 package but when I execute the 'make' command (after the package is configured) I encounter a problem and I don't know how to resolve. can you help me? I have put the er

Re: A Severe Problem with Make

Iman Moosaie (19 July 2017 19:19) > I use Ubuntu Linux on my system. I have downloaded and tried to > install the make-4.2.1 package but when I execute the 'make' command > (after the package is configured) I encounter a problem and I don't > know how to resolve. can

A Severe Problem with Make

Hello I use Ubuntu Linux on my system. I have downloaded and tried to install the make-4.2.1 package but when I execute the 'make' command (after the package is configured) I encounter a problem and I don't know how to resolve. can you help me? I have put the error results in a te

Re: Problem with GNU Make (3.81, probably newer) with stacking --include-dir=...

On Wed, 2014-06-11 at 13:45 -0400, Paul Smith wrote: > Unfortunately in older versions of make the option and argument > are left as two separate words: > > $ echo 'a:;: $(MAKEFLAGS)' | make-3.81 -f- -I/usr/include -I/bin > : I /usr/include -I /bin > > which makes it much more difficult to re

Re: Problem with GNU Make (3.81, probably newer) with stacking --include-dir=...

On Tue, 2014-06-10 at 16:01 -0700, Corey Brenner wrote: > I've run into a situation where I want to control the include dirs in > a recursive make. I am adding include paths to recursive invocations > via --include-dir=, when I find one which matches my criteria. > > However, GNU Make seems to b

Problem with GNU Make (3.81, probably newer) with stacking --include-dir=...

level invocations to lower ones.  The construction of include paths, via --include-dir, should be per-invocation, and not shared with children, except by providing --include-dir=... on the recursive command line.  The attached small makefile illustrates and documents the problem. Is there a way to sup

[bug #39035] problem with blanks in continuation line in a recipe

Update of bug #39035 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Operating System:

[bug #39035] problem with blanks in continuation line in a recipe

URL: <http://savannah.gnu.org/bugs/?39035> Summary: problem with blanks in continuation line in a recipe Project: make Submitted by: None Submitted on: Wed 22 May 2013 08:35:08 AM UTC Severity: 3 -

Problem with secondary expansion and target specific variables

The following makefile.1 produces correct results: --- target1 : var := one target2 : var := two targets := target1 target2 all : $(targets) .SECONDEXPANSION: $(targets) : foo/$$(var)/bar foo/%/bar : mkdir -p $(dir $@) touch $@ .PHONY : target1 target2

Re: root/test make problem

On 06/19/2012 10:19 PM, igle...@unifesp.br wrote: > Dear Sirs, > I am tryinng to install root (cern) in ubuntu 12.04 in order to run a R > package called xps. I could install root following many posts advices (I > am not an expert on linux) and the tutorials run fine. However, I can > not install t

root/test make problem

Dear Sirs, I am tryinng to install root (cern) in ubuntu 12.04 in order to run a R package called xps. I could install root following many posts advices (I am not an expert on linux) and the tutorials run fine. However, I can not install the test directoty with make. I got this: Generating

problem gnu

salut; "there doesn't seem to be GNU Make file in PATHor in dev C++ Bin path" j'ai toujour de problem avec le C++ il ne peut pas compiler a cause de cette erreur,, même prob avec codeblock ou visual c++ quoi faire svp? ___ B

Re: Possible problem / misunderstanding in make manual

On Thu, 2011-05-12 at 14:20 +0200, Julien Palard wrote: > 2011/5/12 Paul Smith > That's because the online manual describes the latest released version > of GNU make (3.82) but your system is using an older version where > this > feature is not supported. > > Oh so easy .

Re: Possible problem / misunderstanding in make manual

2011/5/12 Paul Smith > That's because the online manual describes the latest released version > of GNU make (3.82) but your system is using an older version where this > feature is not supported. > Oh so easy ... and the version is wrote in the first page of the online version ( i missed it ) ,

Re: Possible problem / misunderstanding in make manual

On Thu, 2011-05-12 at 10:10 +0200, Julien Palard wrote: > I have hard time to understand a part of the make manual, the problem > can be a typo of a subject not clearly expressed, here is the point : > > In the page about multiline variables : > http://www.gnu.org/s/he

Possible problem / misunderstanding in make manual

I have hard time to understand a part of the make manual, the problem can be a typo of a subject not clearly expressed, here is the point : In the page about multiline variables : http://www.gnu.org/s/hello/manual/make/Multi_002dLine.html A statement say that : "You may omit the var

Re: Problem with parallel build

a separate test case that reproduces that behavior? In any case that doesn't seem to the problem in Michael's post. The final link command is failing to find app1.o. The archive is already built successfully. The app1.o in this example doesn't actually use anything from the library

Re: Problem with parallel build

> Date: Thu, 21 Oct 2010 15:04:20 -0400 > From: Mike Shal > Cc: Bug-make@gnu.org > > I don't see why Michael's example should fail, but I can reproduce the > behavior with 3.81 and 3.82. It fails because, depending on the timing, app1.o may or may not exist when Make comes to check it. Here's t

Re: Problem with parallel build

rate test case that reproduces that behavior? In any case that doesn't seem to the problem in Michael's post. The final link command is failing to find app1.o. The archive is already built successfully. The app1.o in this example doesn't actually use anything from the library, so e

RE: Problem with parallel build

: Bug-make@gnu.org Subject: Problem with parallel build The Makefile shown below sometimes fails to build the main target (app1). Can anyone reproduce the error and explain what's wrong or confirm it's a bug? All required files are in the attached .tar file. To reproduce the error, make

Problem with parallel build

The Makefile shown below sometimes fails to build the main target (app1). Can anyone reproduce the error and explain what's wrong or confirm it's a bug? All required files are in the attached .tar file. To reproduce the error, make sure app1.o does not exist, then run "make -j2 app1" repeatedly.

Re: possible problem with $(dir ... )

On Tue, 2010-07-13 at 12:44 -0700, Warren Dodge wrote: > > I notice that $(dir ...) leaves the trailing / when given a full > filename path. > > Is there an easy way to remove the trailing / ? It ain't pretty but the standard, safe way of doing it is: $(patsubst %/,%,$(dir ...))

possible problem with $(dir ... )

fails to give me /x/y/z and gives /x/y/z/bin/ . I assume the trailing / in /x/y/z/bin/ is the problem. $(dir $(dir /x/y/z/bin/program)) I was trying to avoid using $(shell ... ) which I assume is slower. ___ Bug-make mailing list Bug-make@gnu.org

[bug #29025] problem with odd directory names with spaces and/or parentheses

7;t support pathnames containing spaces. That's Savannah bug #712. The other problem is a duplicate of the just-fixed bug #28525. ___ Reply to this item at: <http://savannah.

[bug #29025] problem with odd directory names with spaces and/or parentheses

Follow-up Comment #1, bug #29025 (project make): FWIW, I am attaching the original SubDirSpaces directory from the cmake test failure report at http://sourceforge.net/projects/mingw-w64/forums/forum/723798/topic/3551522 The original error message, as reported to me is the following: "gmake[2]: E

[bug #29025] problem with odd directory names with spaces and/or parentheses

Additional Item Attachment, bug #29025 (project make): File name: SubDirSpaces.tar.gzSize:0 KB ___ Reply to this item at: ___ Message sent

[bug #29025] problem with odd directory names with spaces and/or parentheses

URL: <http://savannah.gnu.org/bugs/?29025> Summary: problem with odd directory names with spaces and/or parentheses Project: make Submitted by: sezero Submitted on: Sun 28 Feb 2010 10:35:47 AM GMT Severity: 3 -

Re: problem in using -j with make

n rules do support multiple targets for a single rule.  Depending on your needs, you may be able to use a pattern rule instead of a static rule. Tom. On 2/8/2010 2:47 PM, Warren Dodge wrote: I have a make file that is causing me a problem when I try to use the -j option to speed things up.

problem in using -j with make

I have a make file that is causing me a problem when I try to use the -j option to speed things up. Here is a simplified version of it that shows my problem. ### Makefile all:a b c d e touch all a b c d e: script.5files

I have another problem

: Seif Eldrasi Subject: I have problem with Cygwin To: bug-make@gnu.org Date: Tuesday, February 2, 2010, 6:52 PM Dear Sir,   I was installing the Cygwin on my laptop and I was going on steps like what is says till I stop on a point of setting the environment variables. Please tell me how to do that

I have problem with Cygwin

Dear Sir,   I was installing the Cygwin on my laptop and I was going on steps like what is says till I stop on a point of setting the environment variables. Please tell me how to do that. Thank you Kind regards. Name: Seifelnaser Hamed Speciality: Computer Science Mobile No:  001-832-434-7763

Re: Splitting lines problem in make-3.80 versus 3.81

On Tue, 2009-09-08 at 13:02 -0700, Warren Dodge wrote: > I have attached a small tree of files which will show what we are trying > to do. It has the "runit" script which will process through the > combinations and save the results in log files. I have looked at your examples. I'm not sure why th

Re: Splitting lines problem in make-3.80 versus 3.81

On Tue, 2009-09-08 at 13:02 -0700, Warren Dodge wrote: > I tried it on my specific problem and indeed it solved the issue. A > co-worker was working on another Makefile an having a similar issue. We > tried the solution above and ran into a number if strange issues. I haven't look

RE: Splitting lines problem in make-3.80 versus 3.81

..@gnu.org [mailto:bug-make-bounces+mdorey=bluearc@gnu.org] On Behalf Of Paul Smith Sent: Tuesday, September 08, 2009 13:30 To: warren.l.do...@tektronix.com Cc: bug-make@gnu.org Subject: Re: Splitting lines problem in make-3.80 versus 3.81 On Tue, 2009-09-08 at 13:02 -0700, Warren Dodge wrote:

Splitting lines problem in make-3.80 versus 3.81

Syntax", chapter "Writing Recipe in Rules", for > details. I tried it on my specific problem and indeed it solved the issue. A co-worker was working on another Makefile an having a similar issue. We tried the solution above and ran into a number if strange issues. I have attac

Re: executing perl problem with make 3.81 versus 3.80

I'll check it out. Thanks ___ Bug-make mailing list Bug-make@gnu.org http://lists.gnu.org/mailman/listinfo/bug-make

RE: executing perl problem with make 3.81 versus 3.80

ssage- From: bug-make-bounces+mdorey=bluearc@gnu.org [mailto:bug-make-bounces+mdorey=bluearc@gnu.org] On Behalf Of Warren Dodge Sent: Thursday, September 03, 2009 17:15 To: bug-make@gnu.org Cc: warr...@tektronix.com Subject: executing perl problem with make 3.81 versus 3.80 I have t

executing perl problem with make 3.81 versus 3.80

I have this "Makefile.bug" and an empty file "yyy" which makes no logical sense as I stripped my original problem down to this. ---

Re: make 3.81 + i386-pc-interix* parallelism problem, and "write error"

I'm running make on x86 interix (SFU/SUA). All works like a charm, >> >> > except >> >> > for occasional problems with multi-core machines (I'm not sure if the >> >> > same >> >> > problems would occur on single cores too...).

Re: make 3.81 + i386-pc-interix* parallelism problem, and "write error"

r occasional problems with multi-core machines (I'm not sure if the > >> > same > >> > problems would occur on single cores too...). > >> > > >> > I'm seeing two different problems, the "bader" one being a jobserver > >> &g

Re: make 3.81 + i386-pc-interix* parallelism problem, and "write error"

7;m seeing two different problems, the "bader" one being a jobserver token >> > leak. Sometimes make exits with messages like this: >> > >> >     make: INTERNAL: Exiting with 3 jobserver tokens available; should be >> > 2! >> > >> > But muc

Re: make 3.81 + i386-pc-interix* parallelism problem, and "write error"

> > I'm seeing two different problems, the "bader" one being a jobserver token > > leak. Sometimes make exits with messages like this: > > > > make: INTERNAL: Exiting with 3 jobserver tokens available; should be > > 2! > > > > But much

Re: make 3.81 + i386-pc-interix* parallelism problem, and "write error"

make simply hangs, and seems to be out of > jobserver tokens! Is this a known problem? I tried the patch from [1], but > that didn't make any difference. > > Also I found a patch against 3.80, adding the jobserver_tokens global > variable, so I assume that one has been incorporate

make 3.81 + i386-pc-interix* parallelism problem, and "write error"

oken leak. Sometimes make exits with messages like this: make: INTERNAL: Exiting with 3 jobserver tokens available; should be 2! But much worse is the case where make simply hangs, and seems to be out of jobserver tokens! Is this a known problem? I tried the patch from [1], but that didn

building make 3.81 on HP-UX with bundled compiler small problem

GNU make 3.81 fails to compile on HP-UX 11iv1 (11.11) with the bundled K&R C compiler. The error is like va_dcl unknown identifier in misc.c. I'm using this hack to workaround: echo '#include '>> config.h or more completely: cd ${SOURCE} rm -rf make-3.81 gzcat make-3.81.ta

Problem with substitution reference

Getting a 'target pattern contains no '%' from running a simple make. Running make from OpenSuse using GNU make 3.8.1. Any help would be greatly appreciated. Makefile -- hello: echo $@ make -f include.mk hello include.mk -- hello: hello.o cc -c h

[bug #23468] end-of-line backslashes fails with perl (Cygwin, although I strongly believe it's general problem)

Update of bug #23468 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #2: As Anonymous points o

[bug #23468] end-of-line backslashes fails with perl (Cygwin, although I strongly believe it's general problem)

Follow-up Comment #1, bug #23468 (project make): Look in the NEWS file: * WARNING: Backward-incompatibility! In order to comply with POSIX, the way in which GNU make processes backslash-newline sequences in command strings has changed. If your makefiles use backslash-newline sequences ins

[bug #23468] end-of-line backslashes fails with perl (Cygwin, although I strongly believe it's general problem)

URL: <http://savannah.gnu.org/bugs/?23468> Summary: end-of-line backslashes fails with perl (Cygwin, although I strongly believe it's general problem) Project: make Submitted by: None Submitted on: Tuesday 06/03/2008 a

Re: Problem with make HP-UX

On Mon, 2008-04-21 at 15:17 +0530, vasanthan wrote: > where could i found the same version of GNU make > can any1 send me the link Source code for GNU make can be found here: ftp://ftp.gnu.org/gnu/make -- -

Problem with make HP-UX

Hi... make --version in parent server ( server in france) gives me the below information GNU Make version 3.78.1, by Richard Stallman and Roland McGrath. Built for hppa2.0n-hp-hpux11.00 Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99 Free Software Foundation, Inc. This is free soft

RE: install problem

27;t a make bug. Good luck. I fear you may need it. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Charles H.D.W Sent: Thursday, December 13, 2007 07:38 To: bug-make@gnu.org Subject: install problem I want to instal libieee1284-0.1.6 but when i gift &qu

install problem

I want to instal libieee1284-0.1.6 but when i gift "make" command, it always diplay: docbook2man -o doc doc/interface.sgml make: docbook2man: Command not found make: *** [doc/ieee1284_claim.3] Error 127 please gift me a solution... ___ Bug-make mailing

  1   2   3   4   5   >