public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: Nathan Plesnicher <nplez1@gmail.com>
To: crossgcc@sourceware.org
Subject: RPi build issue on OSX
Date: Thu, 16 May 2013 20:55:00 -0000	[thread overview]
Message-ID: <CAC-CMH16na8pjALdyxFway-raoufChdMGo4X-M53OLPVVoTF1g@mail.gmail.com> (raw)

I am having some trouble getting the RPi sample to build using
homebrew on Mountain Lion. I am getting the following error in the
'Installing C library headers & start files' step:

[CFG  ]    checking for __thread... yes
[CFG  ]    checking for tls_model attribute... yes
[CFG  ]    checking for compiler option to disable generation of FMA
instructions... -ffp-contract=off
[CFG  ]    checking for libgd... no
[CFG  ]    checking for is_selinux_enabled in -lselinux... no
[CFG  ]    checking size of long double... 8
[CFG  ]    checking for _FORTIFY_SOURCE predefine... no
[ERROR]    checking whether armv6-rpi-linux-gnueabi-gcc     implicitly
enables -fstack-protector... configure: error: unexpected symbols in
test:
[ERROR]
[ERROR]  >>
[ERROR]  >>  Build failed in step 'Installing C library headers & start files'
[ERROR]  >>        called in step '(top-level)'
[ERROR]  >>
[ERROR]  >>  Error happened in: CT_DoExecLog[scripts/functions@257]
[ERROR]  >>        called from:
do_libc_backend_once[scripts/build/libc/glibc-eglibc.sh-common@347]
[ERROR]  >>        called from:
do_libc_backend[scripts/build/libc/glibc-eglibc.sh-common@143]
[ERROR]  >>        called from:
do_libc_start_files[scripts/build/libc/glibc-eglibc.sh-common@60]
[ERROR]  >>        called from: main[scripts/crosstool-NG.sh@632]
[ERROR]  >>
[ERROR]  >>  For more info on this error, look at the file: 'build.log'
[ERROR]  >>  There is a list of known issues, some with workarounds, in:
[ERROR]  >>      '/Volumes/CrossTool2NG/crosstool-ng-1.18.0/docs/B -
Known issues.txt'
[ERROR]
[ERROR]  (elapsed: 6:48.00)

Looks like some sort of script problem but I am having trouble
locating the specific problem. Any ideas?

Not sure it matters, but I have been able to successfully build a
toolchain using the non-Linaro gcc w/ the standard glibc (instead of
eglibc) after applying a few manual patches, but I was hoping I could
get the RPi sample to work since I am building the toolchain for RPi
development.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

             reply	other threads:[~2013-05-16 20:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-16 20:55 Nathan Plesnicher [this message]
2013-05-16 21:46 ` Bryan Hundven
2013-05-17 17:06   ` Nathan Plesnicher
2013-05-17 17:23     ` Bryan Hundven

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=CAC-CMH16na8pjALdyxFway-raoufChdMGo4X-M53OLPVVoTF1g@mail.gmail.com \
    --to=nplez1@gmail.com \
    --cc=crossgcc@sourceware.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).