OpenCores
URL https://opencores.org/ocsvn/or1k/or1k/trunk

Subversion Repositories or1k

[/] [or1k/] [trunk/] [linux/] [glibc/] [README.or32] - Rev 1765

Compare with Previous | Blame | View Log


This port of Glibc is unfinished and in highly inmature stage!

It is based on many assembly sources from the or32 port of uClibc.


Build instructions
~~~~~~~~~~~~~~~~~~

In order to build, you need to overlay this sysdeps directory onto a fresh
glibc-2.3.1 tree.  After that, apply the patches.

You need a gcc-3.4 cross-compiler built without thread support.  It must be
patched not to prepend symbol names with an underscore (this is to avoid
conflict with hardcoded symbols in libgcc).

As for Glibc build parameters (asides from the obvious).

CFLAGS="-g -O1 -fno-cprop-registers -fno-unit-at-a-time -finline-functions"

--disable-sanity-checks (allow us to build without thread support)
--disable-profile
--disable-shared        (shared library support is filled with dummy code.
                        better not use it)

Status
~~~~~~

It builds and you can link static binaries with it, but the initialisation
routines contain bugs that cause SIGSEVs (this was found in places like
getenv() and malloc()).

No thread support.  No shared library support.

A number of files (both in sysdeps and in the patches) contain dirty hacks
(some are very dirty, see for yourself).  I tried to keep record of these with
"FIXME" tags.  A number of these hacks are derived from the fact that we don't
have thread support or shared library support and will probably disappear when
we do.

Only 2.3.1 is supported.  It can't be updated to more recent versions of Glibc
untill we have recent binutils in a working state.

Copyright status
~~~~~~~~~~~~~~~~

Before you add copyright-significant amount of code (around 15 unredundant
lines) to this port, please note that due to FSF policy your contribution can't
be merged in official Glibc unless you do the paperwork to assign copyright to
them.

As of importing the port, it only contains work copyrighted by me
(Robert Millan  <robertmh@opencores.org>) and the person who ported uClibc.  My
paperwork wrt Glibc is done.  If you know who wrote the uClibc port, please let
me know so I can contact him/her.

Compare with Previous | Blame | View Log

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.