From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/binutils: fix comment dependencies
Date: Sun, 7 Dec 2014 21:36:52 +0100 [thread overview]
Message-ID: <20141207203652.GD3902@free.fr> (raw)
In-Reply-To: <1417727462-10875-1-git-send-email-romain.naour@openwide.fr>
Romain, All,
On 2014-12-04 22:11 +0100, Romain Naour spake thusly:
> Signed-off-by: Romain Naour <romain.naour@openwide.fr>
> ---
> package/binutils/Config.in | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/package/binutils/Config.in b/package/binutils/Config.in
> index 50c38b6..fb037ef 100644
> --- a/package/binutils/Config.in
> +++ b/package/binutils/Config.in
> @@ -22,5 +22,5 @@ config BR2_PACKAGE_BINUTILS_TARGET
> endif
>
> comment "binutils needs a toolchain w/ wchar"
> - depends on !BR2_aarch64 && !BR2_nios2
> - depends on BR2_USE_WCHAR
> + depends on !BR2_aarch64 || !BR2_nios2
Nope. Architecture dependency must be the same as for the package
symbol, so we must keep the '&&' here, like there is for
BR2_PACKAGE_BINUTILS.
> + depends on !BR2_USE_WCHAR
Yes.
Regards,
Yann E. MORIN.
> --
> 1.9.3
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2014-12-07 20:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 21:11 [Buildroot] [PATCH 1/1] package/binutils: fix comment dependencies Romain Naour
2014-12-07 20:36 ` Yann E. MORIN [this message]
2014-12-07 21:06 ` 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=20141207203652.GD3902@free.fr \
--to=yann.morin.1998@free.fr \
--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