Re: user LDFLAGS for shared libraries

2004-03-14 Thread Marc Aurele La France
On Fri, 27 Feb 2004, Paul Jarc wrote: [I'm not subscribed. Mail-Followup-To set.] In xc/config/cf/{host,site}.def, is there a way for the user to supply linker flags for building shared libraries? I couldn't find one, but I need to supply them (-L and -Wl,-R, to find certain other

user LDFLAGS for shared libraries

2004-02-27 Thread Paul Jarc
[I'm not subscribed. Mail-Followup-To set.] In xc/config/cf/{host,site}.def, is there a way for the user to supply linker flags for building shared libraries? I couldn't find one, but I need to supply them (-L and -Wl,-R, to find certain other libraries), so I had to use this patch when building

Shared libraries

2003-10-24 Thread Matthias Scheler
Hello, even after the recent changes to XFree86-current libGLw, libXau and libXdmcp are still not built shared. I've got a report that this causes problem with certain 3rd party applications which try to build shared objects using these libraries. So may I ask what is the reason that

Re: Shared libraries

2003-10-24 Thread David Dawes
On Fri, Oct 24, 2003 at 09:43:13AM +0200, Matthias Scheler wrote: Hello, even after the recent changes to XFree86-current libGLw, libXau and libXdmcp are still not built shared. I've got a report that this causes problem with certain 3rd party applications which try to build shared

Re: Shared libraries

2003-10-24 Thread Matthieu Herrb
Matthias Scheler wrote (in a message from Friday 24) Hello, even after the recent changes to XFree86-current libGLw, libXau and libXdmcp are still not built shared. I've got a report that this causes problem with certain 3rd party applications which try to build shared objects

Re: Shared libraries

2003-10-24 Thread Mike A. Harris
On Fri, 24 Oct 2003, David Dawes wrote: even after the recent changes to XFree86-current libGLw, libXau and libXdmcp are still not built shared. I've got a report that this causes problem with certain 3rd party applications which try to build shared objects using these libraries. So may I ask

Re: Export symbol lists on Linux (was Re: RFC Marking private symbols in XFree86 shared libraries as private)

2003-10-20 Thread Ian Romanick
Jakub Jelinek wrote: The first is a MUST list, symbols which are exported from XFree86 shared libraries now when there is no anonymous version script, are not exported when an anonymous versions script created from stock *-def.cpp file is applied and are used by some binary or shared library

Re: Export symbol lists on Linux (was Re: RFC Marking private symbols in XFree86 shared libraries as private)

2003-10-15 Thread David Dawes
On Tue, Oct 14, 2003 at 09:50:07PM +0200, Jakub Jelinek wrote: I'd say it would be better to reuse *-def.cpp files (didn't know something like that existed). I've preprocessed all *-def.cpp files included in XFree86/xc/lib, gathered all symbols currently exported from XFree86 shared libraries

Export symbol lists on Linux (was Re: RFC Marking private symbols in XFree86 shared libraries as private)

2003-10-14 Thread Jakub Jelinek
I'd say it would be better to reuse *-def.cpp files (didn't know something like that existed). I've preprocessed all *-def.cpp files included in XFree86/xc/lib, gathered all symbols currently exported from XFree86 shared libraries, all undefined symbols in 5800 shared libraries and binaries I

Re: RFC Marking private symbols in XFree86 shared libraries as private

2003-10-10 Thread Jakub Jelinek
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

Re: RFC Marking private symbols in XFree86 shared libraries as private

2003-10-10 Thread Harold L Hunt II
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

Re: RFC Marking private symbols in XFree86 shared libraries as private

2003-10-09 Thread Ian Romanick
Jakub Jelinek wrote: 1) could be done by some header which everything uses, doing #if defined HAVE_VISIBILITY_ATTRIBUTE defined __PIC__ #define hidden __attribute__((visibility (hidden))) #else #define hidden /**/ #endif and write prototypes like: void hidden

Re: RFC Marking private symbols in XFree86 shared libraries as private

2003-10-09 Thread David Dawes
On Thu, Oct 09, 2003 at 02:05:47PM +0200, Jakub Jelinek wrote: Looking at various /usr/X11R6/lib/lib*.so* shared libraries, I'm seeing lots of exported symbols which look like they are exported just because they cannot be static (as they are used by some other .o files in the same shared library

Re: RFC Marking private symbols in XFree86 shared libraries as private

2003-10-09 Thread Jakub Jelinek
On Thu, Oct 09, 2003 at 12:08:55PM -0400, David Dawes wrote: On Thu, Oct 09, 2003 at 02:05:47PM +0200, Jakub Jelinek wrote: Looking at various /usr/X11R6/lib/lib*.so* shared libraries, I'm seeing lots of exported symbols which look like they are exported just because they cannot be static

Re: RFC Marking private symbols in XFree86 shared libraries as private

2003-10-09 Thread David Dawes
On Thu, Oct 09, 2003 at 04:55:25PM +0200, Jakub Jelinek wrote: On Thu, Oct 09, 2003 at 12:08:55PM -0400, David Dawes wrote: On Thu, Oct 09, 2003 at 02:05:47PM +0200, Jakub Jelinek wrote: Looking at various /usr/X11R6/lib/lib*.so* shared libraries, I'm seeing lots of exported symbols which