Re: Package requiring a customised version of another package

2007-08-23 Thread David Given
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin Pryzby wrote: [...] >> which means the >> preloader library doesn't get a chance to override it. plasticfs wants a >> glibc >> compiled with --disable-hidden-plt to expose this interface. > I still don't understand why? I *presume* so that pla

Re: Package requiring a customised version of another package

2007-08-23 Thread Justin Pryzby
On Thu, Aug 23, 2007 at 10:26:35PM +0100, David Given wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Justin Pryzby wrote: > [...] > >> I have an application I'd like to package --- plasticfs. Unfortunately, > >> due to > >> glibc weirdnesses, it needs a copy of glibc built using cus

Re: Package requiring a customised version of another package

2007-08-23 Thread David Given
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Justin Pryzby wrote: [...] >> I have an application I'd like to package --- plasticfs. Unfortunately, due >> to >> glibc weirdnesses, it needs a copy of glibc built using custom (non-standard) >> options. Is this doable, or is it likely to be a lost c

Re: Package requiring a customised version of another package

2007-08-23 Thread Justin Pryzby
On Thu, Aug 23, 2007 at 08:56:50PM +0100, David Given wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I have an application I'd like to package --- plasticfs. Unfortunately, due to > glibc weirdnesses, it needs a copy of glibc built using custom (non-standard) > options. Is this doabl

Package requiring a customised version of another package

2007-08-23 Thread David Given
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have an application I'd like to package --- plasticfs. Unfortunately, due to glibc weirdnesses, it needs a copy of glibc built using custom (non-standard) options. Is this doable, or is it likely to be a lost cause? Note: it doesn't need the customi