From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Danilo Bargen <mail@dbrgn.ch>
Cc: Buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] Excluding certain architectures for a package
Date: Mon, 5 Dec 2022 21:12:24 +0100 [thread overview]
Message-ID: <20221205201224.GG2855@scaer> (raw)
In-Reply-To: <b0cf6b84-b0ce-4c51-8ed3-54bcfd1c8ef6@app.fastmail.com>
Danillo, All,
On 2022-12-05 07:52 +0100, Danilo Bargen spake thusly:
> Hi all
>
> The package below does not currently build on MIPS because one of
> crypto libraries it depends on doesn't yet fully support that
> architecture: https://github.com/briansmith/ring/issues/562
>
> Is there a way to exclude certain architectures for a package? What
> is the process for this?
You can add a dependency on architectures like any other dependency; see
the manual:
https://buildroot.org/downloads/manual/manual.html#dependencies-target-toolchain-options
Quoting:
* Target architecture
- Dependency symbol: BR2_powerpc, BR2_mips, … (see arch/Config.in)
- Comment string: no comment to be added
For example, to exclude all of mips and mips64:
# Crypto opt not available for mips:
depends on !(BR2_mips || BR2_mipsel || BR2_mips64 || BR2_mips64el)
Adapt appropriately, of course.
Regards,
Yann E. MORIN.
> Cheers,
> Danilo
>
> ----- Original message -----
> Betreff: [autobuild.buildroot.net] Your daily results for 2022-11-03
> Datum: Freitag, 04. November 2022 08:39
>
> Hello,
>
> Autobuilder failures
> ====================
>
> Below is a list of build failures reported by the Buildroot autobuilders
> in relation to packages or CPU architectures you are in charge of.
> Please help us improving the quality of Buildroot by investigating those
> build failures and sending patches to fix them.
>
> Results for the 'master' branch
> -------------------------------
>
> Build failures related to your packages:
>
> arch | reason | url
> -------------+--------------------------------+---------------------------------------------------------------------------------
> mips | tealdeer-1.6.1 | http://autobuild.buildroot.net/results/d4863f476de2a8b4c9d28ee52b1a48f5b0947c4b
>
>
> Thanks for your contribution to Buildroot!
>
> --
> http://autobuild.buildroot.net
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-12-05 20:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 6:52 [Buildroot] Excluding certain architectures for a package Danilo Bargen
2022-12-05 20:12 ` Yann E. MORIN [this message]
2022-12-08 10:05 ` Danilo Bargen
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=20221205201224.GG2855@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=mail@dbrgn.ch \
/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.