[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#513564: marked as done (glibc: Please redefine __i686 to work-around the infamous i686 compilation fail)

Your message dated Fri, 30 Jan 2009 10:36:27 +0100
with message-id <20090130093627.GA11702@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 __i686 to work-around the infamous i686 compilation fail
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 owner@bugs.debian.org
immediately.)


-- 
513564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=513564
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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).
if you force it to be redefid as __i686 it works fine 



-- System Information:
Debian Release: 5.0
  APT prefers testing
  APT policy: (990, 'testing'), (100, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-10
Locale: LANG=he_IL, LC_CTYPE=he_IL (charmap=ISO-8859-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
On Fri, Jan 30, 2009 at 09:25:20AM +0000, Bastian Blank wrote:
> 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 to be redefid as __i686 it works fine 
> 
> Any identifier which starts with two underscores (or one underscore and
> an uppercase letter) is reserved for use by the implementation. You must
> not define them yourself.
> 
> According to the google code search, this code is only used in the
> glibc itself, which obviously built fine.

seconded.
-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

Attachment: pgpfIcjqzGNiL.pgp
Description: PGP signature


--- End Message ---
Reply to: