[Mesa-dev] Is there a mesa Docker image available like on travis-ci? (was Re: [PATCH 1/2] gallium/targets/dri: Add libunwind to linker flags)
Emil Velikov
emil.l.velikov at gmail.com
Wed Sep 13 21:04:45 UTC 2017
On 13 September 2017 at 11:07, Gert Wollny <gw.fossdev at gmail.com> wrote:
> Am Dienstag, den 12.09.2017, 17:15 +0100 schrieb Eric Engestrom:
>> On Tuesday, 2017-09-12 17:26:43 +0200, Gert Wollny wrote:
>> > Am Dienstag, den 12.09.2017, 12:26 +0100 schrieb Emil Velikov:
>> > > On 12 September 2017 at 11:17, Gert Wollny <gw.fossdev at gmail.com>
>> > > wrote:
>> > > >
>> > > >
>> > > > Is there a docker image available that resembles the travis-ci
>> > > > build environment as it is set up in mesa/.travis.yml (i.e.
>> > > > Ubuntu/Trusty with all the manually compiled packages)?
>> > > >
>> > >
>> > > There isn't one that I know of. They are using stock Ubuntu
>> > > (afaict)
>> > > so one should be able to reproduce/create one.
>> >
>> > I tried to avoid that ;)
>> >
>> > >
>> > > That aside, something like the following should help - do tweak
>> > > as
>> > > applicable. Don't forget to trim down the targets - no need to
>> > > build
>> > > unrelated stuff ;-)
>> >
>> > Thanks to your suggestion I was able to get some output [1], but
>> > the link command actually contains -lunwind and it is listed after
>> > libgallium.a, so I have no idea what's going wrong.
>> >
>> > Maybe it's a bug in that libtool version ...
>>
>> I wouldn't be surprised; try slibtool? We've had to use it internally
>> instead of libtool to build mesa for a while now.
>
> Well it turned out to be a different problem: I got random results:
> sometimes it built, sometimes not, and it turned out that for some
> reason the build randomly picked up either llvm-3.5 or llvm-3.9 and the
> first one build and the other one not. Interestingly, forcing either
> version resulted in an error in configure, probably because the default
> version that is installed doesn't have a version number in the llvm-
> config script file name.
>
> If I add the llvm-toolchain-trusty-3.9 toolchain and force the
> versionbuild seems to pass consistently.
>
Hmm the LLVM packaging is broken in more ways than expected :-\
> Emil, is there a reason why in the "make Gallium ST Other" build no
> llvm is specified ? - It is definitely picked up and used.
>
"ST Other" should address the minimum required LLVM version - 3.3.
Such early versions had quite a lot of bugs (wrt packaging at least),
so I did not set it explicitly.
If you can find a way convince Travis to use 3.3, patches will be appreciated.
Thanks
Emil
More information about the mesa-dev
mailing list