Bug#508406: Intend to create an -fPIC library package...

2009-07-22 Thread Peter Samuelson
> > 2) Runtime linking. This is overhead at application startup time. > >Something that embeds an SQL engine should not, I think, start up too > >frequently. Am I wrong? [Bernd Zeimetz] > We're talking about amarok here. As a medi aplayer I could imagine it > will be starte several time

Bug#508406: Intend to create an -fPIC library package...

2009-07-22 Thread Bernd Zeimetz
Peter Samuelson wrote: > 2) Runtime linking. This is overhead at application startup time. >Something that embeds an SQL engine should not, I think, start up too >frequently. Am I wrong? We're talking about amarok here. As a medi aplayer I could imagine it will be starte several times p

Bug#508406: Intend to create an -fPIC library package...

2009-07-21 Thread Steve Langasek
On Tue, Jul 21, 2009 at 04:52:52PM +0200, Wouter Verhelst wrote: > > As I understand it, the performance drawbacks of a shared library are: > > 1) The PIC code and its use of a GOT. Given that we're talking about a > >PIC static library, this is not relevant. > The argument was that a shared

Bug#508406: Intend to create an -fPIC library package...

2009-07-21 Thread Christian Hammers
Hello On 2009-07-21 Wouter Verhelst wrote: > On Tue, Jul 21, 2009 at 12:40:17AM +0200, Christian Hammers wrote: > > Am Mon, 20 Jul 2009 23:18:23 +0100 > > schrieb Roger Leigh : > > > If other libraries are including this library, then why is libmysqld > > > not being provided as a properly-version

Bug#508406: Intend to create an -fPIC library package...

2009-07-21 Thread Wouter Verhelst
On Tue, Jul 21, 2009 at 09:17:28AM -0500, Peter Samuelson wrote: > > [Wouter Verhelst] > > Whether we should recommend using static libraries is another matter > > entirely; indeed performance does go down a teeny weeny bit when using > > shared libraries, but the difference shouldn't be *that* la

Bug#508406: Intend to create an -fPIC library package...

2009-07-21 Thread Peter Samuelson
[Wouter Verhelst] > Whether we should recommend using static libraries is another matter > entirely; indeed performance does go down a teeny weeny bit when using > shared libraries, but the difference shouldn't be *that* large; if it > is, that probably means they're using a twisty maze of functio

Bug#508406: Intend to create an -fPIC library package...

2009-07-21 Thread Wouter Verhelst
On Tue, Jul 21, 2009 at 12:40:17AM +0200, Christian Hammers wrote: > Am Mon, 20 Jul 2009 23:18:23 +0100 > schrieb Roger Leigh : > > If other libraries are including this library, then why is libmysqld > > not being provided as a properly-versioned shared object? > > Upstream, in this case Monty hi

Bug#508406: Intend to create an -fPIC library package...

2009-07-20 Thread Christian Hammers
Am Mon, 20 Jul 2009 23:18:23 +0100 schrieb Roger Leigh : > On Mon, Jul 20, 2009 at 11:10:11PM +0200, Christian Hammers wrote: > > Hello > > > > In the Cc'ed bug report we were asked to created a libmysqld-pic > > package that only contains libmysqld_pic.a which should be compiled > > with -fPIC.

Bug#508406: Intend to create an -fPIC library package...

2009-07-20 Thread Roger Leigh
On Mon, Jul 20, 2009 at 11:10:11PM +0200, Christian Hammers wrote: > Hello > > In the Cc'ed bug report we were asked to created a libmysqld-pic package that > only contains libmysqld_pic.a which should be compiled with -fPIC. > As I'm no library expert I gladly follow the recommendation of Policy

Bug#508406: Intend to create an -fPIC library package...

2009-07-20 Thread Christian Hammers
Hello In the Cc'ed bug report we were asked to created a libmysqld-pic package that only contains libmysqld_pic.a which should be compiled with -fPIC. As I'm no library expert I gladly follow the recommendation of Policy ยง10.2 and ask for comments :) The reason for creating this package was that l