On Thu, Oct 09, 2003 at 09:01:15PM -0400, David Dawes wrote:
Well, both version script and __attribute__((visibility (hidden)))
can be used at the same time.
Anonymous version script works in 2001-12-18 and later binutils
and AFAIK in Solaris linker. No idea about other arches.
If you think
Jakub,
I just noticed this thread today. If this will have problems, then they
will definitely be visible on Cygwin. So, I ask that I please be
included in the testing process before this is committed, if it ever is.
I would gladly do test builds under Cygwin to confirm that the new
scheme
Yth Bapak/Ibu/Sdr/i
Salam Sejahtera,
Perkenalkan nama saya Felix, ingin mengajak anda untuk bekerja sama
dalam bisnis yang sedang saya tekuni saat ini.
Saya mengetahui email address anda dari salah satu web di internet dan saya
berpikir bahwa anda menyenangi komunikasi lewat internet. Oleh
Mark Vojkovich wrote:
On Wed, 8 Oct 2003, Emmanuel ALLAUD wrote:
Juliusz Chroboczek wrote:
I'd like to suggest that you implement device-specific code as a kernel
module.
Well, that won't happen; we already have working portable driver code
in userspace, and there's no
Ave
I've got a error when I build CVS with
#define BuildXF86DRINO
#define BuildXF86DRMNO
Full host.def below the error message.
Distro : debian stable
Error:
make[6]: Entering directory
On Fre, 2003-10-10 at 20:56, Martijn Uffing wrote:
radeon_driver.c: In function `RADEONPreInitConfig':
radeon_driver.c:1972: warning: unused variable `s'
radeon_driver.c: In function `RADEONInitDispBandwidth':
radeon_driver.c:5727: structure has no member named
`directRenderingEnabled'
The locking problem is solved, my original analysis was incorrect. The
problem was that DRM_CAS was not correctly implemented on IA64. Thus
this was an IA64 issue only, this is consistent with others who showed
up in a google search describing the problem, all were on IA64.
I have filed an
John Dennis wrote:
The locking problem is solved, my original analysis was incorrect. The
problem was that DRM_CAS was not correctly implemented on IA64. Thus
this was an IA64 issue only, this is consistent with others who showed
up in a google search describing the problem, all were on IA64.
I