Your message dated Fri, 08 Oct 2004 11:37:52 +0900
with message-id <[EMAIL PROTECTED]>
and subject line Bug#213051: libc6-dev: gcc-2.95 -static fails: "undefined reference 
to `.udiv'"
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; 27 Sep 2003 23:59:15 +0000
>From [EMAIL PROTECTED] Sat Sep 27 18:59:13 2003
Return-path: <[EMAIL PROTECTED]>
Received: from p50881d0f.dip.t-dialin.net (moria) [80.136.29.15] 
        by master.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1A3Oy1-0002Oo-00; Sat, 27 Sep 2003 18:59:13 -0500
Received: from argonath-linux.localnet ([10.10.10.71] ident=andreas)
        by moria with esmtp (Exim 3.35 #1 (Debian))
        id 1A3Oxy-0006yE-00; Sun, 28 Sep 2003 01:59:10 +0200
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Andreas Beckmann <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: libc6-dev: gcc-2.95 -static fails: "undefined reference to `.udiv'"
Bcc: Andreas Beckmann <[EMAIL PROTECTED]>
X-Mailer: reportbug 2.29
Date: Sun, 28 Sep 2003 01:58:32 +0200
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hits=-3.8 required=4.0
        tests=HAS_PACKAGE,RCVD_IN_NJABL
        version=2.53-bugs.debian.org_2003_9_21
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_9_21 
(1.174.2.15-2003-03-30-exp)

Package: libc6-dev
Version: 2.3.2-7
Severity: normal

Statically linking a program with gcc-2.95 fails with the following
errors:

$ gcc-2.95 -static test.c
/usr/lib/gcc-lib/sparc-linux/2.95.4/libgcc.a(_udivdi3.o)(.text+0xac): In
function `__udivdi3':
: undefined reference to `.udiv'
/usr/lib/gcc-lib/sparc-linux/2.95.4/libgcc.a(_umoddi3.o)(.text+0xac): In
function `__umoddi3':
: undefined reference to `.udiv'
collect2: ld returned 1 exit status

test.c is just an empty main().

I also checked this problem against the following versions of libc6-dev:
2.3.2-8:     problem occurs
2.2.5-11.5:  works fine
Unfortunately I couldn't find any older 2.3.x .debs

gcc-3.2 and gcc-3.3 both work fine with 2.3.2-7

installed gcc versions:
ii  gcc-2.95                      2.95.4-17     The GNU C compiler.
ii  gcc-3.2                       3.2.3-8       The GNU C compiler
ii  gcc-3.3                       3.3.2-0pre4   The GNU C compiler

-- System Information:
Debian Release: testing/unstable
Architecture: sparc
Kernel: Linux argonath-linux 2.4.22-anbe2-sparc64-smp #1 SMP Thu Sep 25 06:25:50 CEST 
2003 sparc64
Locale: LANG=C, LC_CTYPE=C

Versions of packages libc6-dev depends on:
ii  libc6                         2.3.2-7    GNU C Library: Shared libraries an

-- no debconf information

Is there any other information you need?

Andreas


---------------------------------------
Received: (at 213051-done) by bugs.debian.org; 8 Oct 2004 02:37:53 +0000
>From [EMAIL PROTECTED] Thu Oct 07 19:37:53 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 1CFkdl-0000OK-00; Thu, 07 Oct 2004 19:37:53 -0700
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
        by webmasters.gr.jp (Postfix) with ESMTP
        id 9FEBBDEB84; Fri,  8 Oct 2004 11:37:52 +0900 (JST)
Date: Fri, 08 Oct 2004 11:37:52 +0900
Message-ID: <[EMAIL PROTECTED]>
From: GOTO Masanori <[EMAIL PROTECTED]>
To: Andreas Beckmann <[EMAIL PROTECTED]>,
        [EMAIL PROTECTED]
Subject: Re: Bug#213051: libc6-dev: gcc-2.95 -static fails: "undefined reference to 
`.udiv'"
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[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.debian.org_2004_03_25
X-Spam-Level: 

At Mon, 05 Jul 2004 18:30:38 +0900,
GOTO Masanori wrote:
> > Statically linking a program with gcc-2.95 fails with the following
> > errors:
> > 
> > $ gcc-2.95 -static test.c
> > /usr/lib/gcc-lib/sparc-linux/2.95.4/libgcc.a(_udivdi3.o)(.text+0xac): In
> > function `__udivdi3':
> > : undefined reference to `.udiv'
> > /usr/lib/gcc-lib/sparc-linux/2.95.4/libgcc.a(_umoddi3.o)(.text+0xac): In
> > function `__umoddi3':
> > : undefined reference to `.udiv'
> > collect2: ld returned 1 exit status
> > 
> > test.c is just an empty main().
> > 
> > I also checked this problem against the following versions of libc6-dev:
> > 2.3.2-8:     problem occurs
> > 2.2.5-11.5:  works fine
> > Unfortunately I couldn't find any older 2.3.x .debs
> > 
> > gcc-3.2 and gcc-3.3 both work fine with 2.3.2-7
> 
> I don't know this problem well, but I guess it's one of libgcc-compat
> things.  Using newer gcc fixes this problem, AFAIK.  In addition,
> glibc is unwilling to support static linking.  Nowadays gcc-3.3 is the
> standard compiler in debian, so I think there's no problem.  If you
> have no objection, I'll close this bug.

In the latest sid that has glibc 2.3.2.ds1-17, this bug has been gone
away.  I guess it's libgcc-compat thing.  Thanks for your report.  I
close this bug.

Regards,
-- gotom


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

Reply via email to