Resurrecting a very old thread:
On Tue, May 13, 2014 at 11:02 AM, Jakub Jelinek wrote:
> On Tue, May 13, 2014 at 06:56:40PM +0200, Sandro Mani wrote:
> > apitrace 5.0 bundles libbacktrace, which looks like is living within
> > the gcc sources. libbacktrace is not build as a shared library from
>
On 2015-01-08, 03:36 GMT, Richard Shaw wrote:
> In the specific case I ran into one of the package suites I've been working
> on technically bundles a modified copy of xmlrpcpp. However, it is quite
> modified, upstream is dead, it's not already in Fedora, and the author I'm
> working with only use
On Wed, Jan 7, 2015 at 7:39 PM, Adam Williamson
wrote:
>
> On Tue, 2014-08-19 at 15:19 +0400, Pavel Alexeev wrote:> Sorry for the old
> thread.
> > But it is very interesting question to clearly determine "bundled
> > library" to which returning happened again and again.
> > Does it hang again no
On Tue, 2014-08-19 at 15:19 +0400, Pavel Alexeev wrote:
> 13.06.2014 01:42, Adam Williamson пишет:
> > On Tue, 2014-05-13 at 18:56 +0200, Sandro Mani wrote:
> > > Hi,
> > >
> > > apitrace 5.0 bundles libbacktrace, which looks like is living
> > > within the
> > > gcc sources. libbacktrace is not
13.06.2014 01:42, Adam Williamson пишет:
> On Tue, 2014-05-13 at 18:56 +0200, Sandro Mani wrote:
>> Hi,
>>
>> apitrace 5.0 bundles libbacktrace, which looks like is living within the
>> gcc sources. libbacktrace is not build as a shared library from the gcc
>> sources, and not packaged.
>>
>> Is
On Tue, 2014-05-13 at 18:56 +0200, Sandro Mani wrote:
> Hi,
>
> apitrace 5.0 bundles libbacktrace, which looks like is living within the
> gcc sources. libbacktrace is not build as a shared library from the gcc
> sources, and not packaged.
>
> Is it feasible to build libbacktrace as a shared li
On 13.05.2014 19:08, Sandro Mani wrote:
On 13.05.2014 19:02, Jakub Jelinek wrote:
On Tue, May 13, 2014 at 06:56:40PM +0200, Sandro Mani wrote:
apitrace 5.0 bundles libbacktrace, which looks like is living within
the gcc sources. libbacktrace is not build as a shared library from
the gcc sourc
On 13.05.2014 19:02, Jakub Jelinek wrote:
On Tue, May 13, 2014 at 06:56:40PM +0200, Sandro Mani wrote:
apitrace 5.0 bundles libbacktrace, which looks like is living within
the gcc sources. libbacktrace is not build as a shared library from
the gcc sources, and not packaged.
Is it feasible to b
On Tue, May 13, 2014 at 06:56:40PM +0200, Sandro Mani wrote:
> apitrace 5.0 bundles libbacktrace, which looks like is living within
> the gcc sources. libbacktrace is not build as a shared library from
> the gcc sources, and not packaged.
>
> Is it feasible to build libbacktrace as a shared librar
