gilbc compilation error

gilbc compilation error

Post by Spyros Tsioli » Sat, 07 Apr 2001 21:35:25



Hello again people,

I would really appreciate if someone has
an opninion on this :

I installed Mandrake 7.2 on a thinkpad notebook.
Usuall story the thinkpad is a T21, needed a
module patch for its miniPCI network adapter.
That worked fine.

Then off to upgrading X from 4.0 to 4.0.3
(since previous versions don't know about
S3 SavageIX).
And here is the problem :
I 've upgraded all gcc related packages in order
for Glibc (which is needed by XF4.0.3) to be
compiled and installed :

Tried : "rpm --rebuild glibc-2.2.2-blah-i586.rpm"
It goes through the compilation process and then
it comes up with the following error :
----------------------------------------------------
../sysdeps/ieee754/dbl-64/s_modf.c:31: conversion to non-scalar type
requested

../sysdeps/ieee754/dbl-64/s_modf.c:31: confused by earlier errors,
bailing out
----------------------------------------------------

spyros

 
 
 

1. Kernel compilation error: GCC Internal errors 6 and 11

Hello all-
   I'm having problems compiling the kernel in a variety of
situations. Here is the simplest: I install Slackware 2.2 off the
Infomagic March 1995 CD set (kernel 1.2.1) and then do "make config"
followed by "make dep; make clean" and finally just plain "make"

   During the last make, GCC periodically halts with an internal error
either 6 or 11. This has happenned with both GCC 2.6.3 and GCC 2.5.8.
It has also happenned when compliing the 1.3.25 kernel.
   If I delete the incomplete .o file produced at that step and
re-run make, it will crash at the same point (it will skip the files
that are already compiled becuase they are up-to-date). If I enter
the command the failed from the proper director (using cut and paste),
the object file is produced correctly, without error. I can then run
"make" again and it will crank away for a while and then crash again.
It seems to crash at the same files each time. If I continue the process
of manually compiling the .c files that there were problems with,
I *DO* end up with a working kernel!!!

   What's wrong, here? I'm worried that there may be something quirky
with my system's SIMMs. It is a fairly new system:
   P-120 with 32MB of memory, 25MB of swap.

Your comments are greatly appreciated!

Mike Phillips

2. ? Dual Pentium board

3. compilation error: "Error: namespace is not defined."

4. Python Freeze Problem under Linux

5. AFS compilation error "configure: error: no available sys_call_table access method"

6. cscope for Linux

7. Kernel/compilation errors, eth0 errors

8. Why doesn't kill -HUP [pid] work on crontab?

9. Errors Errors Erros in Software compilation in Redhat 9.0

10. Cross compilation compilation problems

11. Compilation errors on Solaris2.7

12. 1.3.57: compilation error

13. -2.4.21-rc6-ac1 _critical_ compilation errors