🚀 go-pugleaf

In article <13794@sdcc6.ucsd.edu> jclark@sdcc6.ucsd.edu (John Clark) writes:
>How does one handle the problem of the gnulib and the gnulib2 stuff.
gnulib2 schould be compiled by gcc anyway.

gnulib is a bit more involved. Gcc uses gnulib to get hold of a systems 
floating point library, multiplication and division functions (if none 
are available in the processor, etc.). Some functions you probably could 
compile with gcc also. Others, you will have to re-code. An example
(from memory, may diverge from "real" gnulib):
On a processor without SF mode multiply, the gnu cc will call
mulsf instead. Mulsf is defined thus:

(typedefs for SFmode ... )
SFmode mulsf (a, b)
SFmode a,b;
{
	return a*b;
}

... so you simply get the systems multiplication function. If there isn't any,
you must code this function yourself ...

Maybe someone can get hold of a PD IEEE-emulation library which could
be distributed with gcc, to make cross-compiling easier.

			bye,
				mike
Michael K. Gschwind, Institute for VLSI-Design, Vienna University of Technology
mike@vlsivie.tuwien.ac.at       1-2-3-4 kick the lawsuits out the door
mike@vlsivie.uucp               5-6-7-8 innovate don't litigate
e182202@awituw01.bitnet         9-A-B-C interfaces should be free
Voice: (++43).1.58801 8144      D-E-F-O look and feel has got to go!
Fax:   (++43).1.569697

>The gnulib stuff is compiled by "OLDCC" and the comment says 'OLDCC
>can't be gcc'. This seems to be a chicken and egg problem for the
>Cross compilation since if one had a pre-existing cc for the target
>one would not need gcc.
>
>-- 
>
>John Clark
>jclark@ucsd.edu