Bug#489019: glibc 2.7 build configuration not suitable for Vortex86SX chip (486 compatible)

[Islam Samir Badrel-Dein]

Aurelien Jarno wrote:

Islam Samir Badrel-Dein a écrit :
  

Aurelien Jarno wrote:


Could you please use gdb to find the offending instruction?

  
  

Unfortunately I don't have gdb on my target as it is all compiled from



Then please generate a core on the machine, and examine it on another
machine where you can install gdb.

  
Sorry, but I really don't understand what this means or how to do it? I 
am still newbie to embedded Linux :) Anyway, I'll try soon to install 
Debian Sarge or even puppylinux on this machine to have access to gdb 
and all other stuff. I'll try it then!


-Islam

Bug#489019: glibc 2.7 build configuration not suitable for Vortex86SX chip (486 compatible)

[Aurelien Jarno]

Islam Samir Badrel-Dein a écrit :
> Aurelien Jarno wrote:
>>
>> Could you please use gdb to find the offending instruction?
>>
>>   
> 
> Unfortunately I don't have gdb on my target as it is all compiled from

Then please generate a core on the machine, and examine it on another
machine where you can install gdb.

> scratch. Anyway I think the real problem is the build configurations. It
> seems that the glibc is NOT compiled for generic i386, rather it seems

i386 support has been removed sometimes ago. You now need at least an
i486 processor.

> to be compiled for 686, this is why even static linking fails. Please
> note that my target is a STRICT 486 processor.

That's wrong, the glibc is clearly compiled for an i486 CPU. Your
processor is probably lacking a feature compared to the original i486 one.

-- 
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian developer   | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net



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

Bug#489019: glibc 2.7 build configuration not suitable for Vortex86SX chip (486 compatible)

[Islam Samir Badrel-Dein]

Aurelien Jarno wrote:


Could you please use gdb to find the offending instruction?

  


Unfortunately I don't have gdb on my target as it is all compiled from 
scratch. Anyway I think the real problem is the build configurations. It 
seems that the glibc is NOT compiled for generic i386, rather it seems 
to be compiled for 686, this is why even static linking fails. Please 
note that my target is a STRICT 486 processor.


-Islam



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

Bug#489019: glibc 2.7 build configuration not suitable for Vortex86SX chip (486 compatible)

[Aurelien Jarno]

Islam Samir Badrel-Dein a écrit :
> Package:  libc6
> Version: 2.7-10
> 
> Compiling any program, even hello world, against this library produces
> binaries not working on any Vortex86SX-based system. The program does
> not execute and produces "Illegal Instruction" error message. This is
> always the case even when compiling as static binary with the
> -march=i486 flag. Compiling the same program using libc6 version 2.3.6
> (etch) resulted in a working *static* executable, though shared
> libraries executables still produce the same bug. The only configuration
> that worked for me was using libc6 version 2.3.2 (sarge).
> 

Could you please use gdb to find the offending instruction?

-- 
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian developer   | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net



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

Bug#489019: glibc 2.7 build configuration not suitable for Vortex86SX chip (486 compatible)

[Islam Samir Badrel-Dein]

Package:  libc6
Version: 2.7-10

Compiling any program, even hello world, against this library produces 
binaries not working on any Vortex86SX-based system. The program does 
not execute and produces "Illegal Instruction" error message. This is 
always the case even when compiling as static binary with the 
-march=i486 flag. Compiling the same program using libc6 version 2.3.6 
(etch) resulted in a working *static* executable, though shared 
libraries executables still produce the same bug. The only configuration 
that worked for me was using libc6 version 2.3.2 (sarge).


The details of the whole process are on this forum 
 
(http://ubuntuforums.org/showthread.php?t=841783). I posted it there 
first as I thought it is a 64 bit problem while running Ubuntu Hardy 8.04.



I am using Debian GNU/Linux 4.0 with mixed stable/testing repos.

$gcc --version
gcc (Debian 4.3.1-2) 4.3.1

$/lib/libc.so.6
GNU C Library stable release version 2.7, by Roland McGrath et al.
Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 4.2.3 (Debian 4.2.3-3).
Compiled on a Linux >>2.6.24.4<< system on 2008-03-28.
Available extensions:
   crypt add-on version 2.1 by Michael Glad and others
   GNU Libidn by Simon Josefsson
   Native POSIX Threads Library by Ulrich Drepper et al
   BIND-8.2.3-T5B
For bug reporting instructions, please see:
.


$uname -a
Linux debian 2.6.18-6-686 #1 SMP Sun Feb 10 22:11:31 UTC 2008 i686 
GNU/Linux.