All of lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
       [not found] <20170430062822.F06D82097E@mail.free-electrons.com>
@ 2017-05-03 10:29 ` Thomas De Schampheleire
  2017-05-03 12:29   ` Thomas Petazzoni
  0 siblings, 1 reply; 5+ messages in thread
From: Thomas De Schampheleire @ 2017-05-03 10:29 UTC (permalink / raw)
  To: buildroot

Hi Thomas,

On Sun, Apr 30, 2017 at 08:28:22AM +0200, Thomas Petazzoni wrote:
> Hello,
> 
> This is the list of Buildroot build failures that occured on
> 2017-04-29, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
> 
> Build failures related to your packages:
> 
>          arm |      toolchain-external-custom | http://autobuild.buildroot.net/results/39888c188c0d13219a8419897a833275fcc81597
> 

It seems that this is an invalid configuration:

BR2_arm=y
BR2_cortex_a8=y
BR2_ARM_EABI=y
BR2_ARM_INSTRUCTIONS_THUMB2=y
BR2_STATIC_LIBS=y
BR2_TOOLCHAIN_EXTERNAL=y


With STATIC_LIBS set, there is no downloadable external toolchain.
As such, Buildroot falls back to a preinstalled one and sets the toolchain
location to /path/to/toolchain, which does not exist.

However, I don't find this toolchain config in the list at:
http://autobuild.buildroot.net/toolchains/configs/

The build was submitted by Richard Braun, could it be that he is using toolchain
configs that are not in this list?

Thanks,
Thomas

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
  2017-05-03 10:29 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29 Thomas De Schampheleire
@ 2017-05-03 12:29   ` Thomas Petazzoni
       [not found]     ` <20170503124713.GA17301@shattrath>
  0 siblings, 1 reply; 5+ messages in thread
From: Thomas Petazzoni @ 2017-05-03 12:29 UTC (permalink / raw)
  To: buildroot

Hello,

Adding Arnout in Cc here because I believe it is a bug he introduced :-)

On Wed, 3 May 2017 12:29:22 +0200, Thomas De Schampheleire wrote:

> It seems that this is an invalid configuration:
> 
> BR2_arm=y
> BR2_cortex_a8=y
> BR2_ARM_EABI=y
> BR2_ARM_INSTRUCTIONS_THUMB2=y
> BR2_STATIC_LIBS=y
> BR2_TOOLCHAIN_EXTERNAL=y
> 
> With STATIC_LIBS set, there is no downloadable external toolchain.
> As such, Buildroot falls back to a preinstalled one and sets the toolchain
> location to /path/to/toolchain, which does not exist.
> 
> However, I don't find this toolchain config in the list at:
> http://autobuild.buildroot.net/toolchains/configs/

BR2_STATIC_LIBS is randomly added, to all possible configurations:

  https://git.buildroot.org/buildroot-test/tree/scripts/autobuild-run#n553

So even if you don't see this configuration in the list of toolchains,
it is normal to see BR2_STATIC_LIBS=y.

However, BR2_STATIC_LIBS should not be added for glibc toolchains.
Arnout recently reworked the way we detect if it's a glibc toolchain or
not... and it seems like it doesn't work as expected. Or perhaps
Richard hasn't updated his autobuild-run script and we have another
issue ?

Richard have you updated your autobuild-run script recently?

Thomas DS, see:

  https://git.buildroot.org/buildroot-test/commit/scripts/autobuild-run?id=7c49373a4f494fea64e98c44ca504680e89a0e86
  https://git.buildroot.org/buildroot-test/commit/scripts/autobuild-run?id=3972df164e23828a0e9eb8aa85f4e82b760a859e

Best regards,

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
       [not found]     ` <20170503124713.GA17301@shattrath>
@ 2017-05-03 13:02       ` Thomas Petazzoni
  2017-05-04  6:55         ` Arnout Vandecappelle
  0 siblings, 1 reply; 5+ messages in thread
From: Thomas Petazzoni @ 2017-05-03 13:02 UTC (permalink / raw)
  To: buildroot

Hello,

On Wed, 3 May 2017 14:47:13 +0200, Richard Braun wrote:

> > Richard have you updated your autobuild-run script recently?  
> 
> My builder should be running with version 6986aa15ed966e16312ebaef1a47f498ca76a197.
> 
> It is automatically updated and restarted once a week.

Then you are running with the latest changes from Arnout, and most of
the other autobuilder slaves are not, which is why we only see this
issue coming from your autobuilder.

So, this confirms my hypothesis that the bug is in the changes from
Arnout :-)

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
  2017-05-03 13:02       ` Thomas Petazzoni
