public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus dot milleder at generali dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/35458] Dependency generation (-M) does not quote '#' in filenames
Date: Tue, 04 Mar 2008 14:10:00 -0000	[thread overview]
Message-ID: <20080304141000.8023.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35458-15857@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from markus dot milleder at generali dot at  2008-03-04 14:10 -------
(In reply to comment #2)
> Please note that quoting # in makefiles is not portable, but only supported
> by some make implementations.  For example, with
>    foo: a\#b
>    bar: c#d
> 
> AIX make will assume 'foo' depends on 'a\', and 'bar' on 'c'.
> Likewise HP-UX make.  Consequently, both of these make's will error out on
> either line of:
>   a#b:
>   a\#b:
> 
So it seems to me the patch is an improvement for make versions that understand
quoting and does not worsen the situation for those that do not, i.e. files
containing # are broken on e.g. AIX without the patch and with it.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35458


  parent reply	other threads:[~2008-03-04 14:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-04 13:36 [Bug preprocessor/35458] New: " markus dot milleder at generali dot at
2008-03-04 13:38 ` [Bug preprocessor/35458] " markus dot milleder at generali dot at
2008-03-04 13:54 ` rwild at gcc dot gnu dot org
2008-03-04 14:10 ` markus dot milleder at generali dot at [this message]
2008-03-06 18:10 ` tromey at gcc dot gnu dot org
2008-03-06 18:16 ` tromey at gcc dot gnu dot org

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=20080304141000.8023.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).