[Mesa-dev] [PATCH 1/2] mesa: bump required GCC version to 4.4.0

Jonathan Gray jsg at jsg.id.au
Tue Jan 26 16:35:22 PST 2016


On Tue, Jan 26, 2016 at 02:24:34PM -0800, Matt Turner wrote:
> On Tue, Jan 26, 2016 at 2:04 PM, Timothy Arceri
> <timothy.arceri at collabora.com> wrote:
> > The last time this was bumped we settled on 4.2.0 because OpenBSD
> > wasn't willing to ship anything greater than 4.2.1 (as that was the
> > last GPLv2 licensed version) however they now ship 4.9.3.
> 
> I suspect they ship 4.9.3 in ports but 4.2.1 in the base system, and
> they'll want to build Mesa with 4.2.1 because Mesa is part of the base
> system. (Excuse the potentially incorrect terminology. I've never used
> OpenBSD).
> 
> Cc'ing Jonathan Gray for clarification.

Correct.  There are three source trees in OpenBSD.

src/base, The kernel, libc, libssl, posix utilities etc.
xenocara, xserver, xterm, Mesa, associated libraries.
ports/packages,  Makefiles and patches to fetch third party source.

The src/xenocara trees contain full source ready to build.  Installation
media includes binaries from the src and xenocara trees.  Any dependencies
must be included.  This is why we had a different build system for Mesa
for some time, so as not to to require gnu make or python.

src/xenocara is built with gcc 4.2.1.  This has in the past been patched
for things like the gnu binary integer constants extension the i965
code started to require a couple of major Mesa releases ago.  FreeBSD
also patched their gcc for the same.

In the long term the base compiler will likely move to llvm for
architectures where that is possible.  llvm is not in either
src or xenocara trees currently, so Mesa is not built against llvm.
Which means no 2d/3d acceleration on radeonsi because of the llvm
requirement.

I would be interested to hear specifics as to what post gcc 4.2.1
extensions/changes people are interested in using.

Jonathan


More information about the mesa-dev mailing list