[Buildroot] [PATCH RFC 1/1] package/libpthsem: cannot be sanely cross-compiled

Brendan Heading brendanheading at gmail.com
Sun Aug 2 22:39:02 UTC 2015


> I've tested the first reported build failure... And it builds fine for
> me... :-/
>
> Not to say that the result is correct, just that I can't reproduce the
> build failure.

Yann,

Thanks for reviewing my patch. I knew it would not fly, so I put it as
RFC to start a discussion on the best approach.

> All those tests that can not be determined at build time because they
> need to run programs should be forced-guessed,with the appropriate ac_cv
> variables.
>
> See for example the atk package, which has quite a bunch of those;
>     package/atk/atk.mk

Noted. I agree that this is a better approach.

> Now, if you look closely (not too closely, even!), you'll see that those
> errors are all occuring on a single autobuilder, the one from Nathaniel:
>
>     http://autobuild.buildroot.org/?reason=libpthsem-2.0.8
>
> So, I guess something from the environment causes the build failures.

Yes, I agree. I found the same problem that you did (issues with
reproducibility). Sometimes you get "Exec format error", others "file
not found" (which happens when there is a dynamic link problem).
Strangely, I could reproduce it on some architectures but not others.
But irrespective of this - the way that it is detecting features
cannot work in a cross-compiled environment. So I didn't waste a lot
of time characterising this in detail.

The big problem is the misdetection of the sjlj as you noted. To fix
this properly we're going to have to go through all the arches and
figure out what the correct value is ..

Brendan



More information about the buildroot mailing list