Can't build after refactor

[emveeppe]

Is something new required to force a build of geexbox for the cubox-i?  loadcfg and other scripts are now failing.

Martin

[Thomas Genty]

Le 31/07/2014 04:48, emveeppe a écrit :
> Is something new required to force a build of geexbox for the cubox-i?

No , nothing new.

> loadcfg and other scripts are now failing.

Can you post the last logs ?
>
> Martin

Tom
>
> --
> You received this message because you are subscribed to the Google
> Groups "OpenBricks Development List" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to openbricks-dev...@googlegroups.com
> <mailto:openbricks-dev...@googlegroups.com>.
> For more options, visit https://groups.google.com/d/optout.

[Rudi]

Hi Martin,

> Is something new required to force a build of geexbox for the cubox-i? loadcfg and other scripts are now failing.

I had teh same problems after this update. What I did was to delete build/build.cuboxi.eglibc and build/config.
Of course then a full rebuild is necessary. Also don't be surprised about a lot of messages like:

ls: cannot access packages/*/xbmc-addon-geexbox-network-dbg: No such file or directory

They are annoying, but do not hurt. I already talked about this with Tom...




--

Ruediger "Rudi" Ihle

[Thomas Genty]

Should be solved now with 318b26660

Tom
>
>
>
>

[emveeppe]

On Thursday, July 31, 2014 12:53:12 AM UTC-4, Rudi wrote:

I had teh same problems after this update. What I did was to delete build/build.cuboxi.eglibc and build/config.
Of course then a full rebuild is necessary. Also don't be surprised about a lot of messages like:

ls: cannot access packages/*/xbmc-addon-geexbox-network-dbg: No such file or directory

They are annoying, but do not hurt. I already talked about this with Tom...

Thanks Rudi and Tom, It built successfully after that change an no suprise message after the recent commit.  I forgot how long a clean build takes.

Martin

[Rudi]

Hi Martin,

> I forgot how long a clean build takes.

Now multiply this with 8 and you get an idea about the buildbot's workload...



--

Ruediger "Rudi" Ihle