Hello,
On 06-Feb-10 12:58, Aurelien Jarno wrote:
The '--includedir=/usr/include/i386-linux' is also no longer necessary
because this is handled automagically by the wrappers in
linux-kernel-headers.
This is not the include path of the kernel headers, but the place were
to install the
On Wed, Feb 08, 2006 at 04:58:13PM +0100, Denis Barbier wrote:
[Clint Adams]
Okay. Any remaining reasons not to upload it?
Also could we please wait few days more until -13 enter testing?
This version is listed as a valid candidate in update_excuses, so
it will enter testing today if no new
Hi,
It seems the patch to fix the bug#333766 also fixes this bug. I have
built a glibc with gcc-4.0, and executed the testcase given in this bug
report. The output it the same as the expected one.
Could we consider this bug as fixed, or is it only a postive side effect
of the patch fo
Your message dated Sat, 11 Feb 2006 17:52:55 +0100
with message-id [EMAIL PROTECTED]
and subject line libc6: strtold is broken on hppa
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
reopen 344836
thanks
John David Anglin a écrit :
As this is not a bug, I am closing this bug report.
But there is still a problem ...
#define _ISOC99_SOURCE
#include stdlib.h
#include stdio.h
int
main ()
{
printf (%Lf\n, strtold (1, NULL));
return 0;
}
[EMAIL PROTECTED]:~/gcc_test$ gcc
Aurelien Jarno a écrit :
Could you please tell me where to find this version of the glibc, and
also the sources? I can then find the patch and include it in the Debian
package.
OK, I have found the fix in the CVS, I am currently doing a test build.
Aurelien
--
.''`. Aurelien Jarno
Processing commands for [EMAIL PROTECTED]:
reopen 344836
Bug#344836: libc6: strtold is broken on hppa
Bug reopened, originator not changed.
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
Aurelien Jarno a écrit :
Could you please tell me where to find this version of the glibc, and
also the sources? I can then find the patch and include it in the Debian
package.
OK, I have found the fix in the CVS, I am currently doing a test build.
Great.
If you are doing this,
John David Anglin a écrit :
Aurelien Jarno a écrit :
Could you please tell me where to find this version of the glibc, and
also the sources? I can then find the patch and include it in the Debian
package.
OK, I have found the fix in the CVS, I am currently doing a test build.
Great.
Package: libc6
Version: 2.3.5-13
Severity: wishlist
Tags: patch l10n
Hello,
Would you please be so kind to apply the attached patch (or alternatively
use the fully updated pt_BR.po file also attached) so libc6's Brazilian
Portuguese (pt_BR) translation would be up-to-date again ?
Thanks,
--
tag 344836 + patch
thanks
On Sat, Feb 11, 2006 at 07:09:34PM +0100, Aurelien Jarno wrote:
Aurelien Jarno a écrit :
Could you please tell me where to find this version of the glibc, and
also the sources? I can then find the patch and include it in the Debian
package.
OK, I have found
Processing commands for [EMAIL PROTECTED]:
tag 344836 + patch
Bug#344836: libc6: strtold is broken on hppa
There were no tags set.
Tags added: patch
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
Author: barbier
Date: 2006-02-11 20:28:02 + (Sat, 11 Feb 2006)
New Revision: 1168
Modified:
glibc-package/trunk/debian/changelog
glibc-package/trunk/debian/po/pt_BR.po
Log:
Update Brazilian Portuguese debconf translation, by Andr?\195?\169
Lu?\195?\173s Lopes
Modified:
Author: schizo
Date: 2006-02-12 00:26:38 + (Sun, 12 Feb 2006)
New Revision: 1169
Modified:
glibc-package/trunk/debian/changelog
Log:
rewrite history
Modified: glibc-package/trunk/debian/changelog
===
---
glibc_2.3.6-1_all.changes uploaded successfully to localhost
along with the files:
glibc_2.3.6-1.dsc
glibc_2.3.6.orig.tar.gz
glibc_2.3.6-1.diff.gz
glibc-doc_2.3.6-1_all.deb
locales_2.3.6-1_all.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL
Accepted:
glibc-doc_2.3.6-1_all.deb
to pool/main/g/glibc/glibc-doc_2.3.6-1_all.deb
glibc_2.3.6-1.diff.gz
to pool/main/g/glibc/glibc_2.3.6-1.diff.gz
glibc_2.3.6-1.dsc
to pool/main/g/glibc/glibc_2.3.6-1.dsc
glibc_2.3.6.orig.tar.gz
to pool/main/g/glibc/glibc_2.3.6.orig.tar.gz
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#225516: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#227214: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#248377: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#279697: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#295810: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#309846: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#323159: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#329428: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#327025: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#334864: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#331377: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#343885: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#345479: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#345641: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#347315: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#347323: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#347686: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#348518: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:10 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#348804: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
Your message dated Sat, 11 Feb 2006 16:47:11 -0800
with message-id [EMAIL PROTECTED]
and subject line Bug#350103: fixed in glibc 2.3.6-1
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your
36 matches
Mail list logo
