Hello,
The intent of the default rule is to make it easy to handle object files
or libs I think. So it makes sense that for you the file is assumed to
be an object file and is passed to the link line.
For anything other than very simple cases you will make your own rules.
1.
Do you actually
Follow-up Comment #4, bug #23273 (project make):
patch attached
Posted this already on make mailing list, sorry for duplicate info, was not
sure about adding patch here.
As simple as possible I think.
Don't call to fatal so that easter egg error text is clear of adornment.
Exits using die(2) as
Sorry I'm not sure about where to submit a patch.
http://savannah.gnu.org/projects/make/ ?
I keep on thinking about this since I saw your request Joachim!
Now maybe I can lay it to rest whether this is used or not.
As simple as possible I think.
Don't call to fatal so that easter egg error tex
Georg-Johann Lay wrote:
> make clean
echo clean
clean
That proves that your make does accept the command-line target.
So it must be the shell or ?? something.
Not a problem with make I think.
your Makefile and sh -c 'make clean' call works okay within cygwin for me:
$ sh -c 'make clean'
ec
Oh dear. Sorry people. I was of course being a bit silly when talking about
make -j 16385!
Howard Chu wrote:
[EMAIL PROTECTED] wrote:
Perhaps... On the other hand, if you're using -j 65K, why not
just -j? Does you build even have 65K jobs?
of course I do not use -j65k ! :-O :-)
Very good
Paul Smith wrote:
On Tue, 2007-01-09 at 10:32 +, James Coleman wrote:
Ken Takusagawa wrote:
For reasons I haven't completely triaged yet, I've been having my
parallel makes die with
"read jobs pipe: Resource temporarily unavailable. Stop."
All memory on machine mi
Ken Takusagawa wrote:
For reasons I haven't completely triaged yet, I've been having my
parallel makes die with
"read jobs pipe: Resource temporarily unavailable. Stop."
All memory on machine might be used up (real memory + all swap).
e.g. we get this: virtual memory exhausted: Resource temp
libumem on solaris is quite good, you can run it no problem without dbx
or the other sun tools. Not quite as good as valgrind I believe though
I don't have experience with valgrind.
Here's another url with good examples of use of libumem:
http://access1.sun.com/techarticles/libumem.html
Very ea
I definately agree it is a bug fix. (that changes behaviour :) )
Thanks Paul,
James.
Paul D. Smith wrote:
I'll add a note about this as it's a behavior change, even though I
consider it a bug fix.
___
Bug-make mailing list
Bug-make@gnu.org
htt
Hi Paul,
Build & install on solaris 2.9 (sparc) using gcc (3.4.5) looks fine. make
check all good.
Parallel builds for making make as well as building our stuff.
I see one thing that might be an issue. Not critical I think.
But it's a change in behaviour anyway and I'd like to run it by you
Hello,
8.8 The eval Function has an example of using eval, foreach, ... and I am
planning on using something a bit like that myself. The example provided
has a two problems and I have a fixed version
(tested on GNU Make 3.80 on solaris).
You might like to incorporate this fixed version in the m
11 matches
Mail list logo
