From: Carlos Santos <casantos@datacom.ind.br>
To: buildroot@busybox.net
Subject: [Buildroot] Why is libbsd limited to ARM, x86 and x86_64?
Date: Thu, 4 Feb 2016 10:22:02 -0200 (BRST) [thread overview]
Message-ID: <963387420.1109035.1454588522735.JavaMail.zimbra@datacom.ind.br> (raw)
In-Reply-To: <20160204052132.GK3529@sapphire.tkos.co.il>
> From: "Baruch Siach" <baruch@tkos.co.il>
> To: "Arnout Vandecappelle" <arnout@mind.be>
> Cc: "Carlos Santos" <casantos@datacom.ind.br>, "guilherme machado" <guilherme.machado@datacom.ind.br>, "buildroot"
> <buildroot@buildroot.org>
> Sent: Thursday, February 4, 2016 3:21:32 AM
> Subject: Re: [Buildroot] Why is libbsd limited to ARM, x86 and x86_64?
> Hi Carlos, Arnout,
>
> On Thu, Feb 04, 2016 at 01:00:14AM +0100, Arnout Vandecappelle wrote:
>> On 03-02-16 19:50, Carlos Santos wrote:
>> > 2. I'm absolutely ignorant about nios2. What defconfig should I use to
>> > build for it?
>>
>> Hm, looks like we don't have a nios2 defconfig... But you can do a very quick
>> build-test by setting arch to nios2 and selecting the Sourcery toolchain.
>
> You can also use the config at
> http://autobuild.buildroot.net/toolchains/configs/br-nios2-glibc.config.
OK, I was able to build libbsd and its dependent packages (libedit and netcat-openbsd) using br-nios2-glibc.config, as well as the following defconfigs: (some of them modified to use glibc instead of uClibc):
- qemu_aarch64_virt
- qemu_mips64_malta
- qemu_mips64el_malta
- qemu_mips_malta
- qemu_mipsel_malta
- qemu_sh4_r2d
- qemu_sparc64_sun4u
- qemu_sparc_ss10
The compilation for microblaze failed using br-microblazeel-full.config, taken from the autobuilder (build log saved at http://ur1.ca/ohak2). It also failed, for similar reasons using the existing defconfig's:
- qemu_microblazebe_mmu
- qemu_microblazeel_mmu
'
The compilation also failed using qemu_sh4eb_r2d_defconfig but I don't think it is a valid test, since I forced BR2_TOOLCHAIN_BUILDROOT_GLIBC to "y".
So I think I should disable libbsd for the microblaze architecture, at least for the moment.
Carlos Santos (Casantos)
DATACOM, P&D
prev parent reply other threads:[~2016-02-04 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 15:30 [Buildroot] Why is libbsd limited to ARM, x86 and x86_64? Carlos Santos
2016-02-02 21:09 ` 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 [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=963387420.1109035.1454588522735.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