Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Currently packaging Qt5
Date: Wed, 22 May 2013 14:16:01 +0200	[thread overview]
Message-ID: <20130522141601.1fa68730@skate> (raw)
In-Reply-To: <1369020695818-45544.post@n4.nabble.com>

Dear prabindh,

On Sun, 19 May 2013 20:31:35 -0700 (PDT), prabindh wrote:

> Using default cross-compiled toolchain for the Beaglebone, some of the Xorg
> libraries are failing to link, with below errors:
> 
> undefined reference to `pwrite64'
> undefined reference to `pread64'

Have you enable largefile support in your configuration?

> I need C++ toolchain as well, that does not seem to be built with buildroot
> by default. Are the below the right set of options to add to have this
> support ?
> 
> "BR2_GCC_CROSS_CXX=y BR2_INSTALL_LIBSTDCPP=y"

The first one is useless, because it enables C++ on the native compiler
on the target (which is a deprecated feature anyway). And also, this
BR2_GCC_CROSS_CXX option has been removed in december 2010. I would
_really_ recommend you to upgrade to a more recent Buildroot version.
We're clearly not going to support a Buildroot version that's 2 years
old, considering how many things have changed since then.

BR2_INSTALL_LIBSTDCPP (despite its bizarre name) is the right option to
have C++ support in the cross-compiler.

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  parent reply	other threads:[~2013-05-22 12:16 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-14  9:58 [Buildroot] Currently packaging Qt5 Thomas Petazzoni
2013-01-14 10:50 ` Daniel Nyström
2013-01-14 11:04   ` Thomas Petazzoni
2013-02-19  4:18     ` prabindh
2013-02-19 15:29       ` Thomas Petazzoni
2013-05-20  3:31         ` prabindh
2013-05-22 11:55           ` Sundareson, Prabindh
2013-05-22 12:17             ` Thomas Petazzoni
2013-05-22 12:23               ` prabindh
2013-05-22 12:31                 ` Thomas Petazzoni
2013-05-22 12:36                   ` prabindh
2013-05-22 13:06                     ` Thomas Petazzoni
2013-05-22 13:26                       ` Sundareson, Prabindh
2013-05-22 13:30                         ` Thomas Petazzoni
2013-05-22 13:35                           ` prabindh
2013-05-22 14:04                             ` Thomas Petazzoni
2013-05-22 14:18                               ` Spenser Gilliland
2013-05-22 14:39                                 ` Thomas Petazzoni
2013-05-22 15:57                                 ` prabindh
2013-05-22 17:33                                   ` Spenser Gilliland
2013-05-23 20:38                                     ` Wojciech Sleńska
2013-05-22 12:16           ` Thomas Petazzoni [this message]
2013-05-22 12:21             ` prabindh
2013-01-14 11:37 ` Luca Ceresoli
2013-01-14 11:45   ` Thomas Petazzoni
2013-01-14 12:48     ` Sagaert Johan
2013-01-14 13:10       ` Thomas Petazzoni
2013-01-17  9:03         ` Arnout Vandecappelle
2013-02-06  9:56 ` Daniel Nyström
2013-02-06 10:04   ` Thomas Petazzoni
2013-02-06 10:12     ` Frédéric COIFFIER
2013-02-06 10:43       ` Thomas Petazzoni

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=20130522141601.1fa68730@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox