public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Pavel Pavlov <pavel@summit-tech.ca>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Problem building gcc
Date: Thu, 06 May 2010 05:40:00 -0000	[thread overview]
Message-ID: <FEC208E803C7894F9CAB7B7410AC26441F5A5F1F6F@EXCHANGE03.pacifica.ca> (raw)

I'm having troubles with gcc build (it's really irrelevant what version I'm building, version itself is ok)
I tried to google, and I see similar problem reported all over the web, but nobody ever finally got it resolved.

My problem is identical to this one: http://gcc.gnu.org/ml/gcc-help/2008-03/msg00044.html
It fails on configure step of binutils in libiberty. I have no idea what's the problem: everything is good, I have all the headers installed and I use gcc-4.4.0 as toolset to build crosscompiler.

In that particular case I have this config.status : http://pastebin.com/PSsaya6F
Yet, the final config.h is absolutely identical to config.in: http://pastebin.com/ecL4qkqT with the only change added is the single line at the top: 
/* config.h.  Generated from config.in by configure.  */

Details of my environment: win7+msys and I'm trying to build cegcc crosscompiler. The src that I'm using is ok, I built it on Cygwin without that error, yet on msys/mingw it fails at the beginning.


I'm absolute ZERO or NULL in that black magic gibberish autoxxx scripts, so I'm asking for your help to resolve that issue. It seems that some of that atotools fail somehow to properly modify/parse some of the input files (CRLF issue maybe?). If It was a compilation issue I'd resolve it in no time, but since it's a configure failure I even have no idea what's called in what order so that I could see what script/program fails.

Than you

PS: That same problem was once raised on cegcc list but with the same outcome (unresolved): http://www.mail-archive.com/cegcc-devel@lists.sourceforge.net/msg02642.html

             reply	other threads:[~2010-05-06  5:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  5:40 Pavel Pavlov [this message]
2010-05-06  6:02 ` Pavel Pavlov
2010-05-06  6:16 ` Ian Lance Taylor
2010-05-06  6:40   ` Pavel Pavlov
2010-05-07 19:03 ` Ralf Wildenhues
2010-05-07 23:04   ` Pavel Pavlov
  -- strict thread matches above, loose matches on Subject: below --
2011-11-30  8:35 gideon425.gb5
2011-11-30  8:58 ` Marc Glisse
2011-12-19 18:45   ` Abdul Wahid Memon
2011-12-19 21:21     ` Ian Lance Taylor
2011-12-20  2:25       ` Abdul Wahid Memon
2011-12-20  5:07         ` Ian Lance Taylor
2008-08-28 13:28 problem " collinr
2008-08-28 13:42 ` Brian Dessent
2000-11-02 10:59 Problem building GCC Andrew Dumaresq
2000-11-03 18:51 ` Alexandre Oliva

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=FEC208E803C7894F9CAB7B7410AC26441F5A5F1F6F@EXCHANGE03.pacifica.ca \
    --to=pavel@summit-tech.ca \
    --cc=gcc-help@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).