Sorry for spam, I omit or I used wrong this option when I test it.
It works as I expected.
On 2023. 05. 05. 16:34, Eli Zaretskii wrote:
Date: Fri, 5 May 2023 12:47:35 +0300
From: Nagy Ákos
I want to configure a custom location for a Makefile.
I use the make tool as sysadmin, and I use the sa
> Date: Fri, 5 May 2023 12:47:35 +0300
> From: Nagy Ákos
>
> I want to configure a custom location for a Makefile.
>
> I use the make tool as sysadmin, and I use the same makefile for each
> usualy docker project, and I need to copy it to all folders where I use
> it, and I need to update it o
On Fri, 2023-05-05 at 12:47 +0300, Nagy Ákos wrote:
> automatic detection: when the make tool don't found the makefile in
> local folder, can check an environment variable (ex:
> MAKEFILE_LOCATION) and if exist, can use it
>
> manual flag: can add a new configuration flag to make: make
> --locat
Hello,
I want to configure a custom location for a Makefile.
I use the make tool as sysadmin, and I use the same makefile for each
usualy docker project, and I need to copy it to all folders where I use
it, and I need to update it on all location.
Workflow:
automatic detection: when the ma
GNU parallel has a "-j" option quite like GNU make. But it also
allows to specify the number of jobs relative to the number of
CPU cores present:
--jobs N
-j N Number of jobslots on each machine. Run up to N jobs in parallel. 0
means as many as possible.
Default is 100% which
URL:
<https://savannah.gnu.org/bugs/?59752>
Summary: feature request: quote/expand function
Project: make
Submitted by: alecov
Submitted on: Tue 22 Dec 2020 07:00:07 PM UTC
Severity: 3 - Normal
Item
URL:
<https://savannah.gnu.org/bugs/?57680>
Summary: Feature request "import"
Project: make
Submitted by: ydaveluy
Submitted on: lun. 27 janv. 2020 18:40:07 UTC
Severity: 3 - Normal
Item Gr
Am 05.01.20 um 17:03 schrieb Paul Smith:
That is not the right URL; you want git://git.sv.gnu.org/gnulib (note the
/git subdirectory is removed).
When you use https: you need to use /git/gnulib after the hostname, but
when you use the git: protocol you just use /gnulib after the hostname.
Ups
On Sun, 2020-01-05 at 12:12 +0100, Christof Warlich wrote:
> Thus, everything looks perfectly fine so far. But the following still
> fails:
>
> > $ git ls-remote git://git.sv.gnu.org/git/gnulib
> > fatal: remote error: access denied or repository not exported:
> > /git/gnulib
That is not the righ
Am 04.01.20 um 21:55 schrieb Paul Smith:
Hm, this worked fine for me:
$ git ls-remote git://git.sv.gnu.org/gnulib
...list of branches...
Perhaps your system is sequestered behind some sort of firewall that will
not allow the git: protocol (port 9418 IIRC) to pass through? Almost all
f
On Sat, 2020-01-04 at 10:16 +0100, Christof Warlich wrote:
> The original doesen't work from my system (Debian Buster) at least:
>
> > $ ./bootstrap
> > ./bootstrap: Bootstrapping from checked-out make sources...
> > ./bootstrap: getting gnulib files...
> > Cloning into 'gnulib'...
> > fatal: unab
Am 03.01.20 um 21:25 schrieb Paul Smith:
On Fri, 2020-01-03 at 20:42 +0100, Christof Warlich wrote:
By the way, I stumbled into a minor issue entirely unrelated to the
feature above that you may want to fix: The gnulib git repository
referenced in bootstrap seems to have changed its location, s
On Fri, 2020-01-03 at 20:42 +0100, Christof Warlich wrote:
> By the way, I stumbled into a minor issue entirely unrelated to the
> feature above that you may want to fix: The gnulib git repository
> referenced in bootstrap seems to have changed its location, so you may
> want it to change it accord
Hi Paul,
Am 03.01.20 um 18:24 schrieb Paul Smith:
Hi Christof; .EXTRA_PREREQS is provided in 4.2.93 please test in your
environment.
Note that I did rework some things to allow it to work with implicit rules
(previously it only worked for explicit rules) although it still can't be
used as a pat
On Fri, 2019-08-09 at 17:52 +0200, Christof Warlich wrote:
> attached is the comprehensive (and significantly reworked) patch that
> implements the feature of a new internal variable
Hi Christof; .EXTRA_PREREQS is provided in 4.2.93 please test in your
environment.
Note that I did rework some thi
> From: Paul Smith
> Cc: thirdedit...@gmx.net, bug-make@gnu.org
> Date: Tue, 19 Nov 2019 09:22:17 -0500
>
> On Fri, 2019-11-15 at 15:52 +0200, Eli Zaretskii wrote:
> > Ping! Paul, did you have a chance to look at this issue?
>
> Sorry, I'm quite underwater. I hope to be able to do a bit of mak
On Fri, 2019-11-15 at 15:52 +0200, Eli Zaretskii wrote:
> Ping! Paul, did you have a chance to look at this issue?
Sorry, I'm quite underwater. I hope to be able to do a bit of make work
over the next few weeks: get out a final RC and a release.
For this, I don't really understand the issue :).
Ping! Paul, did you have a chance to look at this issue?
> Date: Thu, 07 Nov 2019 17:29:48 +0200
> From: Eli Zaretskii
> Cc: bug-make@gnu.org
>
> > From: "Jannick"
> > Cc:
> > Date: Thu, 7 Nov 2019 12:32:23 +0100
> >
> > Subject: [PATCH 03/13] Windows build: add optional cmd line flag --exe-
> From: "Jannick"
> Cc:
> Date: Thu, 7 Nov 2019 12:32:23 +0100
>
> Subject: [PATCH 03/13] Windows build: add optional cmd line flag --exe-name to
> build_w32.bat
>
> This commit helps the user choose a name for the GNUMake executable
> different from the default 'gnumake.exe' used at link time
On Mon, 04 Nov 2019 05:35:46 +0200, Eli Zaretskii wrote:
> And how do you suggest to fix this?
For your consideration attached 3 patches implementing the suggested idea: a
new optional command line flag '--exe-name' to build_w32.bat to help the
user pass an executable name (default: 'gnumake') us
> From: "Jannick"
> Cc:
> Date: Sun, 3 Nov 2019 22:01:06 +0100
>
> > In particular, can you show how the hard-coded name of the executable
> > prevents linking against the import library?
>
> As said above, the issue is not about linking the dll (which should always
> work), but that the plugin
Hi Eli,
Many thanks for looking into this!
On Sun, 03 Nov 2019 17:35:42 +0200, Eli Zaretskii wrote:
> > From: "Jannick"
> > Date: Sun, 3 Nov 2019 13:30:11 +0100
> >
> > Would it be possible to pass to build_w32.bat in an optional command
> > line argument the executable name (currently hard code
> From: "Jannick"
> Date: Sun, 3 Nov 2019 13:30:11 +0100
>
> Would it be possible to pass to build_w32.bat in an optional command line
> argument the executable name (currently hard coded in the variable MAKE as
> 'gnumake')?
>
> When creating a plugin (.dll) with GCC (by linking against gnumake
Hi,
This is a pure Windows issue:
Would it be possible to pass to build_w32.bat in an optional command line
argument the executable name (currently hard coded in the variable MAKE as
'gnumake')?
When creating a plugin (.dll) with GCC (by linking against gnumake.dll.a)
which should then be called
Am 14.08.19 um 20:31 schrieb Paul Smith:
On Fri, 2019-08-09 at 17:52 +0200, Christof Warlich wrote:
From my perspective, everything is complete and works as it should,
so I would definitely need your feedback if there is anything missing
or wrong.
Otherwise (or in parallel), could you guide
On Fri, 2019-08-09 at 17:52 +0200, Christof Warlich wrote:
> From my perspective, everything is complete and works as it should,
> so I would definitely need your feedback if there is anything missing
> or wrong.
>
> Otherwise (or in parallel), could you guide me to get the copyright
> assignment
Am 13.07.19 um 14:46 schrieb Paul Smith:
On Wed, 2019-07-10 at 18:15 +0200, Christof Warlich wrote:
Am 10.07.19 um 14:44 schrieb Paul Smith:
Let me know how you want to proceed.
As I want to tackle the most challenging part first, I'd like to suggest to
do the copyright assignment after the t
Am 13.07.19 um 14:46 schrieb Paul Smith:
On Wed, 2019-07-10 at 18:15 +0200, Christof Warlich wrote:
Am 10.07.19 um 14:44 schrieb Paul Smith:
Let me know how you want to proceed.
As I want to tackle the most challenging part first, I'd like to suggest to
do the copyright assignment after the t
On Wed, 2019-07-10 at 18:15 +0200, Christof Warlich wrote:
> Am 10.07.19 um 14:44 schrieb Paul Smith:
> > Let me know how you want to proceed.
>
> As I want to tackle the most challenging part first, I'd like to suggest to
> do the copyright assignment after the technical side is in a decent shape
Am 10.07.19 um 14:44 schrieb Paul Smith:
Would it really help if I try to supply a patch that implements your idea?
Or is the current "state of affairs" sufficient that the general idea (i.e.
allowing to add target specific prerequisites without changing automatic
variables) will eventually go i
On Wed, 2019-07-10 at 10:24 +0200, Christof Warlich wrote:
> > What if we do this instead: create a variable which can contain a list
> > of "hidden prerequisites": they will always be built first but they
> > won't cause any changes in the automatic variables. If set globally it
> > will apply to
Am 09.07.19 um 20:51 schrieb David Boyce:
I don't claim to know much about how Savannah works but I see
anonymous bug reports and RFEs come in frequently so it seems you
don't need a login to make one.
https://www.gnu.org/software/make/manual/html_node/Bugs.html
Thanks, that's want I was looki
Am 09.07.19 um 20:52 schrieb Paul Smith:
https://savannah.gnu.org/bugs/?func=additem&group=make
You don't have to make an account in order to file a bug, but be sure
to add yourself to mail notifications if you don't create an account,
or you won't get any updates.
Ok, but considering your sugg
On Tue, 2019-07-09 at 20:19 +0200, Christof Warlich wrote:
> Am 09.07.19 um 15:42 schrieb David Boyce:
> > I also think the proposal is reasonable but I think it would be
> > "stickier", i.e. less likely to get lost, if you filed it as an
> > enhancement request via the Savannah bug reporting syste
I don't claim to know much about how Savannah works but I see anonymous bug
reports and RFEs come in frequently so it seems you don't need a login to
make one.
https://www.gnu.org/software/make/manual/html_node/Bugs.html
On Tue, Jul 9, 2019 at 11:19 AM Christof Warlich wrote:
> Am 09.07.19 um 1
Am 09.07.19 um 15:42 schrieb David Boyce:
I also think the proposal is reasonable but I think it would be
"stickier", i.e. less likely to get lost, if you filed it as an
enhancement request via the Savannah bug reporting system.
I'd be glad to do that if it increases the chance to get it in. Bu
I also think the proposal is reasonable but I think it would be "stickier",
i.e. less likely to get lost, if you filed it as an enhancement request via
the Savannah bug reporting system.
On Tue, Jul 9, 2019 at 5:27 AM Tim Murphy wrote:
> I quite like this idea because so many of us work on integ
I quite like this idea because so many of us work on integrating things
that we have no permission to modify and we need ways to make them work
cleanly without messing them up. They are sort of "fix-up" or "patch"
dependencies. I'm not sure the name makes this clear though.
Regards,
Tim
On Sat
on 05.07.19 at 23:44 Martin Dorey wrote:
... Sadly, though, adding all these things to the dependency list
won't really help me. We installed this system just three days ago,
yet the mtime on stdio.h is months ago:
devadmin@ch-ep1-3:~$ ls -l /usr/include/stdio.h
-rw-r--r-- 1 root root 31494 Fe
ind@swiftboat:~/tmp/warlich-2019-07-05$
> depenency
> conviniently
> reciepe
Spelling.
From: Bug-make on behalf of
Christof Warlich
Sent: Thursday, July 4, 2019 10:13
To: bug-make@gnu.org
Subject: Feature request / patch: dependency-only prerequisites
* EXTERNAL EMAIL *
De
Dear all,
please bear with me if I'm doing something wrong here, this is the first
time that I'm trying to contribute to GNU Make.
The attached patch would add a minor (but imho useful) feature to GNU
Make. Here is an extract of the (changed) documentation (changes are in
red), giving a quite co
I've recently come up with a nifty way to detect subdirectories:
ALLFILES := $(notdir $(wildcard $(d)/*))
# figure out which files are subdirs by wildcarding on /.
SUBDIRS := $(notdir $(patsubst %/.,%,$(wildcard $(addprefix
$(d)/,$(addsuffix /.,$(ALLFILES))
This is useful for scanning whole d
I've recently come up with a nifty way to detect subdirectories:
ALLFILES := $(notdir $(wildcard $(d)/*))
# figure out which files are subdirs by wildcarding on /.
SUBDIRS := $(notdir $(patsubst %/.,%,$(wildcard $(addprefix
$(d)/,$(addsuffix /.,$(ALLFILES))
This is useful for scanning whole d
OK
>
> From: Paul Smith
>To: Jim Michaels
>Cc: "bug-make@gnu.org"
>Sent: Thursday, May 2, 2013 4:41 AM
>Subject: Re: feature request: parallel builds feature
>
>
>On Wed, 2013-05-01 at 20:38 -0700, Jim Michaels wrote:
On Wed, 2013-05-01 at 20:38 -0700, Jim Michaels wrote:
> again, problem solved with what I proposed. think. separate shell
> window for each job.
You can do that today by just writing your recipes such that they start
a screen session or xterm or whatever. Those tools allocate and manage
their
again, problem solved with what I proposed. think. separate shell window for
each job.
>
> From: Paul Smith
>To: Jim Michaels
>Cc: "bug-make@gnu.org"
>Sent: Tuesday, April 30, 2013 11:23 PM
>Subject: Re: feature request: para
On Tue, 2013-04-30 at 17:20 -0700, Jim Michaels wrote:
> I wasn't digressing. I was explaining the point. the concept I am
> trying to present as a solution to the problem of making parallel
> stdin for --jobs in gnu make (which currenty doesn't work and is I
> guess single-threaded) is to make a
allel.html
>
> From: Howard Chu
>To: Jim Michaels ; "psm...@gnu.org"
>Cc: "bug-make@gnu.org"
>Sent: Tuesday, April 30, 2013 6:55 PM
>Subject: Re: feature request: parallel builds feature
>
>
>Jim Michaels wrote:
>>
>> I wasn't digre
Jim Michaels wrote:
what if you in your makefile are creating files from scratch using echo, based
on system configuration information?
I know I have to do that in order to create XML manifest files for resources
to compile and link in via resource compiler for windows builds.
echo writes to st
%.%extension%.manifest
there is more. there are if statements involved, etc.
currently, there is no manifest tool in the compiler set for mingw-w64 or
mingw. nothing is planned.
>____
> From: Howard Chu
>To: Jim Michaels ; "psm...@gnu.org"
>Cc: "bug-make@gnu.org"
>Sen
m Michaels
*Cc:* bug-make@gnu.org
*Sent:* Monday, April 22, 2013 10:56 AM
*Subject:* Re: feature request: parallel builds feature
On Mon, 2013-04-22 at 00:42 -0700, Jim Michaels wrote:
> it currently has a problem with stdin, because at this point there is
> only one o
pril 22, 2013 10:56 AM
>Subject: Re: feature request: parallel builds feature
>
>
>On Mon, 2013-04-22 at 00:42 -0700, Jim Michaels wrote:
>> it currently has a problem with stdin, because at this point there is
>> only one of those, only 1 of them gets it, and the others st
On Mon, 2013-04-22 at 00:42 -0700, Jim Michaels wrote:
> it currently has a problem with stdin, because at this point there is
> only one of those, only 1 of them gets it, and the others starve. so
> if your build needs stdin or creates files from the commandline using
> heredocs, you can't use it
On Tue, 2013-04-16 at 01:34 -0700, Jim Michaels wrote:
> I have been toying with this idea of parallel builds to gain project
> compile speed (reducing time to a fraction) for quite a while.
Can you explain the difference between what you're suggesting and the
existing --jobs (-j) feature availabl
feature request: parallelize make builds.
current problem: make is serial in nature. there is room for making it
series-parallel.
I have been toying with this idea of parallel builds to gain project compile
speed (reducing time to a fraction) for quite a while.
compiles seem to spend more
On 4.2.2013 01:09, Sebastian Pipping wrote:
> On 04.02.2013 00:13, Matěj Týč wrote:
>> On Ne, 2013-02-03 at 23:40 +0100, Sebastian Pipping wrote:
>>> To my understanding, it would have to be optional and off by default to
>>> not break other cases that are currently supported. Think of something
On 04.02.2013 00:13, Matěj Týč wrote:
> On Ne, 2013-02-03 at 23:40 +0100, Sebastian Pipping wrote:
>> To my understanding, it would have to be optional and off by default to
>> not break other cases that are currently supported. Think of something like
>>
>> tmp:
>> mkdir tmp
>>
>> tmp/fo
On Ne, 2013-02-03 at 23:40 +0100, Sebastian Pipping wrote:
> On 03.02.2013 23:20, Matěj Týč wrote:
> >> If that happens how about replacing
> >>
> >> $(MAKE) cache-foo
> >>
> >> by something like
> >>
> >> mkdir .lock 2>/dev/null || exit 0 ; \
> >> $(MAKE) cache-foo ; \
> >> ret=$$?
On 03.02.2013 23:20, Matěj Týč wrote:
>> If that happens how about replacing
>>
>> $(MAKE) cache-foo
>>
>> by something like
>>
>> mkdir .lock 2>/dev/null || exit 0 ; \
>> $(MAKE) cache-foo ; \
>> ret=$$?; \
>> rmdir .lock && exit $${ret}
>>
>> The idea is:
>>
>> - mkdir can
On Ne, 2013-02-03 at 00:45 +0100, Sebastian Pipping wrote:
> On 02.02.2013 18:38, Matěj Týč wrote:
> >> How about something like this?
> >>
> >> bar_deps = foo1 foo2
> >>
> >> bar: $(bar_deps)
> >>
> >> $(bar_deps):
> >>$(MAKE) cache-foo
> >>touch $@
> >>
> >> %:
> >>touch $@
>
On 02.02.2013 18:38, Matěj Týč wrote:
>> How about something like this?
>>
>> bar_deps = foo1 foo2
>>
>> bar: $(bar_deps)
>>
>> $(bar_deps):
>> $(MAKE) cache-foo
>> touch $@
>>
>> %:
>> touch $@
>
> I have also thought of that, but this can work well reliably only in the
> c
On So, 2013-02-02 at 18:14 +0100, Sebastian Pipping wrote:
> On 02.02.2013 16:19, Matěj Týč wrote:
> > [...]
>
> How about something like this?
>
> bar_deps = foo1 foo2
>
> bar: $(bar_deps)
>
> $(bar_deps):
> $(MAKE) cache-foo
> touch $@
>
> %:
> touch $@
>
> Now cac
On 02.02.2013 16:19, Matěj Týč wrote:
>> This is what I understand to be our current Makefile:
>>
>> bar_deps = foo1 foo2
>>
>> bar: $(bar_deps)
>>
>> $(bar_deps): | cache-foo
>>
>> %:
>> touch $@
> [..]
>
> Thank you for your quick help, your example indeed works, but it has one
> we
On So, 2013-02-02 at 00:22 +0100, Sebastian Pipping wrote:
> On 01.02.2013 16:18, Matěj Týč wrote:
> > ...
> >
> > Consider a server process that can execute commands and that can load
> > (huge) data into cache to spped the execution up. Loading the data is a
> > make task and a target file cache
On 01.02.2013 16:18, Matěj Týč wrote:
> Hi,
> I have noticed that if we have a target that has prerequisities, if
> those prerequisities are missing and I want to make the target, then
> even if the target file exists, prerequisities are remade if possible
> and then, consequently, the target has t
Hi,
I have noticed that if we have a target that has prerequisities, if
those prerequisities are missing and I want to make the target, then
even if the target file exists, prerequisities are remade if possible
and then, consequently, the target has to be remade, too, since its
prerequisity is
Den onsdagen den 7:e november 2012 skrev Paul Smith:
>
> There is already a new $(file ...) function in the current CVS version
> of GNU make, which writes to a file.
>
That is the best response any feature request can get! Its already
implemented. :-)
Thanks
On Wed, 2012-11-07 at 14:39 +0100, Fredrik Öhrström wrote:
> To get around this particular problem I implemented a workaround
> marcro called ListPathsSafely that writes the contents of a variable
> to disk.
There is already a new $(file ...) function in the current CVS version
of GNU make, which
When I designed the new makefiles for the OpenJDK project
(http://openjdk.java.net/projects/build-infra/guide.html)
The first and foremost problem was,
how to efficiently compile Java software from makefiles.
That included:
1 not wanting to spawn a jvm, to check if any java sources had changed.
Hello,
Please make .NOTPARALLEL to accept prerequisites list, with meaning that these
targets should not be build in parallel.
This is similar to to ClearCase make, described there:
http://publib.boulder.ibm.com/infocenter/cchelp/v7r0m0/index.jsp?topic=/com.ibm.rational.clearcase.books.cc_buil
On 08/11/2012 11:49 AM, Tim Murphy wrote:
> For the sake of understanding you properly, if you can detect, remove and
> add targets then 'replacing the recipe silently' is just these three
> operations in sequence, right?
>
No. A target might be defined, but might have or not have an associated
re
For the sake of understanding you properly, if you can detect, remove and
add targets then 'replacing the recipe silently' is just these three
operations in sequence, right? We can already add targets but not the
other two.
Cheers,
Tim
On Aug 11, 2012 10:53 AM, "Stefano Lattarini"
wrote:
> On
On 08/11/2012 07:36 AM, Tim Murphy wrote:
> This is a different thing but I'd have had great use for a way to tell if a
> target had been defined previously. Had to use variables to do it which
> used a lot of memory and it was a total waste because make has the
> information already.
>
I dimly rem
This is a different thing but I'd have had great use for a way to tell if a
target had been defined previously. Had to use variables to do it which
used a lot of memory and it was a total waste because make has the
information already.
Perhaps the ability to detect if a target is defined and anoth
On 08/11/2012 01:27 AM, David Boyce wrote:
> On Fri, Aug 10, 2012 at 2:38 PM, Stefano Lattarini
> wrote:
>> I have no answer for that, lacking any knowledge about GNU make
>> internals; I guess the make developers here will be in a better
>> position to answer my question.
>
> Yes, and I hope you
On Fri, Aug 10, 2012 at 2:38 PM, Stefano Lattarini
wrote:
> I have no answer for that, lacking any knowledge about GNU make
> internals; I guess the make developers here will be in a better
> position to answer my question.
Yes, and I hope you get your feature. But consider that auto-tools are
tr
guess in the end it
will boil down to: is it be easier to consistently use the idiom
above, or to enhance GNU make to implement my feature request?
I have no answer for that, lacking any knowledge about GNU make
internals; I guess the make developers here will be in a better
position to answer my
Even with GNU make as it stands, couldn't you emit your rules in the
form of variables, override them at will, and eval() them at the end?
E.g.
define ruleA
version 1
endef
then later...
define ruleA
version 2
endef
$(eval $(call ruleA,...))
-David Boyce
On Fri, Aug 10, 2012 at 12:36 PM, Stef
In some situations, it would be very useful to be able to override
already-defined rules for a target without having GNU make complaining
about the override.
For example, when writing a "library" of makefiles recipes, organized as
a set of makefile fragments to be included by a "master" (user-writ
On Sat, Mar 3, 2012 at 6:30 PM, Odne Hellebø wrote:
...
> I have A.java which uses B.java and thus the rule becomes this A.java B.class>, but I don't need to recompile A.java if B.class is changed,
> I just need B.class to be there with the features I use in A.class. So what
> I suggest is that w
Hey,
I know this probably isn't the right place to ask for a new feature, but
I couldn't find any decent places to do it, so here goes. I recently
started using make for a project in java and I know that Java isn't
supported by default, but I do believe that this is something that will
benefi
Hi,
I have stumbled upon a thread from 2009 in your archive that mentioned
.PHONY .SECONDARY targets. This would suggest I am not the only
person that requires this functionality that was removed through a fix
made to address another problem. I have a proposed solution to
reintroduce the functio
On Fri, 2009-10-09 at 16:56 +0300, Andrei Kopats wrote:
> Hello.
>
> Today I had a problem with GNU Make - it has key -j for control max jobs
> count.
> User can set particular count, or infinite.
> With particular user must define count, but, user not always know the best.
> With infinite - syst
Hello.
Today I had a problem with GNU Make - it has key -j for control max jobs
count.
User can set particular count, or infinite.
With particular user must define count, but, user not always know the best.
With infinite - system could get frozen. Today I built project on system
with 2 Gb of R
Hello,
the GNU GCC and Binutils packages have the following feature: when
compiled for cross compilation, e.g., for
TARGET=arm-none-eabi
they are compiled with the names $TARGET-gcc, $TARGET-nm, etc. Various
programs such as the compiler driver, the linker etc. automatically
change their
Please choose just one of the make mailing lists to send a particular
email to. Thanks!
--
---
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org http://make.
I would like to request a new option to be added. When
deciding on uptodateness of a target it should render
make sensitive to a time-stamp on a link rather than a
file this link points to. Another possibility is to
render make sensitive to the time-stamp of a link or a
file it points to whichever
%% Dave Yost <[EMAIL PROTECTED]> writes:
dy> I have two sets of isomorphic sources. Let's say one is in lisp
dy> syntax and the other is in Java syntax. Two different sets of
dy> programmers, one likes lisp syntax; the other likes Java syntax.
dy> I've written a program that automaticall
I have two sets of isomorphic sources. Let's say one is in lisp syntax and the other
is in Java syntax. Two different sets of programmers, one likes lisp syntax; the
other likes Java syntax.
I've written a program that automatically syncs the two sets of files, but I can't get
make to invoke
Martin Quinson wrote:
> Others, I did report this to the debian BTS and not here directly to benefit
> of its sorted archiving mechanism. If you want more context, please check
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=206746
I agree with Manoj that watching a file system should not be ma
[EMAIL PROTECTED] wrote:
>
> On Wed, 27 Aug 2003 07:37:46 -0400, Noel Yap <[EMAIL PROTECTED]> said:
>
> >> I would like a way to list all dependencies and subdependencies of
> >> a given target to avoid the recursive shell function hackism I
> >> currently have to do when using "make -pnq".
>
>
encies in complex build environments that are only
> peripherally relevant in this feature request. The solution proposed
> in the paper, a single, humongous Makefiule (even if it is practical,
> which I personally think is only practical for small projects), would
> still hav
t; >
> > This was a feature request from a Debian user.
> >
> > I would like a way to list all dependencies and subdependencies of a
> > given target to avoid the recursive shell function hackism I
> > currently have to do when using "make -pnq".
>
Hello,
I'm the one which asked for this feature in the debian bug tracking system.
Manoj, thanks for taking care of this bug that way and keeping me in CC. And
sorry for not steping in the discution sooner, I was away from mails.
Others, I did report this to the debian BTS and not here directly
and any
external implementation would have to track the algorithm make uses,
so yes, I do think make is the best place to put this feature in.
> What I've done in the past is to have each project to supply a
> makefile that lists its dependencies on other projects. Each
> project wo
cking this feature
set in make.
> Anyway, since this is open source, your always welcome to contribute
> a patch. Otherwise, there's a very small possibility that someone
> else will create the patch for you.
*Shrug*. I know how free software works. This is why this
though this is
> the hack one must resort to, for the moment, lacking this feature
> set in make.
This is true unless you follow the above example.
> *Shrug*. I know how free software works. This is why this is
> labelled a "feature request", not a feature dema
On Wed, Aug 27, 2003 at 12:12:38AM -0500, Manoj Srivastava wrote:
> Hi,
> [Please retain the CC to [EMAIL PROTECTED] so
>that the Debian Bug Tracking system can record your input]
>
> This was a feature request from a Debian user.
>
> I would l
am justusing a simple Makefile.
> Sorry for not checking the URL. If you're still interested in the
> paper, googling for "recursive make harmful" turns up many links.
OK. But I think we are being bitten by semantics -- the paper
refers to inefficiencies in comple
On Wed, 27 Aug 2003 07:37:46 -0400, Noel Yap <[EMAIL PROTECTED]> said:
>> I would like a way to list all dependencies and subdependencies of
>> a given target to avoid the recursive shell function hackism I
>> currently have to do when using "make -pnq".
> IMHO, don't use recursive make:
> http:
1 - 100 of 114 matches
Mail list logo
