public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Pavel Pavlov <pavel@summit-tech.ca>
Cc: "gcc-help\@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Problem building gcc
Date: Thu, 06 May 2010 06:16:00 -0000	[thread overview]
Message-ID: <mcr1vdpzhaq.fsf@dhcp-172-17-9-151.mtv.corp.google.com> (raw)
In-Reply-To: <FEC208E803C7894F9CAB7B7410AC26441F5A5F1F6F@EXCHANGE03.pacifica.ca> (Pavel Pavlov's message of "Thu\, 6 May 2010 01\:39\:54 -0400")

Pavel Pavlov <pavel@summit-tech.ca> writes:

> 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.  */

There is some contradiction there.  The config.status file says
HAVE_LIMITS_H should be defined.  The config.h file says that it is
not defined.

Precisely which config.status and config.h file did you paste?  There
are several different files with those names in the build tree.  In
particular, did you paste files from the same directory?

The most useful file to look at in these cases is the config.log file.
Look at the one in the directory whose config.h says that
HAVE_LIMITS_H is undefined.  Look for the test for whether limits.h is
present.  Look for compilation errors.

Ian

  parent reply	other threads:[~2010-05-06  6:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  5:40 Pavel Pavlov
2010-05-06  6:02 ` Pavel Pavlov
2010-05-06  6:16 ` Ian Lance Taylor [this message]
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=mcr1vdpzhaq.fsf@dhcp-172-17-9-151.mtv.corp.google.com \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=pavel@summit-tech.ca \
    /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).