From: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, gofrontend-dev@googlegroups.com
Subject: Re: libgo patch committed: Add SPARC RTEMS specific file
Date: Sun, 23 Jan 2011 13:29:00 -0000 [thread overview]
Message-ID: <20110123084505.GB3563@gmx.de> (raw)
In-Reply-To: <mcrr5c49ors.fsf@google.com>
* Ian Lance Taylor wrote on Sun, Jan 23, 2011 at 06:23:35AM CET:
> Ralf Wildenhues writes:
> > * Ian Lance Taylor wrote on Sat, Jan 22, 2011 at 03:01:40AM CET:
> >> If anybody knows of a simple way to use automake with files
> >> that may or may not exist, please let me know. I'd prefer to avoid
> >> configure tests since they separate the test and the use in a way that I
> >> find hard to maintain over time.
> > if COND
> > foo_SOURCES += bar.go
> > endif
> >
> > or you can
> >
> > foo_SOURCES = $(computed)
> > EXTRA_foo_SOURCES = bar1.go bar2.go bar3.go
> Thanks, I know about those possibilities, but they aren't what I want,
> because they require me to determine whether the files exist in the
> configure script and to then use that determination in the Makefile. I
> don't want to split things up that way. I want to say something like
>
> foo_SOURCES = `test -f f.c && echo f.c`
That doesn't work with the current dependency tracking machinery; it
needs to know the list of files at automake time in order to include
the relevant .Po and .Plo files in the Makefile.
This is something we may be able to address once we have machinery in
place to emit GNU make-specific code, and this Makefile is required to
work with GNU make only.
Sorry,
Ralf
next prev parent reply other threads:[~2011-01-23 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-22 3:06 Ian Lance Taylor
2011-01-22 10:18 ` Ralf Wildenhues
2011-01-23 10:35 ` Ian Lance Taylor
2011-01-23 11:27 ` Ian Lance Taylor
2011-01-23 12:52 ` Ian Lance Taylor
2011-01-23 13:29 ` Ralf Wildenhues [this message]
2011-01-24 0:03 ` [gofrontend-dev] " Joel Sherrill
2011-01-24 20:43 ` Ian Lance Taylor
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=20110123084505.GB3563@gmx.de \
--to=ralf.wildenhues@gmx.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@google.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).