public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pme@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gin@mo.msk.ru, pme@gcc.gnu.org Subject: Re: libstdc++/5095: broken $(MAKEFLAGS) Date: Wed, 10 Apr 2002 10:08:00 -0000 [thread overview] Message-ID: <20020410170759.21034.qmail@sources.redhat.com> (raw) Synopsis: broken $(MAKEFLAGS) State-Changed-From-To: open->feedback State-Changed-By: pme State-Changed-When: Wed Apr 10 10:07:58 2002 State-Changed-Why: I don't fully understand it either. I think I see what's happening, but I don't see how it could. gin@mo.msk.ru, is this still happening for you? Lots of changes have been made since 3.0.2. In particular, I don't see how this can happen with the default "gmake bootstrap-lean" and no other arguments or overrides. Nobody else has experienced this with the default setup. The problem would seem to occur when trying to override a makefile variable on the command line; this gets tricky when recursing. The construct $(foo) is simply a variable in makefiles, but in a POSIX Bourne shell it is the same as writing `foo` which means something very different. A cleaner makefile would use ${foo} in all cases, because brace-expansion means the same thing (variable expansion) in makefiles as it does in shells. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5095
next reply other threads:[~2002-04-10 17:08 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-10 10:08 pme [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-31 18:05 pme 2002-04-18 22:26 Phil Edwards 2002-04-09 14:23 bkoz 2001-12-12 9:16 Golubev I. N.
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=20020410170759.21034.qmail@sources.redhat.com \ --to=pme@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=gin@mo.msk.ru \ /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: linkBe 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).