From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] protobuf: bump version to 2.6.1
Date: Tue, 30 Jun 2015 16:48:14 +0200 [thread overview]
Message-ID: <20150630164814.3d7c2bdc@free-electrons.com> (raw)
In-Reply-To: <1313674444.2327407.1435171914537.JavaMail.zimbra@datacom.ind.br>
Dear George Redivo,
On Wed, 24 Jun 2015 15:51:54 -0300 (BRT), George Redivo wrote:
> I looked to the ola's Config.in file and there is no powerpc dependency declared in there.
> So I'm not sure if it's valid to try to make a build to powerpc arch including this package. Is it?
I think Peter added || BR2_powerpc in ola/Config.in. The ola package
itself does not have any architecture dependency, it only has such
dependencies because it selects protobuf. So if protobuf now supports
PowerPC, then it should also be possible to build Ola.
And anyway, the error reported by Peter occurred during the build of
protobuf itself, so Ola is not relevant here.
> Anyway, I tried to reproduce the reported error by adding those flags in my .config file.
> In addition, I removed BR2_powerpc_8548=y, that was declared.
>
> I ran make olddefconfig and the .config changed.
> The BR2_PACKAGE_OLA flag simply dropped out from the .config file.
>
> May you send me your entire .config after running make olddefconfig please?
Just do:
$ cat > .config <<EOF
BR2_powerpc=y
BR2_powerpc_603e=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_PACKAGE_OLA=y
EOF
and then:
$ make olddefconfig
$ make
As explained by Peter.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-30 14:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 17:58 [Buildroot] [PATCH 1/1] protobuf: bump version to 2.6.1 George Redivo
2015-06-22 20:51 ` Peter Korsgaard
2015-06-22 21:21 ` Matthew Weber
2015-06-24 18:51 ` George Redivo
2015-06-30 14:48 ` Thomas Petazzoni [this message]
2015-07-07 15:06 ` George Redivo
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=20150630164814.3d7c2bdc@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox