From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Disable o32 ABI for MIPS64 architectures
Date: Fri, 28 Mar 2014 12:07:07 +0100 [thread overview]
Message-ID: <20140328120707.73840d9e@skate> (raw)
In-Reply-To: <5335510C.3090006@imgtec.com>
Dear Vicente Olivert Riera,
On Fri, 28 Mar 2014 10:38:04 +0000, Vicente Olivert Riera wrote:
> > That's not a problem is it? It's ok if the line is missing. A
> > missing line means "this option is not available". A line starting
> > with "#" means "the option is available but currently disabled"
>
> I want to be sure about that, because there are packages which use
> the BR2_MIPS_OABI32 symbol. So, maybe having that line starting with
> "#" means BR2_MIPS_OABI32=n, and everything works fine, and don't
> having that line at all means that symbol is not defined and the
> packages which use that symbol fail because of that. That's what I
> want to know.
BR2_FOO=n never exists. An option is either BR2_FOO=y, or undefined.
And since # indicates comments in .config files, a # BR2_FOO is not set
line is the same as not having BR2_FOO mentioned at all in the .config.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-03-28 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 14:15 [Buildroot] [PATCH v3] Disable o32 ABI for MIPS64 architectures Vicente Olivert Riera
2014-03-26 17:18 ` Arnout Vandecappelle
2014-03-26 18:03 ` Vicente Olivert Riera
2014-03-26 21:28 ` Peter Korsgaard
2014-03-27 9:56 ` Vicente Olivert Riera
2014-03-28 0:02 ` Joshua Kinard
2014-03-28 9:51 ` Vicente Olivert Riera
2014-03-28 10:27 ` Markos Chandras
2014-03-28 10:38 ` Vicente Olivert Riera
2014-03-28 10:41 ` Markos Chandras
2014-03-28 10:52 ` Joshua Kinard
2014-03-28 11:01 ` Vicente Olivert Riera
2014-03-28 11:07 ` Thomas Petazzoni [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=20140328120707.73840d9e@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 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.