I am not able to reproduce this bug anymore!! I am compiling using Lenny
gcc and glibc and no errors are encountered. I think this bug should be
marked invalid, I'll continue compiling programs from Lenny until this
bug shows up again, or as I hope, everything goes smoothly.
Thanks much for yo
Once again, what is the kernel of your TARGET system, i.e. on Vortex86SX
chip. Is it really 2.6.25.5 with FPU emulation enabled ?
Yes, the kernel for the TARGET system is 2.6.25.5 from Kernel.org with no
patches and with FPU emulation enabled.
Or 2.6.25.5 is version available on the system, whe
Petr Salinger wrote:
Once again, what is the kernel of your TARGET system, i.e. on
Vortex86SX chip. Is it really 2.6.25.5 with FPU emulation enabled ?
Yes, the kernel for the TARGET system is 2.6.25.5 from Kernel.org with
no patches and with FPU emulation enabled.
Or 2.6.25.5 is version avai
What is the kernel of your target system
Once again, what is the kernel of your TARGET system, i.e. on Vortex86SX
chip. Is it really 2.6.25.5 with FPU emulation enabled ?
Or 2.6.25.5 is version available on the system, where you are building
packages ?
How did you installed debian/libraries
Petr Salinger wrote:
You did not answer my very important question:
What is the kernel of your target system
Sorry, I really forgot to answer it! My kernel is 2.6.25.5, so lenny/sid
should be no problem. The point is: my installation is on a VirtualBox
virtual machine. I installed Debian
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 t
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
environmen
Petr Salinger wrote:
Hi,
it looks like you use 64 bit environment.
Is it true ?
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 deboot
Petr Salinger wrote:
Hi,
it looks like you use 64 bit environment.
Is it true ?
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 deboot
9 matches
Mail list logo
