public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Earnie Boyd <earnie_boyd@yahoo.com>
To: Kevin Wright <kwright@uk.mdis.com>,
	Cygwin <cygwin@sourceware.cygnus.com>
Subject: RE: B20.1: make dependencies broken
Date: Thu, 27 Jan 2000 11:38:00 -0000	[thread overview]
Message-ID: <20000127175330.4654.qmail@web123.yahoomail.com> (raw)

Hmm...  Is you Makefile example correct?  I redid it like this:

------------------------------
NTTOOLSDIR = /tmp

NTTOOLS = f1.bat \
          f2.bat

All: $(NTTOOLS)

$(NTTOOLS): % : $(NTTOOLSDIR)/%
        # making $@ due to $?
        cp $? $@
--------------------------------

I then did 

mkdir /tmp/maketest
cd /tmp/maketest
create above Makefile
touch /tmp/f1.bat /tmp/f2.bat
make
       This gave me the expected results.
touch /tmp/f2.bat
make
       This gave me the expected results.
touch /tmp/f1.bat
make
       This gave me the expected results.
make
       Everything current, great, that was the expected result.
cd ..
make -f maketest/Makefile
       Everything current, great, that was the expected result.

Earnie.

--- Kevin Wright <kwright@uk.mdis.com> wrote:
> I tried adding
> .SUFFIXES: .bat
> and it didn't make any difference.
> 
> Kevin.
> 
> > 
> > Ok.  You problen with .bat is that it is an suffix that isn't a 
> > default one. 
> > What happens if you add .SUFFIXES .bat?
> > 
> > Earnie.
> > 
> > > > > I've found the following problem with make on B20.1.
> > > > > Try the following makefile:
> > > > > ------------------------------
> > > > > NTTOOLSDIR = /tmp
> > > > >
> > > > > NTTOOLS = $(NTTOOLSDIR)/f1.bat \
> > > > >           $(NTTOOLSDIR)/f2.bat
> > > > >
> > > > > All: $(NTTOOLS)
> > > > >
> > > > > $(NTTOOLS): $(NTTOOLSDIR)/%: %
> > > > >
> > > > > $(NTTOOLS):
> > > > >         # making $@ due to $?
> > > > >         cp $? $@
> > > > > --------------------------------
> > > > >
> > > > > now touch f1.bat f2.bat
> > > > >
> > > > >
> > > > > make always reports:
> > > > > make: Nothing to be done for `All'.
> > > > >
> > > > > Removing the .bat extension on f1/f2 fixes the problem.
> > > > > Removing the second file from NTTOOLS fixes the problem.
> > > > >
> > > > > This all worked fine on B17.
> > > > >
> > > > > I'm using NT4 SP5
> > > > >
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
> 
> 
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

             reply	other threads:[~2000-01-27 11:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-27 11:38 Earnie Boyd [this message]
2000-01-28  4:15 ` Kevin Wright
  -- strict thread matches above, loose matches on Subject: below --
2000-01-28  6:31 Earnie Boyd
2000-01-28  8:58 ` Kevin Wright
2000-01-26 12:00 Earnie Boyd
2000-01-27  7:09 ` Kevin Wright
2000-01-26  6:59 Earnie Boyd
2000-01-26  9:29 ` Kevin Wright
2000-01-26  6:34 Kevin Wright

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20000127175330.4654.qmail@web123.yahoomail.com \
    --to=earnie_boyd@yahoo.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=kwright@uk.mdis.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).