This is the mail archive of the libc-alpha@sourceware.cygnus.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

[Craig Metz <cmetz@inner.net>] libc/1184: Latest glibc + toolchain can't really build 386 lib



We've received the append bug report.  Any ideas what's broken here?
How are distribution makers handling this problem - or is there no
problem for you?

Andreas



Topics:
   libc/1184: Latest glibc + toolchain can't really build 386 lib


----------------------------------------------------------------------

Date: Mon, 28 Jun 1999 16:04:01 -0400
From: Craig Metz <cmetz@inner.net>
To: bugs@gnu.org
Subject: libc/1184: Latest glibc + toolchain can't really build 386 lib
Message-Id: <199906281955.TAA19997@inner.net>


>Number:         1184
>Category:       libc
>Synopsis:       Latest glibc + toolchain can't really build 386 lib
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    libc-gnats
>State:          open
>Class:          sw-bug
>Submitter-Id:   unknown
>Arrival-Date:   Mon Jun 28 16:10:01 EDT 1999
>Last-Modified:
>Originator:     Craig Metz
>Organization:
>Release:        libc-2.1.1
>Environment:
386 Linux 2.2
Host type: i386-pc-linux
System: Linux ministry-of-love 2.2.7 #10 Sat May 1 01:45:32 EDT 1999 i686 unknown
Architecture: i686

Addons: linuxthreads crypt

Build CC: gcc
Compiler version: egcs-2.91.66 19990314 (egcs-1.1.2 release)
Kernel headers: 2.2.10
Symbol versioning: yes
Build static: yes
Build shared: yes
Build pic-default: no
Build profile: no
Build omitfp: no
Build bounded: no
Build static-nss: no
Stdio: libio

>Description:

  I'm not sure exactly which program is at fault, but I wanted to get this into
the PR system so it's known about.

  Using egcs 1.1.2, binutils 2.9.1, and glibc 2.9.1, if I build and install a
library using target i386-pc-linux and CC="gcc -m386" (I did verify that the
right flags are getting sent to the compiler), I can build programs with -m386
and they fine on my PII system (well, subject to the other bug I reported).
However, if I run the same binary and libraries on my 386 system, they choke
with SIGILL. I've checked, and this isn't a matter of me grabbing the wrong
library or something like that.

  This worked fine for glibc 2.0.6 and egcs 1.1.1. I haven't tried 2.1 and/or
tried 2.0.6 with the latest toolchain.

>How-To-Repeat:

  Build and install glibc with -m386. Build a substantial program with -m386.
Run it on a real 386.

>Fix:

  Not known.
>Audit-Trail:
>Unformatted:


------------------------------

End of forwardu8D7mR Digest
***************************



-- 
 Andreas Jaeger   aj@arthur.rhein-neckar.de    jaeger@informatik.uni-kl.de
  for pgp-key finger ajaeger@aixd1.rhrk.uni-kl.de

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]