On 28 October 2013 17:30, Jack Mitchell <[email protected]> wrote:
>> Not sure what's going on yet, but I found a configure failure, see the
>> attached log file.
>
> I have rebuilt this package multiple times now and have still not
> managed to break it. I believe it will just be a dirty build directory,
> but that shouldn't be an excuse for it not building.
>
> Does anyone have any suggestions on how to overcome this?

Just had a look at that configure log and that's normally the error
you get when moving from B==S to B!=S.  Unless Saul can replicate it
I'd say that warning was spurious/expected and can be ignored.

Not entirely sure why this happened as the patch also updates
separatebuilddir.inc, but without the actual tmp directory and all
logs that's not going to be easy to work out...

Ross
_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to