[Buildroot] [PATCH] bullet: disable on microblaze

[Buildroot] [PATCH] bullet: disable on microblaze

[Arnout Vandecappelle]

gcc doesn't finish compiling btSoftBody.cpp when optimization is
enabled.

Fixes:
http://autobuild.buildroot.net/results/6e4/6e4a9ede477b031f47f7e271c38f67f432a3573c
http://autobuild.buildroot.net/results/7dc/7dc4ab759dd3b1e3e03fe52c78e31327340bf8c9
http://autobuild.buildroot.net/results/637/637bae8b2be6c4c64f4f7c661cc8d4606b553538

Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
An option would have been to disable optimisation, but I couldn't be
bothered...
---
 package/bullet/Config.in | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/package/bullet/Config.in b/package/bullet/Config.in
index fc285ab..56b3d62 100644
--- a/package/bullet/Config.in
+++ b/package/bullet/Config.in
@@ -1,6 +1,7 @@
 config BR2_PACKAGE_BULLET
 	bool "bullet"
 	depends on BR2_INSTALL_LIBSTDCPP
+	depends on !BR2_microblaze
 	help
 	  Bullet is a Collision Detection and Rigid Body Dynamics
 	  Library.
@@ -9,3 +10,4 @@ config BR2_PACKAGE_BULLET
 
 comment "bullet needs a toolchain w/ C++"
 	depends on !BR2_INSTALL_LIBSTDCPP
+	depends on !BR2_microblaze
-- 
2.6.2

[Buildroot] [PATCH] bullet: disable on microblaze

[Sergio Prado]

Dear Arnout,

I'm looking at a related bug in the gpsd package (
https://bugs.busybox.net/show_bug.cgi?id=6872) and preparing a patch for
it. in my case, looks like it is just a matter of
disabling -fexpensive-optimizations. That way we can keep compiling the
package for the microblaze architecture.

I can make some tests in the bullet package if you want.

Regards,

Sergio Prado
Embedded Labworks
Office: +55 11 2628-3461
Mobile: +55 11 97123-3420

2015-11-21 19:10 GMT-02:00 Arnout Vandecappelle (Essensium/Mind) <
arnout@mind.be>:

> gcc doesn't finish compiling btSoftBody.cpp when optimization is
> enabled.
>
> Fixes:
>
> http://autobuild.buildroot.net/results/6e4/6e4a9ede477b031f47f7e271c38f67f432a3573c
>
> http://autobuild.buildroot.net/results/7dc/7dc4ab759dd3b1e3e03fe52c78e31327340bf8c9
>
> http://autobuild.buildroot.net/results/637/637bae8b2be6c4c64f4f7c661cc8d4606b553538
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> An option would have been to disable optimisation, but I couldn't be
> bothered...
> ---
>  package/bullet/Config.in | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/package/bullet/Config.in b/package/bullet/Config.in
> index fc285ab..56b3d62 100644
> --- a/package/bullet/Config.in
> +++ b/package/bullet/Config.in
> @@ -1,6 +1,7 @@
>  config BR2_PACKAGE_BULLET
>         bool "bullet"
>         depends on BR2_INSTALL_LIBSTDCPP
> +       depends on !BR2_microblaze
>         help
>           Bullet is a Collision Detection and Rigid Body Dynamics
>           Library.
> @@ -9,3 +10,4 @@ config BR2_PACKAGE_BULLET
>
>  comment "bullet needs a toolchain w/ C++"
>         depends on !BR2_INSTALL_LIBSTDCPP
> +       depends on !BR2_microblaze
> --
> 2.6.2
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20151121/a2f08aec/attachment.html>

[Buildroot] [PATCH] bullet: disable on microblaze

[Arnout Vandecappelle]

On 21-11-15 22:31, Sergio Prado wrote:
> Dear Arnout,
> 
> I'm looking at a related bug in the gpsd package
> (https://bugs.busybox.net/show_bug.cgi?id=6872) and preparing a patch for it. in
> my case, looks like it is just a matter of disabling -fexpensive-optimizations.
> That way we can keep compiling the package for the microblaze architecture.
> 
> I can make some tests in the bullet package if you want.


 Yeah, good plan.


 Regards,
 Arnout



-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] [PATCH] bullet: disable on microblaze

[Arnout Vandecappelle]

On 22-11-15 01:17, Arnout Vandecappelle wrote:
> On 21-11-15 22:31, Sergio Prado wrote:
>> Dear Arnout,
>>
>> I'm looking at a related bug in the gpsd package
>> (https://bugs.busybox.net/show_bug.cgi?id=6872) and preparing a patch for it. in
>> my case, looks like it is just a matter of disabling -fexpensive-optimizations.
>> That way we can keep compiling the package for the microblaze architecture.
>>
>> I can make some tests in the bullet package if you want.
> 
> 
>  Yeah, good plan.

 On second thought, don't bother. I tried it and it doesn't make a difference.

 Regards,
 Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

[Buildroot] [PATCH] bullet: disable on microblaze

[Thomas Petazzoni]

Dear Arnout Vandecappelle (Essensium/Mind),

On Sat, 21 Nov 2015 22:10:07 +0100, Arnout Vandecappelle
(Essensium/Mind) wrote:
> gcc doesn't finish compiling btSoftBody.cpp when optimization is
> enabled.
> 
> Fixes:
> http://autobuild.buildroot.net/results/6e4/6e4a9ede477b031f47f7e271c38f67f432a3573c
> http://autobuild.buildroot.net/results/7dc/7dc4ab759dd3b1e3e03fe52c78e31327340bf8c9
> http://autobuild.buildroot.net/results/637/637bae8b2be6c4c64f4f7c661cc8d4606b553538
> 
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
> ---
> An option would have been to disable optimisation, but I couldn't be
> bothered...
> ---
>  package/bullet/Config.in | 2 ++
>  1 file changed, 2 insertions(+)

I've added a comment in the Config.in with a reference to the gcc bug
you have reported. Then, applied to master. Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com