public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bruce Hoglund <bhoglund@mac.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>, gcc-help@gcc.gnu.org
Subject: Re: long long size compute failure during make of gcc-4.6.1 on OS X 10.7 Lion
Date: Wed, 07 Sep 2011 13:49:00 -0000	[thread overview]
Message-ID: <9ED5FF3E-92FA-433A-8D09-CE81ABEC238D@mac.com> (raw)
In-Reply-To: <mcr39g9szzw.fsf@coign.corp.google.com>


On Sep 7, 2011, at 1:06 AM, Ian Lance Taylor wrote:

> Bruce Hoglund <bhoglund@mac.com> writes:
> 
>> However, looking at the top, I noticed autoconfig 2.64 being used, while my 'which autoconf' says I'm using version 2.68 in /opt/local/bin/autoconf, and there is a version 2.61 in /usr/bin/autoconf. So where is the autoconf 2.64 from the config.og coming from?
> 
> autoconf is run by a gcc developer.  It is not run when compiling gcc.
> This is not an issue.

Ok, it just seemed the mismatch between the autoconfi I have & it used was odd, but again, I claim no expertise here. Here is the topmost part, which includes my configure directive:

"
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by configure, which was
generated by GNU Autoconf 2.64.  Invocation command line was

  $ /Users/bhoglund/tmp/gcc-4.6.1/configure --enable-languages=c,fortran,java,objc --enable-threads --with-cpu-64=x86-64 --with-gmp-lib=/usr/local/lib/ --with-mpfr-lib=/usr/local/lib/ --with-mpc-lib=/usr/local/lib/
"


> 
>> I can send the whole config.log if that will help, but here's the bottom-most bits of it:
> 
> This is probably the wrong config.log file.  You need the one in the
> directory in which configure is being run.  In this case,
> gcc/config.log.

The config.log I am referencing is in the same directory (see above) that in invocked my configure directive.

> 
> In general, the bottommost parts of config.log are not helpful.  You
> need to look for the failing test.

Searching the config.log on the word "fail" I found this middle bit:


"
configure:5545: gcc -o conftest -g -O2    conftest.c  -L/usr/local/lib/ -L/usr/local/lib/ -L/usr/local/lib/ -lmpc -lmpfr -lgmp >&5
configure:5545: $? = 0
configure:5546: result: yes
configure:5730: checking for PWL_handle_timeout in -lpwl
configure:5755: gcc -o conftest -g -O2    conftest.c -lpwl   >&5
ld: library not found for -lpwl
collect2: ld returned 1 exit status
configure:5755: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define LT_OBJDIR ".libs/"
| /* end confdefs.h.  */
| 
| /* Override any GCC internal prototype to avoid an error.
|    Use char because int might match the return type of a GCC
|    builtin and then its argument prototype would still apply.  */
| #ifdef __cplusplus
| extern "C"
| #endif
| char PWL_handle_timeout ();
| int
| main ()
| {
| return PWL_handle_timeout ();
|   ;
|   return 0;
| }
configure:5764: result: no
configure:5778: checking for version 0.11 (revision 0 or later) of PPL
configure:5795: gcc -c -g -O2    conftest.c >&5
conftest.c:10:19: fatal error: ppl_c.h: No such file or directory
compilation terminated.
configure:5795: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL ""
| #define LT_OBJDIR ".libs/"
| /* end confdefs.h.  */
| #include "ppl_c.h"
| int
| main ()
| {
| 
|     #if PPL_VERSION_MAJOR != 0 || PPL_VERSION_MINOR < 11
|     choke me
|     #endif
| 
|   ;
|   return 0;
| }
configure:5799: result: no

"

I hope this helps, and thank you for your help.


Bruce



  parent reply	other threads:[~2011-09-07 13:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-06 21:22 Bruce Hoglund
2011-09-06 21:52 ` Jonathan Wakely
2011-09-07  1:48   ` Bruce Hoglund
2011-09-07  5:06     ` Ian Lance Taylor
2011-09-07  8:28       ` Jonathan Wakely
2011-09-07 13:53         ` Bruce Hoglund
2011-09-07 14:02           ` Jonathan Wakely
2011-09-07 15:26             ` Bruce Hoglund
2011-09-07 15:42               ` Jonathan Wakely
2011-09-07 15:50                 ` Jonathan Wakely
2011-09-07 13:49       ` Bruce Hoglund [this message]
2011-09-07 14:07         ` Jonathan Wakely
2011-09-07 15:35           ` Bruce Hoglund
2011-09-07 16:32             ` Ian Lance Taylor
2011-09-07 22:11               ` Bruce Hoglund
2011-09-09 16:18                 ` Jonathan Wakely
2011-09-09 20:40                   ` Bruce Hoglund
2011-09-07 15:48         ` Ian Lance Taylor
2011-09-07  8:30     ` Jonathan Wakely
     [not found]       ` <37D86901-9803-45C7-B143-CC9A7D3E8814@mac.com>
2011-09-07 15:45         ` Jonathan Wakely

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=9ED5FF3E-92FA-433A-8D09-CE81ABEC238D@mac.com \
    --to=bhoglund@mac.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=jwakely.gcc@gmail.com \
    /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).