All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Flax <flatmax@flatmax.org>
To: buildroot@busybox.net
Subject: [Buildroot] aarch64 : g++ is not working
Date: Wed, 12 Apr 2017 19:17:00 +1000	[thread overview]
Message-ID: <bbdce605-675e-d770-3981-cf37e658d8e6@flatmax.org> (raw)
In-Reply-To: <f53a3152-a0ad-d86d-a9d1-26da5dceb526@flatmax.org>

Turns out this bug is with ulibc.

ulibc and g++ don't play well together - by switching to glibc, the 
problem is resolved.


Matt


On 11/04/17 09:50, Matt Flax wrote:
> Hi there,
>
> I have found that g++ is not working with aarch64. Not sure why it 
> isn't working. If others can verify this problem, it is a pretty big 
> show stopper.
>
> I have checked the problem with rtorrent like so :
>
> BR2_aarch64=y
> BR2_TOOLCHAIN_BUILDROOT_CXX=y
> BR2_PACKAGE_RTORRENT=y
>
> When I execute rtorrent :
>
> # rtorrent
>
> /usr/bin/rtorrent: symbol '_ZSt15__once_callable': can't handle reloc 
> type 0x407
>
>
> Any one got any ideas on how to get g++ working with aarch64 and 
> buildroot ?
>
>
> I have tried to test on qemu like so :
>
> make qemu_aarch64_virt_defconfig
> make menuconfig # enable cxx and rtorrent
>
> However, when I try to run qemu (looking at the file 
> board/qemu/aarch64-virt/readme.txt) the kernel doesn't output during 
> boot  - any suggestions on how to make this work ? I use the following 
> command :
>
> qemu-system-aarch64 -M virt -cpu cortex-a57 -nographic -smp 1 -kernel 
> output/images/Image -append "console=ttyAMA0" -netdev user,id=eth0 
> -device virtio-net-device,netdev=eth0
>
>
> thanks
>
> Matt
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

      reply	other threads:[~2017-04-12  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 23:50 [Buildroot] aarch64 : g++ is not working Matt Flax
2017-04-12  9:17 ` Matt Flax [this message]

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=bbdce605-675e-d770-3981-cf37e658d8e6@flatmax.org \
    --to=flatmax@flatmax.org \
    --cc=buildroot@busybox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.