From: Eli Zaretskii <eliz@is.elta.co.il>
To: "J.T. Conklin" <jtc@redback.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: make capabilities
Date: Wed, 21 Mar 2001 15:59:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010304080237.12520B@is> (raw)
In-Reply-To: <5mofvlqrpv.fsf@jtc.redback.com>
On 1 Mar 2001, J.T. Conklin wrote:
> Is it safe to assume that all versions of make used to build GDB will
> understand the ${FOO:.c=.o} construct? It does not appear to be used
> elsewhere in the GDB or binutils trees, so it is possible (maybe even
> likely) that they do not. But I do not know how to solve a problem
> without it.
>
> The problem is the "lint" target:
>
> lint: $(LINTFILES)
> $(LINT) $(INCLUDE_CFLAGS) $(LINTFLAGS) $(LINTFILES) \
> `echo $(DEPFILES) | sed 's/\.o /\.c /g'`
>
> If srcdir != objdir, lint is not able to find the source files. This
> can be fixed if the rule is re-written as such:
>
> lint: $(LINTFILES) $(DEPFILES:.c=.o)
> $(LINT) $(INCLUDE_CFLAGS) $(LINTFLAGS) $^
>
> Thoughts?
I can suggest two thoughts:
1. The current Emacs distribution uses $(FOO:.x=.y) in its Makefile's.
While this version is not yet released, its pretest was tested on
many different systems, and none failed to build it.
2. However, it _is_ known that not all versions of Make support that
construct. If you want to be 100% portable, you can edit .c into .o
with `sed` invocation in the rule's commands.
next prev parent reply other threads:[~2001-03-21 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-21 15:59 J.T. Conklin
2001-03-21 15:59 ` Eli Zaretskii [this message]
2001-03-21 15:59 ` J.T. Conklin
2001-03-21 15:59 ` Eli Zaretskii
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.SUN.3.91.1010304080237.12520B@is \
--to=eliz@is.elta.co.il \
--cc=gdb@sourceware.cygnus.com \
--cc=jtc@redback.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