Hi, I've built a glibc2 test suite as well. But that's not really related to the gnome issue, as I compiled gnome with very few problems without using glibc to do it. You don't really need it to build gnome. I _did_ find that mico wouldn't compile for me unless I used egcs, which I also have on board, as an option for cases like this ( read the docs ). ( still have gcc-2.7+ btw. Eggs is a fallback and no substitute for the compiler that comes with S.u.S.E. esp for kernels, but I'm sure you know this.) If you do intend to build gnome, make sure you read the docs, and scan the gnome archives to see problems that recur cause you WILL have problems. It's not a smooth build. Some Makefiles, potfiles, etc will need tooling, etc etc. And there are mistakes, in some of the packages. I know they put out another one a few days ago ( 27?) but it's IMHO an even bigger pain in the ass than the one before it.:-) I also recommend that when you build snaps for developmental software like Gnome you put it in a little 'test' pocket. That is, make a Gnome directory for compiling test snapshots, so it's contained and you don't have stuff all over your system, this way if you compiled it and hate it you can 'rm -rf $GNOME_DIRECTORY'and be done with it. All you have to do is make a Gnome directory and install EVERYTHING there included libraries and include files and then run 'autogen.sh' with --prefix <test directory> option and you have a nice little contained package. You can run things from the command line by just adding it's bin directory to your .profile. To me this is the safest way, and the way I use to install stuff like this so that I can get rid of it easily when I compile new snapshots, or just want to free up the disk space once I've seen what I need to see. I also add the gnome directory to profile with something like'GNOME=/opt/BUILD/gnome; export GNOME', so I can get there fast and save typing on configure. If you do things this way, you'll of course want to make sure you add the libraries to ld.so.conf. As far as how it RUNS after you build it, for _me_ it runs o.k. But there are some real bugs, so don't expect it to run perfectly even if you do decide to build it. And don't get mad when some things ( applets/panel errors are getting alot of notoriety) don't work quite as you had hoped. It's still in development. Good Luck. <g> Michael On Sun, 16 Aug 1998, Mark Wagnon wrote:

Hi all-

I just spent the last four hours downloading the sources and compiling glibc2. I followed the Glibc2-HOWTO to the letter, and if the "hello world" test program in the howto is a litmus test, I now have glibc2 installed on my system as a test library.

My primary goal was to get glibc2 installed so that I could compile gnome from the sources. I realize that SuSE 5.3 will ship with glibc (binary?) support, but I wanted to do things myself. Has anyone else done this? Anyone running gnome on their SuSE system? I'm going to head on over to the gnome site to see what I need to download. If anyone has any pointers. I'd be grateful.

Thanks,

Mark (with nothing better to do on a Saturday night) - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e

-M One is most dishonest towards one's God; he is not _permitted_ to sin. mail: mjohnson@pop3.aebc.com - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e