Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] Why is libbsd limited to ARM, x86 and x86_64?
Date: Tue, 2 Feb 2016 13:30:09 -0200 (BRST)	[thread overview]
Message-ID: <1326783145.511396.1454427009117.JavaMail.zimbra@datacom.ind.br> (raw)

Hello,

I'm working on a project for PowerPC in which libbsd would be useful. However the package is restricted to ARM, x86 and x86_64 architectures, since Config.in contains this:

  # libbsd requires a.out.h, which is only available for those
  # architectures: arm, x86 (and alpha, currently not supported in Buildroot;
  # also m68k which is currently not enabled, so can't be tested.)
  default y if BR2_arm || BR2_i386 || BR2_x86_64

However, my PowerPC toolchain, generated by crosstool-NG, provides the required a.out.h file. It is based on GCC 4.8.2, GLIBC 2.19 and Kernel 3.10.47.

Where does the information about the missing a.out.h on PowerPC comes from?

Carlos Santos (Casantos) - DATACOM, P&D
Rua Am?rica, 1000 - Eldorado do Sul, RS, Brasil - 92990-000
casantos at datacom.ind.br          +55 51 3933.3000 ext. 3627
http://www.datacom.ind.br

             reply	other threads:[~2016-02-02 15:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-02 15:30 Carlos Santos [this message]
2016-02-02 21:09 ` [Buildroot] Why is libbsd limited to ARM, x86 and x86_64? Arnout Vandecappelle
2016-02-03 15:39   ` Carlos Santos
2016-02-03 18:50     ` Carlos Santos
2016-02-04  0:00       ` Arnout Vandecappelle
2016-02-04  5:21         ` Baruch Siach
2016-02-04 12:22           ` Carlos Santos

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=1326783145.511396.1454427009117.JavaMail.zimbra@datacom.ind.br \
    --to=casantos@datacom.ind.br \
    --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