On Thu, 17 Jun 2010 14:55:05 +0200, Trever L. Adams wrote:
> Valgrind, gcc, abrt, etc. all seem to not get the symbols (debug info)
> for the subpackages in my project with the subpackages. It was picking
> them up in the main packages.
>
> Is this normal?
gcc does not load debuginfo. abrt parti
On 06/16/2010 06:10 AM, Roland McGrath wrote:
> It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> Please explain exactly why this is a problem for you.
>
>
> Thanks,
> Roland
>
Thank you all for responding.
Valgrind, gcc, abrt, etc. all seem to not get the symbols (debug i
On Wed, 2010-06-16 at 09:37 -0400, Adam Jackson wrote:
> On Wed, 2010-06-16 at 05:10 -0700, Roland McGrath wrote:
> > It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> > Please explain exactly why this is a problem for you.
>
> I can't speak to Trever's case, but I can say th
On Wed, 2010-06-16 at 09:47 -0400, Matthias Clasen wrote:
> On Wed, 2010-06-16 at 09:37 -0400, Adam Jackson wrote:
> > I can't speak to Trever's case, but I can say that it's pretty
> > irritating to need debuginfo for every compiler in gcc when all I really
> > need is debuginfo for libgcc:
> >
>
On Wed, 2010-06-16 at 09:47 -0400, Matthias Clasen wrote:
> On Wed, 2010-06-16 at 09:37 -0400, Adam Jackson wrote:
> > On Wed, 2010-06-16 at 05:10 -0700, Roland McGrath wrote:
> > > It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> > > Please explain exactly why this is a prob
On Wed, 2010-06-16 at 09:37 -0400, Adam Jackson wrote:
> On Wed, 2010-06-16 at 05:10 -0700, Roland McGrath wrote:
> > It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> > Please explain exactly why this is a problem for you.
>
> I can't speak to Trever's case, but I can say th
On Wed, 2010-06-16 at 09:32 -0400, Frank Ch. Eigler wrote:
> Roland McGrath writes:
>
> > It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> > Please explain exactly why this is a problem for you.
>
> One possible reason is RPM-level conflicts between concurrently
> installe
On Wed, 2010-06-16 at 09:37 -0400, Adam Jackson wrote:
> On Wed, 2010-06-16 at 05:10 -0700, Roland McGrath wrote:
> > It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> > Please explain exactly why this is a problem for you.
>
> I can't speak to Trever's case, but I can say th
On Wed, 2010-06-16 at 05:10 -0700, Roland McGrath wrote:
> It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> Please explain exactly why this is a problem for you.
I can't speak to Trever's case, but I can say that it's pretty
irritating to need debuginfo for every compiler in
Roland McGrath writes:
> It's normal to get a single foo-debuginfo package from a foo.src.rpm.
> Please explain exactly why this is a problem for you.
One possible reason is RPM-level conflicts between concurrently
installed multilib debuginfo RPMs, such as glibc.i686 and
glibc.x86_64.
- FChE
-
It's normal to get a single foo-debuginfo package from a foo.src.rpm.
Please explain exactly why this is a problem for you.
Thanks,
Roland
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
2010/6/16 Trever L. Adams :
> Hello everyone,
>
> I am having a hard time finding documentation which explains this. I
> have a spec file which generates several subpackages (-classify,
> -clamav, etc.). I have this working fine. The problem is I am only
> getting a debuginfo package for the main p
Hello everyone,
I am having a hard time finding documentation which explains this. I
have a spec file which generates several subpackages (-classify,
-clamav, etc.). I have this working fine. The problem is I am only
getting a debuginfo package for the main package. This contains all the
informati
13 matches
Mail list logo