@ 2017-05-04  6:55         ` Arnout Vandecappelle
  2017-05-04  7:37           ` Thomas Petazzoni
  0 siblings, 1 reply; 5+ messages in thread
From: Arnout Vandecappelle @ 2017-05-04  6:55 UTC (permalink / raw)
  To: buildroot



On 03-05-17 15:02, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 3 May 2017 14:47:13 +0200, Richard Braun wrote:
> 
>>> Richard have you updated your autobuild-run script recently?  
>>
>> My builder should be running with version 6986aa15ed966e16312ebaef1a47f498ca76a197.
>>
>> It is automatically updated and restarted once a week.
> 
> Then you are running with the latest changes from Arnout, and most of
> the other autobuilder slaves are not, which is why we only see this
> issue coming from your autobuilder.
> 
> So, this confirms my hypothesis that the bug is in the changes from
> Arnout :-)

 The problem is that that defconfig file (sourcery-arm-thumb2.config) doesn't
specify which toolchain to use:

BR2_arm=y
BR2_cortex_a8=y
BR2_ARM_EABI=y
BR2_ARM_INSTRUCTIONS_THUMB2=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TARGET_OPTIMIZATION=""

It just relies on the default external toolchain.

 Obviously this isn't very robust to begin with: when the external toolchains
change, this could implicitly change this toolchain defconfig. E.g. imagine that
Linaro would grow a Thumb2 option, then suddenly this sourcery-arm-thumb2.config
would build using a Linaro toolchain...

 So I think the solution is to explicitly add the predefined external toolchain
to use to all the toolchain configs. I'll try to send a patch for that.

 BTW, I notice now that we don't have configs for the Codescape toolchains. Any
reason for that?

 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

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29
  2017-05-04  6:55         ` Arnout Vandecappelle
@ 2017-05-04  7:37           ` Thomas Petazzoni
  0 siblings, 0 replies; 5+ messages in thread
From: Thomas Petazzoni @ 2017-05-04  7:37 UTC (permalink / raw)
  To: buildroot

Hello,

On Thu, 4 May 2017 08:55:47 +0200, Arnout Vandecappelle wrote:

>  The problem is that that defconfig file (sourcery-arm-thumb2.config) doesn't
> specify which toolchain to use:
> 
> BR2_arm=y
> BR2_cortex_a8=y
> BR2_ARM_EABI=y
> BR2_ARM_INSTRUCTIONS_THUMB2=y
> BR2_TOOLCHAIN_EXTERNAL=y
> BR2_TARGET_OPTIMIZATION=""
> 
> It just relies on the default external toolchain.
> 
>  Obviously this isn't very robust to begin with: when the external toolchains
> change, this could implicitly change this toolchain defconfig. E.g. imagine that
> Linaro would grow a Thumb2 option, then suddenly this sourcery-arm-thumb2.config
> would build using a Linaro toolchain...

Aaah, yes.

>  So I think the solution is to explicitly add the predefined external toolchain
> to use to all the toolchain configs. I'll try to send a patch for that.

OK. Thanks.

>  BTW, I notice now that we don't have configs for the Codescape toolchains. Any
> reason for that?

Nope, just nobody has suggested one. Or maybe at the time I was a bit
annoyed by having too many MIPS related configurations.

Best regards,

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

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2017-05-04  7:37 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
     [not found] <20170430062822.F06D82097E@mail.free-electrons.com>
2017-05-03 10:29 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2017-04-29 Thomas De Schampheleire
2017-05-03 12:29   ` Thomas Petazzoni
     [not found]     ` <20170503124713.GA17301@shattrath>
2017-05-03 13:02       ` Thomas Petazzoni
2017-05-04  6:55         ` Arnout Vandecappelle
2017-05-04  7:37           ` Thomas Petazzoni

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.