[Syllable-kernel] Glibc 2.3.3 source now up

[Kristian V. <kri...@xe...>]

I've uploaded the source for Glibc 2.3.3 to match the binaries
I released last Friday.  Get it from
http://www.liqwyd.com/glibc/glibc-2.3.3-beta1.src.tar.gz  You'll
also need the latest CVS headers for Syllable and
http://www.liqwyd.com/glibc/includes-011104.tgz

How to build it:

o Install Gcc 3.x, Binutils 2.15 and Gawk 3.x
o Untar the source; this will create a directory called "libc"
o Alongside this directory create two more empty directories;
  libc-build and libc-config
o cd into libc-config and run:

  $ ../libc/configure --prefix=/path/to/libc-build
    --enable-hacker-mode

o Once configure has completed:

  $ make

o The build will fail at the point where make will complain that it
  doesn't know how to build "syscall-stubs.o"  I don't know what
  causes this; just run make again and it'll carry on.

o It should build all the way through without a problem, but I
  have noticed that AFS seems to have some problems under very high
  loads E.g. when building Glibc.  Occasionally some files may
  appear to be corrupt and the build will stop.  The copy I built
  this morning is always stopping at libcrypt and complaing about
  undefined symbols, but I know the same source built fine
  previously. let me know if you have any *persistent* problems
  like this.

o Eventually make should exit successfully.  Now run:

  $ make install

  This will place all the files in the libc-build directory.

I'd advise that you install the Glibc 2.3.3 binaries I released on
Friday using the install.sh script and then simply copy the new
libc-2.3.3.so file into /system/libs to overwrite the existing file.
Don't simply copy all of the DSO's that Glibc builds into /system/libs
because you *WILL* break your system.  If you did that, re-install.
Note that if you make changes and copy the new library into place
the old library may be cached so you'll have to reboot to get the
new library to be used.

The API SHOULD be complete; that is, all of the Syllable specific
functions and syscalls should be available and should work as
expected.  The exception to this are stricmp() and strnicmp(); Kurt
added these but I have left them out.  If they're required I'll
implement them.  Let me know if you get any undefined symbols or
unexpected behavour.

C++ isn't working due to some header clashes.  I still need to
solve this one.

I recommend at least 256Mb of memory and 250Mb of disk space,
running sync as often as you can to insure against a crash.  My
development box here is a puny P3 450 and it takes about 2 hours to
do a full build there.  I wouldn't dream of trying on anything
slower!

Be aware that the tarball posted is a CVS working copy with
changes; you can run "cvs update" to pull down the latest changes
in the Glibc CVS server but this MAY cause the build to break.
Breakage is not usually serious but even I've been left
scratching my head at some of them in the past so be warned;
changes can be obscure.

-- 
Vanders
http://www.syllable.org
http://www.liqwyd.com

_____________________________________________________________________
This message has been checked for all known viruses by Xenicom delivered through the MessageLabs Virus Control Centre.