From: "Avraham H. Fraenkel" <avraham.fraenkel@comMATCH.com>
To: Brian Pollard <b_pollard@trillium.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: problem with make
Date: Wed, 16 Aug 2000 00:01:00 -0000 [thread overview]
Message-ID: <Pine.GHP.4.10.10008160947190.14548-100000@tctohp14> (raw)
In-Reply-To: <0E7AA454E229D411A1CB0090274661FF550314@gaea.trillium.com>
You can do :
1) put the remark in the line before.
in such case no trilling balnks are added to the macro.
2) if you are using GNU make , there is a function called strip, so you
can do:
$(strip $(hehe))/mine.h
Avraham
-------------------------------------
Avraham H. Fraenkel
comMATCH: www.comMATCH.com
-------------------------------------
On Tue, 15 Aug 2000, Brian Pollard wrote:
> when using a make file, assignment statements such as:
>
> hehe=. #some comment
>
> $(hehe)/mine.h
> hehe stores ". " instead of "./"
>
> this causes problems when accessing something such as:
>
>
> because it is interpreted as ". /mine.h"
>
>
> I would guess that the source code needs to be modified, any suggestions???
>
> Thanks,
> Brian
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-08-16 0:01 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-15 10:37 Brian Pollard
2000-08-16 0:01 ` Avraham H. Fraenkel [this message]
2000-08-16 4:34 ` Lassi A. Tuura
-- strict thread matches above, loose matches on Subject: below --
2013-06-05 7:00 Problem " Lange, Jan-Erik
2013-06-05 7:31 ` Corinna Vinschen
2002-04-22 0:50 problem " Jason Morgan
[not found] <009001c17d8a$9ad87380$9a5f07d5@BRAMSCHE>
2001-12-05 5:26 ` Earnie Boyd
[not found] <200103150254.SAA09865@cygnus.com>
2001-03-14 19:04 ` Problem " Christopher Faylor
2001-03-14 18:54 Mark Paulus
2000-08-17 9:43 problem " Brian Pollard
2000-08-17 23:26 ` Lassi A. Tuura
2000-08-16 15:58 Noel L Yap
2000-08-16 15:23 Noel L Yap
2000-08-16 13:12 Heribert Dahms
2000-08-16 23:01 ` Lassi A. Tuura
1999-06-10 4:56 Problem " Brown, Kim
1999-06-30 22:10 ` Brown, Kim
1999-06-09 23:12 N8TM
1999-06-30 22:10 ` N8TM
1999-06-09 12:17 Phil Edwards
1999-06-30 22:10 ` Phil Edwards
1999-06-09 9:43 Brown, Kim
1999-06-09 12:26 ` Don Sharp
1999-06-30 22:10 ` Don Sharp
1999-06-30 22:10 ` Brown, Kim
1999-06-09 9:36 Blob, Dave
1999-06-30 22:10 ` Blob, Dave
1998-08-06 14:36 problem " Stuart
1998-08-07 10:39 ` Stuart
1998-08-09 11:19 ` Pete Jordan
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=Pine.GHP.4.10.10008160947190.14548-100000@tctohp14 \
--to=avraham.fraenkel@commatch.com \
--cc=b_pollard@trillium.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).