Your message dated Thu, 22 Apr 2010 19:28:26 +0200
with message-id <[email protected]>
and subject line No longer applies
has caused the Debian Bug report #450643,
regarding tcc: Fails to link ("/usr/lib/libc_nonshared.a:
'__i686.get_pc_thunk.bx' defined twice")
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
450643: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=450643
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tcc
Version: 0.9.24~cvs20070502-2
Severity: important
tcc compiles fine, but linking fails. I originally tried to compile
Warzone with tcc, but reproduced this with beav from Debian (just change
the compiler in the Makefile to tcc).
As I said, compilation works fine, but linking fails with the following
error:
/usr/lib/libc_nonshared.a: '__i686.get_pc_thunk.bx' defined twice
Running tcc as an interpreter (ex1.c and ex4.c from the tcc source)
still works.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (900, 'unstable'), (800, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.22.12-ck1-2 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_GB.utf8)
Shell: /bin/sh linked to /bin/dash
Versions of packages tcc depends on:
ii libc6 2.6.1-6 GNU C Library: Shared libraries
Versions of packages tcc recommends:
ii libc6-dev [libc-dev] 2.6.1-6 GNU C Library: Development Librari
-- no debconf information
--
You should never wear your best trousers when you go out to fight for
freedom and liberty.
-- Henrik Ibsen
--- End Message ---
--- Begin Message ---
I can't reproduce this neither with tcc-0.9.25-1, nor with tcc-0.9.24-1.
Please don't hesitate to reopen this bug if you're still experiencing this
bug.
--- End Message ---
