This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: crossgcc building problem


miki.shapiro@eAladdin.com wrote:
> 
> I'm now attempting to compile either newlib-1.9.0 or glibc-1.09.1
> 
> For now, I opted for newlib, doing this:
> a. added the /.../cross-compiler-dir/bin to my tcsh path
> b. configured as follows:
> 
> 13:51|[May] mikisu:/usr/src/cross2/newlib-1.9.0/build#../configure
> --target=sparc-sun-solaris2.7 --prefix=/usr/local/cpl/sparc-sun-solaris2.7

 Neither glibc-1.09.1 or newlib is ported to Solaris2 very well or at all...
Some support for SunOS 4 seems to exist in newlib, but the 'newlib/libc/sys/sparc64'
seems to be for the ESA 'erc32' or some other embedded system...

 The Sun's own Solaris2.7 headers and libraries are easily available, Sun sent the
Solaris2.7 installation media as free for all home users, students, testers etc.
So the obvious question is why you want to try the glibc-1.09.1 or newlib ports?
There will be man-months to do before glibc-1.09.1 or newlib will be even near the
Sun's own basic C-library... Then there are all the extra termcap, curses, network,
X11 etc. libs to port...

 Once I bettered the SCO 3.2 / SVR3.2/i386 support in glibc-1.09.1 and newlib, because
the SCO's own DevSys costed $1000 or so, and the headers and libs from it were needed
for the "free GCC" (ie. getting GCC to work costed the $1000...) and for simple compiles.
But why Sparc/Solaris2.7 ?

Cheers, Kai



------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]