public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Berlin <dberlin@dberlin.org>
To: Toon Moene <toon@moene.indiv.nluug.nl>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	Diego Novillo <dnovillo@redhat.com>
Subject: Re: [tree-ssa] Fix bootstrap failure
Date: Sun, 30 Nov 2003 19:10:00 -0000	[thread overview]
Message-ID: <012406BB-2365-11D8-BE3D-000A95DA505C@dberlin.org> (raw)
In-Reply-To: <3FCA37F3.7010703@moene.indiv.nluug.nl>


On Nov 30, 2003, at 1:33 PM, Toon Moene wrote:

> Daniel Berlin wrote:
>>>
>>> Fixed with
>>>
>>>     * Makefile.in (GTFILES): Fix typo in tree-alias-common.c
>>>     entry.
>
>> Update again, it was already fixed :P
>
> Talking about "fixed" - as far as I can see your PTA only takes effect 
> if HAVE_BANSHEE is defined during compilation.  Now, despite of the 
> fact that libbanshee is built correctly (and used !) in my bootstrap 
> (powerpc-unknown-linux-gnu), I still don't see a -DHAVE_BANSHEE on the 
> compile lines ..

Because it gets thrown into gcc's config.h.

Toplevel configure automatically passes --with-libbanshee to gcc 
configure if libbanshee exists.

(of course, there is no --without-libbanshee flag right now for 
toplevel configure, you have to remove the libbanshee dir for it to not 
pass --with-libbanshee, but at least *that* works)

  reply	other threads:[~2003-11-30 18:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 15:11 Diego Novillo
2003-11-30 15:51 ` Daniel Berlin
2003-11-30 19:09   ` Toon Moene
2003-11-30 19:10     ` Daniel Berlin [this message]
2003-11-30 19:12       ` Toon Moene
2003-11-30 19:31         ` Toon Moene
2003-11-30 19:56           ` Daniel Berlin
2003-11-30 21:01             ` Toon Moene

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=012406BB-2365-11D8-BE3D-000A95DA505C@dberlin.org \
    --to=dberlin@dberlin.org \
    --cc=dnovillo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=toon@moene.indiv.nluug.nl \
    /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).