Islam Samir Badrel-Dein a écrit :
> Petr Salinger wrote:
>> Hi,
>>
>> it looks like you use 64 bit environment.
>> Is it true ?
>>

Could you please clearly answer this question? You original bug report
only mentions packages (glibc, kernel) from a plain i386 installation.

The CPU support is not the same for i386 and amd64 distributions.


>> The "gcc -m32 -march=486" will produce i486 compliant code, BUT
>> the startup files and whole glibc is compiled with -march=686,
>> so the resulting binary wouldn't be.
>>
>> You have to use 32 bit chroot, see also man debootstrap.
>>
>> What is the kernel of your target system,
>> does FPU emulation work correctly ?
>> How output of "cat /proc/cpuinfo" looks ?
>>
>> Petr
>>
> Hello Petr,
> 
> That what I realized early enough after I encountered many failures and
> thats why I started to try older and older versions of Debian on a VM.
> The only version that worked was Debian oldstable (Sarge). It seems the
> glibc was compiled for 486 then. I am filing this bug more-of a (wish)
> than a (bug). There should be someway for developers to compile code
> that would work correctly on any i386 target
> without having to chroot in another environment. This is the purpose of
> the -m32 and the multilib anyway!!
> 
> Thanks,
> Islam
> 
> 
> 


-- 
  .''`.  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]

Reply via email to