public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Bruce Hoglund <bhoglund@mac.com>
Cc: 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 15:50:00 -0000	[thread overview]
Message-ID: <CAH6eHdRAN4o+DRn4ugrfR+RiTjOcHJ25D-fW+VOp0KRrx26i-Q@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdQFDTT5YXJC-QW8JPyqAvtgjwbZwVDF7e7s3py_DY4U_Q@mail.gmail.com>

On 7 September 2011 16:42, Jonathan Wakely wrote:
> On 7 September 2011 16:25, Bruce Hoglund wrote:
>>
>> configure:5771: result: 0
>> configure:5785: checking size of int
>> configure:5790: gcc -o conftest -g -fkeep-inline-functions    conftest.c  >&5
>> Undefined symbols for architecture x86_64:
>>  "___builtin___stpncpy_chk", referenced from:
>>      ___inline_stpncpy_chk in ccL1VweA.o
>> ld: symbol(s) not found for architecture x86_64
>> collect2: ld returned 1 exit status
>> configure:5790: $? = 1
>> configure: program exited with status 1
>> configure: failed program was:
>> | /* confdefs.h */
>>
>> "
>>
>> Looks like the checker program ( "confdefs.h") did not have an uptodate idea of w the x86_64 architecture should have or not have, but I may be quite wrong.
>
> You are.  It's just telling you that the symbol it's trying to find is
> an x86_64 symbol.
>
> Again, ignore failures except the "cannot compute sizeof (long long)"
> one, they do not indicate a problem, that's what's supposed to happen.


Apologies, looking properly I see the same linker error in the
"checkin size of long long" test.

So now we're finally getting somewhere.

  reply	other threads:[~2011-09-07 15:50 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 [this message]
2011-09-07 13:49       ` Bruce Hoglund
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=CAH6eHdRAN4o+DRn4ugrfR+RiTjOcHJ25D-fW+VOp0KRrx26i-Q@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=bhoglund@mac.com \
    --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).