🚀 go-pugleaf

vos@neuretb.biol.ruu.nl (j vos) wrote:

>I have succesfully (that is, so it seems...) compiled glibc-1.09. Happily
>I started to run the tests ('make tests') but now my linker complained:

>collect2: ld returned 1 exit status:
>Undefined:  fltused
>            SYS_sigvec
>            SYS_exit
>            ___curbrk

 Perhaps there is already help gotten by Jan Vos (by email ) but these
things seem quite common, so I answer them here....

 There are a lot missing things from the glibc Makefiles, the
'routines' - lists are not quite perfect:

 The  '__sigvec'  should be mentioned in the signal/Makefile (it is in
the sysdeps/unix - subdirectory).  'exit' and '_exit' should be listed
in the 'routines' in the stdlib/Makefile and so on.....

 Even the routines themselves could be missing, so you must compose
them yourself. For the syscalls this is usually only as a matter of
how many parameters to pass to the syscall.... 

 Doing some 'find -name xxxx.X -print' searches for 'xxxx.S' ,
'xxxx.c', '__xxxx.S', '__xxxx.c'  and looking those files without the
'__' , could give hints where could the needed file be, or are there
any....

>            <and a lot more of 'SYS_...' stuff>

 Because these things are defined in the 'syscall.h',  you of course 
 must have it and the call numbers for the missing 'SYS_sigvec',
'SYS_exit' routines must mentioned there....  There seems to be no
'syscall.h' for BSD-systems in the glibc-1.09....

  If you have some native headers, they perhaps have this header.
Otherwise the syscall-numbers must be get somewhere if they aren't
there.  I remember the Linux-ibcs2 has i386BSD-call numbers in a table
with the iBCS/SYSV numbers, but perhaps they vary on different
architectures.... You can get this header quite surely  from the
NetBSD-sources...

>            _____isinf
>            _____isnam

>I compiled with GCC version 2.7.0 using GAS 1.37.
>My system is a Masscomp 5450 computer with a BSD4.2 'look-alike'
>(I hope it looks good enough) with 68020/68881 CPU/FPU.

 Their 'parent' functions are in the math-subdir, but the routines
'__isinf.c' and '__isnan.c' are probably  in the sysdeps/m68k/fpu, in
your case... Add the names to the math/Makefile's 'routines' -list so
they get compiled and added to the library.
 
>I have no idea where to look further, so please give me some advice!

  Hope this will help and good luck,  I have succeeded to build
glibc-1.09 to SCO compatibles and had just the same kind of problems
as you seem to have... 

  But expect a lot more fixes after having all the routines compiled
from the library... but perhaps BSD is better supported than SysV/i386
and there are not so many incompatible headers and routines....