public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52378] Can't build most recent svn version, i.e., trunk 4.7.0
Date: Sat, 25 Feb 2012 08:06:00 -0000	[thread overview]
Message-ID: <bug-52378-4-0hm6dfgkNM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52378-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52378

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |WAITING
   Last reconfirmed|                            |2012-02-25
     Ever Confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-02-25 07:46:51 UTC ---
>./configure 

I bet this is just a problem with you building in the src directory.  This is
not always supported and not always 100% working.  Can you try building in an
object directory?

Also do you have flex since that is required while building from subversion
(but not from the release tarballs)?


  reply	other threads:[~2012-02-25  7:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-25  7:47 [Bug target/52378] New: Can't build most recent svn version list at qtrac dot plus.com
2012-02-25  8:06 ` pinskia at gcc dot gnu.org [this message]
2012-02-25  9:10 ` [Bug target/52378] Can't build most recent svn version, i.e., trunk 4.7.0 list at qtrac dot plus.com
2012-02-25  9:41 ` pinskia at gcc dot gnu.org

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=bug-52378-4-0hm6dfgkNM@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).