I have the following Makefile:
foo: bar
@echo While building $@ MACRO = ${MACRO}
foo: MACRO += foo_specific
bar:
@echo While building $@ MACRO = ${MACRO}
bar: MACRO += bar_specific
MACRO = common
I would expect to get th
Hi,
I am trying to configure GNU make from cygwin and ./configure doesn't run.
I have attached the cygwin console capture with the error. I have
installed this two years ago without any problems. Any comments will be
appreciated.
Thanks
Nik Faroughi
[EMAIL PROTECTED]
___
> Date: Fri, 3 Aug 2007 14:52:53 -0700 (PDT)
> From: [EMAIL PROTECTED]
>
> I am trying to configure GNU make from cygwin and ./configure doesn't run.
> I have attached the cygwin console capture with the error.
I see no attachments.
___
Bug-make maili
> Date: Fri, 3 Aug 2007 14:55:15 -0700 (PDT)
> From: [EMAIL PROTECTED]
>
> oops, here is the attached console capture
It's much better to send this as plain text (you can capture it with
`tee' or even by copying and pasting the contents into your mailer).
My crystal ball says that somehow the co
On Fri, 2007-08-03 at 12:45 -0700, Samuel Klatchko wrote:
> The real use case is when I have a Makefile that is building both an
> shared object and an executable that uses it. I want to factor LDLIBS
> into common libraries that both use and specific libraries that are
> only for the shared objec
On Fri, 2007-08-03 at 12:45 -0700, Samuel Klatchko wrote:
> Is this a bug or am I misunderstanding how target specific variables
> work.
The latter.
See the section in the GNU make manual 'Target-specific Variable Values'
and read the part starting with "There is one more special feature of
targe
On Sat, Aug 04, 2007 at 01:08:54AM +0300, Eli Zaretskii wrote:
>> Date: Fri, 3 Aug 2007 14:55:15 -0700 (PDT)
>> From: [EMAIL PROTECTED]
>>
>> oops, here is the attached console capture
>
>It's much better to send this as plain text (you can capture it with
>`tee' or even by copying and pasting the
