Package: nscd
Version: 2.7-18
Severity: important
Hi,
I just upgraded nscd from version 2.3.6.ds1-13etch8 to 2.7-18 and it
started using 100% CPU. In fact it starts using 100% CPU a few seconds
after it was started.
I tried to run it in debug mode (nscd -d), and it also starts using 100%
CPU
Your message dated Fri, 30 Jan 2009 08:58:37 -0500
with message-id <20090130135837.ga25...@caradoc.them.org>
and subject line Re: Bug#513341: doesn't contain debugging symbols
has caused the Debian Bug report #513341,
regarding doesn't contain debugging symbols
to be marked as done.
This means th
The problem is not with building other packages. the problem is building glibc
itself.
there is a cotradiction between the definition by gcc and the code used in
glibc assebler files.
On יום שישי 30 ינואר 2009 11:25:20 Bastian Blank wrote:
> On Fri, Jan 30, 2009 at 10:37:57AM +0200, Yoram bar ha
Your message dated Fri, 30 Jan 2009 10:36:27 +0100
with message-id <20090130093627.ga11...@artemis.corp>
and subject line Re: Bug#513564: glibc: Please redefine __i686 to work-around
the infamous i686 compilation fail
has caused the Debian Bug report #513564,
regarding glibc: Please redefine __i6
On Fri, Jan 30, 2009 at 10:37:57AM +0200, Yoram bar haim wrote:
> When compiling with gcc that uses march=i686 (or any sub-arch) gcc defines
> __i686 to be 1, that causes instructions such as
> ..ifndef __i686.get_pc_thunk.reg;
> to fail as syntax error (because the prefix is 1).
> if you force it
Package: glibc
Version: 2.7-18
Severity: grave
Justification: renders package unusable
When compiling with gcc that uses march=i686 (or any sub-arch) gcc defines
__i686 to be 1, that causes instructions such as
..ifndef __i686.get_pc_thunk.reg;
to fail as syntax error (because the prefix is 1).
i
6 matches
Mail list logo
