From: Geert Bosch <bosch@gnat.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: gcc mailing list <gcc@gcc.gnu.org>
Subject: Re: Build problem on ia64 (reverting patch on 3.4 branch)
Date: Fri, 24 Sep 2004 20:20:00 -0000 [thread overview]
Message-ID: <E4950175-0E5C-11D9-9684-000A959A128E@gnat.com> (raw)
In-Reply-To: <20040923213953.GB7247@lucon.org>
On Sep 23, 2004, at 17:39, H. J. Lu wrote:
> You also need to regenerate top level Makefile.in.
Doesn't seem to work: the variable gets replaced with nothing:
> lang.stageprofile: ada.stageprofile
> lang.stagefeedback: ada.stagefeedback
>
> # Set up library path if needed.
>
>
> # per-language makefile fragments
> ifneq ($(LANG_MAKEFRAGS),)
> include $(LANG_MAKEFRAGS)
> endif
Do you know where this might have gone wrong?
next prev parent reply other threads:[~2004-09-24 19:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-22 13:20 Build problem on ia64 Zdenek Dvorak
2004-09-22 13:39 ` Paolo Carlini
2004-09-22 16:33 ` H. J. Lu
2004-09-23 20:04 ` Build problem on ia64 (reverting patch on 3.4 branch) Geert Bosch
2004-09-23 20:13 ` H. J. Lu
2004-09-23 21:40 ` Geert Bosch
2004-09-24 0:05 ` H. J. Lu
2004-09-24 0:09 ` H. J. Lu
2004-09-24 20:20 ` Geert Bosch [this message]
2004-09-24 20:36 ` H. J. Lu
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=E4950175-0E5C-11D9-9684-000A959A128E@gnat.com \
--to=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.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).