public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Wilson <David.Wilson@MessagingDirect.com>
To: cygwin@sourceware.cygnus.com
Cc: David.Wilson@MessagingDirect.com
Subject: B20.1: problem with make and multiple absolute targets
Date: Tue, 31 Aug 1999 23:49:00 -0000	[thread overview]
Message-ID: <16756.934911474@MessagingDirect.com> (raw)
Message-ID: <19990831234900.ho889NqUyUws2eq-WVt0enfzmlhf4o2miIa6i7zGJRA@z> (raw)

We have found a problem with B20.1 make (GNU 3.75 port) for which we can find 
no workaround. The problem arises when one has a multiple target dependency 
and some of the file names start with '/'. This is in UNIX mode.

Here is a simple Makefile that exhibits the problem:

	all: file1 /file2

	file1 /file2:
		echo $@

If the '/' is removed from the front of file2 in both cases, the result is as 
expected. No problem is found with GNU make 3.75 built on Solaris.

The output from make -p seems to indicate that the space + '/' results in 
names being paired. So, with

	/file1 /file2 /file3 /file4:
		echo $@

you get references to

	/file1 /file2:
		echo $@

	/file3 /file4:
		echo $@

in the make -p output.

I see evidence of GMU make 3.77 ports for the Cygnus environment. Where can 
one get these from? For our purposes make only needs to operate in UNIX mode, 
and //c/... type names are not required.

David Wilson                          David.Wilson@MessagingDirect.com
MessagingDirect Ltd.                             Tel: +44 181 332 9091
http://www.messagingdirect.com                   Fax: +44 181 332 9019



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

             reply	other threads:[~1999-08-31 23:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-17 10:38 David Wilson [this message]
1999-08-17 10:57 ` Glenn Spell
1999-08-21 16:15   ` Michael Hirmke
1999-08-31 23:49     ` Michael Hirmke
1999-08-31 23:49   ` Glenn Spell
1999-08-31 23:49 ` David Wilson

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=16756.934911474@MessagingDirect.com \
    --to=david.wilson@messagingdirect.com \
    --cc=cygwin@sourceware.cygnus.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).