Using -export-symbols-regex all private symbols are hidden, resulting in the
following changes:
libkms: removes all driver specific exports
radeon: removes the bof_* exports
nouveau: removes the abi16_* exports
freedreno: remove the *kgsl_* and msm_* exports
intel: removes the drm_mm* exports
[CCing Emil as well]
Am 30.07.2014 um 11:38 schrieb Maarten Lankhorst:
Using -export-symbols-regex all private symbols are hidden, resulting in the
following changes:
Wasn't -export-symbols-regex exactly that stuff we are trying to avoid
in mesa?
Christian.
libkms: removes all driver
On 30/07/14 11:16, Christian König wrote:
[CCing Emil as well]
Am 30.07.2014 um 11:38 schrieb Maarten Lankhorst:
Using -export-symbols-regex all private symbols are hidden, resulting in the
following changes:
Wasn't -export-symbols-regex exactly that stuff we are trying to avoid in
From: Thierry Reding tred...@nvidia.com
Checks whether or not the compiler supports the -fvisibility option. If
so it sets the VISIBILITY_CFLAGS variable which can be added to the per
directory AM_CFLAGS where appropriate.
By default all symbols will be hidden via the VISIBILITY_CFLAGS. The
On Wed, Jul 30, 2014 at 9:48 AM, Thierry Reding
thierry.red...@gmail.com wrote:
From: Thierry Reding tred...@nvidia.com
Checks whether or not the compiler supports the -fvisibility option. If
so it sets the VISIBILITY_CFLAGS variable which can be added to the per
directory AM_CFLAGS where
On 30/07/14 14:48, Thierry Reding wrote:
From: Thierry Reding tred...@nvidia.com
Checks whether or not the compiler supports the -fvisibility option. If
so it sets the VISIBILITY_CFLAGS variable which can be added to the per
directory AM_CFLAGS where appropriate.
By default all symbols
On 30/07/14 15:31, Rob Clark wrote:
On Wed, Jul 30, 2014 at 9:48 AM, Thierry Reding
thierry.red...@gmail.com wrote:
From: Thierry Reding tred...@nvidia.com
Checks whether or not the compiler supports the -fvisibility option. If
so it sets the VISIBILITY_CFLAGS variable which can be added to
On Wed, Jul 30, 2014 at 10:37 AM, Emil Velikov emil.l.veli...@gmail.com wrote:
On 30/07/14 15:31, Rob Clark wrote:
On Wed, Jul 30, 2014 at 9:48 AM, Thierry Reding
thierry.red...@gmail.com wrote:
From: Thierry Reding tred...@nvidia.com
Checks whether or not the compiler supports the
I've been following the nouveau git, but it seems now that when I follow
the instructions on it [1], I end up with a kernel v3.12 rather than
3.16rc7 (though that is a branch in my repo). I guess I don't yet grok how
git works with remote masters. I want to update to the latest Linus git
kernel +
You probably want the drm-nouveau-next branch. Unfortunately master
does not appear to get updated anymore.
You can also attempt to build the very latest and greatest, which is
at http://cgit.freedesktop.org/~darktama/nouveau, although it will
only build against the latest kernels (usually).
On
10 matches
Mail list logo