Bug#283461: new patch glibc232-nptl-pthread to build g++/libsupc++ with nptl headers

2004-11-29 Thread GOTO Masanori
At Mon, 29 Nov 2004 08:39:10 +0100,
Matthias Klose wrote:
> diff -u glibc-2.3.2.ds1/debian/changelog glibc-2.3.2.ds1/debian/changelog
> --- glibc-2.3.2.ds1/debian/changelog
> +++ glibc-2.3.2.ds1/debian/changelog
> @@ -1,3 +1,10 @@
> +glibc (2.3.2.ds1-18ubuntu3) hoary; urgency=low
> +
> +  * glibc232-nptl-pthread: New patch, taken from upstream CVS: Do not
> +use C99 designators, as C++ does not have support for them.
> +
> + -- Matthias Klose <[EMAIL PROTECTED]>  Mon, 29 Nov 2004 00:11:44 +0100

Did you see why this patch is existed? (#275997).

Regards,
-- gotom


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Processed: Re: Bug#283461: new patch glibc232-nptl-pthread to build g++/libsupc++ with nptl headers

2004-11-29 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

> severity 283461 important
Bug#283461: new patch glibc232-nptl-pthread to build g++/libsupc++ with nptl 
headers
Severity set to `important'.

> merge 283461 275997
Bug#275997: seq24: FTBFS on amd64: mutex.cpp:24: error: parse error before `.' 
token
Bug#283461: new patch glibc232-nptl-pthread to build g++/libsupc++ with nptl 
headers
Mismatch - only Bugs in same state can be merged:
Values for `package' don't match:
 #275997 has `seq24';
 #283461 has `glibc'

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#281815: marked as done (glibc: Please change cryptic error message: "Servname not supported for ai_socktype")

2004-11-29 Thread Debian Bug Tracking System
Your message dated Tue, 30 Nov 2004 00:59:15 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#281815: glibc: Please change cryptic error message: 
"Servname not supported for ai_socktype"
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 responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 17 Nov 2004 23:20:16 +
>From [EMAIL PROTECTED] Wed Nov 17 15:20:16 2004
Return-path: <[EMAIL PROTECTED]>
Received: from master.debian.org [146.82.138.7] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CUZ5z-0006Xf-00; Wed, 17 Nov 2004 15:20:16 -0800
Received: from rcm-200-220-132-60.nipnet.net.br (khazad-dum.debian.net) 
[200.220.132.60] 
by master.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CUZ5z-00063G-00; Wed, 17 Nov 2004 17:20:15 -0600
Received: from localhost (localhost [127.0.0.1])
by localhost.khazad-dum.debian.net (Postfix) with ESMTP id 633FD20612F;
Wed, 17 Nov 2004 21:20:10 -0200 (BRST)
Received: from khazad-dum.debian.net ([127.0.0.1])
by localhost (khazad-dum [127.0.0.1]) (amavisd-new, port 10024)
with LMTP id 17535-02-2; Wed, 17 Nov 2004 21:20:09 -0200 (BRST)
Received: by khazad-dum.debian.net (Postfix, from userid 1000)
id EAB59200142; Wed, 17 Nov 2004 21:20:09 -0200 (BRST)
Date: Wed, 17 Nov 2004 21:20:09 -0200
From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: glibc: Please change cryptic error message: "Servname not supported 
for ai_socktype"
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Reportbug-Version: 3.2
X-GPG-Fingerprint-1: 1024D/128D36EE 50AC 661A 7963 0BBA 8155  43D5 6EF7 F36B 
128D 36EE
X-GPG-Fingerprint-2: 1024D/1CDB0FE3 5422 5C61 F6B7 06FB 7E04  3738 EE25 DE3F 
1CDB 0FE3
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at khazad-dum.debian.net
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: glibc
Severity: wishlist

It is nearly impossible for an user to understand what the hell "Servname
not supported for ai_socktype" means.  Please at least change that to
"Socket service name unknown", or something else that makes sense to someone
who DOES NOT write Unix socket code...

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.28-rc1-debian5+skas+lmsensors+3c59xvlan+lmlbt4x
Locale: LANG=pt_BR, LC_CTYPE=pt_BR (charmap=ISO-8859-1)

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

---
Received: (at 281815-done) by bugs.debian.org; 29 Nov 2004 15:59:16 +
>From [EMAIL PROTECTED] Mon Nov 29 07:59:16 2004
Return-path: <[EMAIL PROTECTED]>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CYnvo-0001UL-00; Mon, 29 Nov 2004 07:59:16 -0800
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
by webmasters.gr.jp (Postfix) with ESMTP
id DAA5CDEB3B; Tue, 30 Nov 2004 00:59:15 +0900 (JST)
Date: Tue, 30 Nov 2004 00:59:15 +0900
Message-ID: <[EMAIL PROTECTED]>
From: GOTO Masanori <[EMAIL PROTECTED]>
To: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: Re: Bug#281815: glibc: Please change cryptic error message: "Servname 
not supported for ai_socktype"
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
 FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
 (i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
autolearn=no version=2.60-bugs.debi

Trovato virus nel messaggio "Extended Mail"

2004-11-29 Thread Grazia Beolchi
Symantec AntiVirus ha trovato un virus in un allegato inviato da 
([EMAIL PROTECTED] <[EMAIL PROTECTED]>) a [EMAIL 
PROTECTED]

Per garantire che i destinatari possano utilizzare i file inviati, eseguire una 
scansione dei virus, ripulire eventuali file infetti e inviare di nuovo 
l'allegato.


Allegato:  document_info.txt
   .pif
Minaccia: [EMAIL PROTECTED]
Azione intrapresa:  Quarantena riuscito
Stato file:  Infetto



<>

Bug#281815: glibc: Please change cryptic error message: "Servname not supported for ai_socktype"

2004-11-29 Thread Henrique de Moraes Holschuh
On Tue, 30 Nov 2004, GOTO Masanori wrote:
> At Wed, 17 Nov 2004 21:20:09 -0200,
> Henrique de Moraes Holschuh wrote:
> > It is nearly impossible for an user to understand what the hell "Servname
> > not supported for ai_socktype" means.  Please at least change that to
> > "Socket service name unknown", or something else that makes sense to someone
> > who DOES NOT write Unix socket code...
> 
> I don't think it's big difference between the original message and
> your proposed one.  Note that at least FreeBSD and Solaris8 uses your

There is a quite big one, Goto-san.  "Servname" is not defined anywhere, it
does not exist as a word, it is not on the top of a comment in
"/etc/services", and it is not documented in services(5) either. It is not
documented even in any of the getserv* manpages.

"Service name" is at least something that can be understood by someone that
knows what a "service" is. And the fact that there is a 'services' database
in nsswitch.conf and there is an /etc/services file, and that apropos
services gives an useful pointer to services(5) makes a LOT of difference.

IMHO a very good error message would be something like:
"Service name %s not in the system socket service name database".  

But this is probably not doable, so we would have to go with something less
helpful, but still easy to understand, like:
"Service name is unknown to the system socket service name database".

Text about "ai_socktype" in a user-visible error message is completely,
utterly useless for anyone that does not do Unix socket programming.  And
"Servname" is something that we can only infer to mean something if we already
have a damn good idea of what the error message could be talking about in
the first place...

> Closed.  But if you have another opinion, and that makes really sense,
> I would reconsider it.  In that case, please discuss it with us.

Well, I have explained my POV better, now. And I gave an example of a good
message that is very different from the original one.

Please reconsider changing this error message, there is no reason to keep an
obscure error message THIS obscure. Especially when people hit the problem
quite often.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: libunwind in unstable

2004-11-29 Thread Peter Chubb
> "Matthias" == Matthias Klose <[EMAIL PROTECTED]> writes:

Matthias> Matthieu Delahaye writes:
>> On Wed, 2004-11-24 at 17:36, Ian Wienand wrote: > On Wed, Nov 24,
>> 2004 at 12:46:12AM +0100, Matthias Klose wrote: > > ok, Ian, if
>> it's ok with you, I'll prepare a libunwind upload, which > > plays
>> well with a libgcc1 package including the libunwind7 shared > >
>> libs.

Matthias> please review the attached patch. you find the corresponding
Matthias> gcc package at http://people.debian.org/~doko/gcc-ia64/


I don't know what's happened, but apt-get upgrade this morning broke
the world.


Errors were encountered while processing:
 /var/cache/apt/archives/nano_1.2.4-3_ia64.deb
 /var/cache/apt/archives/procps_1%3a3.2.4-1_ia64.deb
 /var/cache/apt/archives/python2.3_2.3.4-16_ia64.deb
 /var/cache/apt/archives/ethereal_0.10.7-3_ia64.deb
 /var/cache/apt/archives/pppconfig_2.3.9_all.deb
 /var/cache/apt/archives/tasksel_2.15_all.deb
 /var/cache/apt/archives/timidity_2.13.2-5_ia64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
: berry-uni; 
: berry-uni; sudo apt-get install libunwind
apt-get: error while loading shared libraries: libunwind.so.7: cannot
open shared object file: No such file or directory
: berry-uni; sudo apt-get install libgcc   
apt-get: error while loading shared libraries: libunwind.so.7: cannot
open shared object file: No such file or directory


I had to fetch libunwind7 manually and install it before I could proceed.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: libunwind in unstable

2004-11-29 Thread Matthieu Delahaye

> 
> please review the attached patch. you find the corresponding gcc
> package at http://people.debian.org/~doko/gcc-ia64/
> 
>   Matthias
> 

FYI:
Accepted:
libunwind-setjmp0-dev_0.98.3-2_ia64.deb
  to pool/main/libu/libunwind/libunwind-setjmp0-dev_0.98.3-2_ia64.deb
libunwind-setjmp0_0.98.3-2_ia64.deb
  to pool/main/libu/libunwind/libunwind-setjmp0_0.98.3-2_ia64.deb
libunwind7-dev_0.98.3-2_ia64.deb
  to pool/main/libu/libunwind/libunwind7-dev_0.98.3-2_ia64.deb
libunwind7_0.98.3-2_ia64.deb
  to pool/main/libu/libunwind/libunwind7_0.98.3-2_ia64.deb
libunwind_0.98.3-2.diff.gz
  to pool/main/libu/libunwind/libunwind_0.98.3-2.diff.gz
libunwind_0.98.3-2.dsc
  to pool/main/libu/libunwind/libunwind_0.98.3-2.dsc
Announcing to [EMAIL PROTECTED]


Thank you for your contribution to Debian.



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Bug#283597: [PATCH] more patch

2004-11-29 Thread NIIBE Yutaka
Sorry, two more files are needed.  Please apply this patch
after applying the patch I send earlier.

GNU C library has successfully (cross) compiled with those header
files.

  * include/asm-m32r/{m32r.h,page.h}: New files.

 -- NIIBE Yutaka <[EMAIL PROTECTED]>  Tue, 30 Nov 2004 11:50:50 +0900

diff -u linux-kernel-headers-2.5.999-test7-bk/include/asm-m32r/README 
linux-kernel-headers-2.5.999-test7-bk/include/asm-m32r/README
--- linux-kernel-headers-2.5.999-test7-bk/include/asm-m32r/README
+++ linux-kernel-headers-2.5.999-test7-bk/include/asm-m32r/README
@@ -1,5 +1,9 @@
 From Linux M32R project, for 2.6.9-rc1
 
+Custom version:
+   page.h
+   m32r.h
+
 Removed following subdirectories, because those are target specific
 and never related to user space.
m32700ut/
@@ -25,7 +29,6 @@
local.h
m32102.h
m32102peri.h
-   m32r.h
m32r_mp_fpga.h
mc146818rtc.h
mmu.h
@@ -33,7 +36,6 @@
mmzone.h
namei.h
numnodes.h
-   page.h
percpu.h
pgalloc.h
pgtable-2level.h
--- linux-kernel-headers-2.5.999-test7-bk.orig/include/asm-m32r/page.h
+++ linux-kernel-headers-2.5.999-test7-bk/include/asm-m32r/page.h
@@ -0,0 +1,10 @@
+#ifndef _ASM_M32R_PAGE_H
+#define _ASM_M32R_PAGE_H
+
+/* PAGE_SHIFT determines the page size */
+#define PAGE_SHIFT 12
+#define PAGE_SIZE  (1UL << PAGE_SHIFT)
+#define PAGE_MASK  (~(PAGE_SIZE-1))
+
+#endif /* _ASM_M32R_PAGE_H */
+
--- linux-kernel-headers-2.5.999-test7-bk.orig/include/asm-m32r/m32r.h
+++ linux-kernel-headers-2.5.999-test7-bk/include/asm-m32r/m32r.h
@@ -0,0 +1,33 @@
+#ifndef _ASM_M32R_M32R_H_
+#define _ASM_M32R_M32R_H_
+
+/* 
+ * Mitsubishi M32R processor
+ * Copyright (C) 1997-2002, Mitsubishi Electric Corporation
+ */
+
+/*
+ * PSW (Processor Status Word)
+ */
+
+/* PSW bit */
+#define M32R_PSW_BIT_SM   (7)/* Stack Mode */
+#define M32R_PSW_BIT_IE   (6)/* Interrupt Enable */
+#define M32R_PSW_BIT_PM   (3)/* Processor Mode [0:Supervisor,1:User] */
+#define M32R_PSW_BIT_C(0)/* Condition */
+#define M32R_PSW_BIT_BSM  (7+8)  /* Backup Stack Mode */
+#define M32R_PSW_BIT_BIE  (6+8)  /* Backup Interrupt Enable */
+#define M32R_PSW_BIT_BPM  (3+8)  /* Backup Processor Mode */
+#define M32R_PSW_BIT_BC   (0+8)  /* Backup Condition */
+
+/* PSW bit map */
+#define M32R_PSW_SM   (1UL<< M32R_PSW_BIT_SM)   /* Stack Mode */
+#define M32R_PSW_IE   (1UL<< M32R_PSW_BIT_IE)   /* Interrupt Enable */
+#define M32R_PSW_PM   (1UL<< M32R_PSW_BIT_PM)   /* Processor Mode */
+#define M32R_PSW_C(1UL<< M32R_PSW_BIT_C)/* Condition */
+#define M32R_PSW_BSM  (1UL<< M32R_PSW_BIT_BSM)  /* Backup Stack Mode */
+#define M32R_PSW_BIE  (1UL<< M32R_PSW_BIT_BIE)  /* Backup Interrupt Enable */
+#define M32R_PSW_BPM  (1UL<< M32R_PSW_BIT_BPM)  /* Backup Processor Mode */
+#define M32R_PSW_BC   (1UL<< M32R_PSW_BIT_BC)   /* Backup Condition */
+
+#endif /* _ASM_M32R_M32R_H_ */


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]