public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Korn <dave.korn.cygwin@googlemail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
	  "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: What precisely is the status of ppl/cloog anyway?
Date: Wed, 06 May 2009 16:03:00 -0000	[thread overview]
Message-ID: <4A01B763.3020001@gmail.com> (raw)
In-Reply-To: <4A01AE78.1040604@gnu.org>

Paolo Bonzini wrote:
> Dave Korn wrote:
>>   Sorry to have to ask a dumb question, but it's not clear to me and I'm not
>> having a lot of luck searching recent list posts:
>>
>>   Are cloog and ppl now mandatory requirements for building gcc, or are they
>> still optional extras?
> 
> Optional.
> 
> Paolo

  Ah, so if there's no --with specified, and no in-tree version, we can't just
fall back on defaulting to $prefix, we need to actually do a proper search to
see if there's a cloog/ppl install there and decide whether to build it or
not.  Hmm, the version check will need to be skipped in that case.

  Or if no --with-cloog option is given, should the default be to assume
--with-cloog=no, rather than try and guess?

[ All said here also applies to --with-ppl pro rata. ]

    cheers,

  reply	other threads:[~2009-05-06 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-06 15:14 Dave Korn
2009-05-06 15:36 ` Paolo Bonzini
2009-05-06 16:03   ` Dave Korn [this message]
2009-05-06 17:26     ` [PATCH] Fix bootstrap when no --with-ppl/--with-cloog [was Re: What precisely is the status of ppl/cloog anyway?] Dave Korn

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=4A01B763.3020001@gmail.com \
    --to=dave.korn.cygwin@googlemail.com \
    --cc=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.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).