From: Gary Benson <gbenson@redhat.com>
To: rhug-rhats@sources.redhat.com
Subject: Re: [tromey@redhat.com (Tom Tromey)] FAIL: rhug build on Sat May 3 03:26:43 MDT 2003
Date: Thu, 22 May 2003 16:44:00 -0000 [thread overview]
Message-ID: <20030522164403.GE16272@redhat.com> (raw)
In-Reply-To: <1053620895.3465.797.camel@escape>
Anthony Green wrote:
> I got it. I am building outside of my srcdir. I think this needs a
> "$(srcdir)/" or two somewhere...
>
> .resource-stamp: $(XERCES_PROP_S)
> @for x in $(XERCES_PROP_S); do \
> if [ ! -f $$x.o -o $$x -nt $$x.o ]; then \
> $(top_srcdir)/mkinstalldirs `dirname $$x`; \
> cp -a $$x $$x.java; \
> echo $(LTGCJCOMPILE) -o $$x.o -c $$x \
> -Wc,--resource,`echo $$x | sed "s/.*\/src\///g"`; \
> $(LTGCJCOMPILE) -o $$x.o -c $$x.java \
> -Wc,--resource,`echo $$x | sed "s/.*\/src\///g"`; \
> rm -f $$x.java; \
> fi; \
> done
> @touch $@
>
> Maybe just "cp -a $(srcdir)/$$x $$.java; \"? I don't understand the
> "[ ! -f ... " etc part. Does this need a $(srcdir) as well?
The [ ! -f $$x.o -o $$x -nt $$x.o ] is basically to make it only build
the .o file when it isn't there or the .properties file is newer than
it (like what make should be doing).
Basically, I think that every $$x.o and $$x.java need a $(srcdir), but
$$x on its own does not.
Gary
next prev parent reply other threads:[~2003-05-22 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-03 22:16 Tom Tromey
2003-05-06 13:24 ` Anthony Green
2003-05-21 7:31 ` Anthony Green
2003-05-21 9:38 ` Gary Benson
2003-05-21 15:46 ` Anthony Green
2003-05-21 16:44 ` Gary Benson
2003-05-21 19:15 ` Anthony Green
[not found] ` <20030522092501.GB15469@redhat.com>
[not found] ` <1053620895.3465.797.camel@escape>
2003-05-22 16:44 ` Gary Benson [this message]
2003-05-22 18:48 ` Anthony Green
2003-05-23 8:42 ` Gary Benson
2003-05-21 13:01 ` Stefan Seefeld
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=20030522164403.GE16272@redhat.com \
--to=gbenson@redhat.com \
--cc=rhug-rhats@sources.redhat.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).