Skip to Content.
Sympa Menu

baslinux - Re: [BL] /lib/cpp error compiling in BL2 with libc-2.2.5 upgrade

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: sindi keesan <keesan AT sdf.lonestar.org>
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] /lib/cpp error compiling in BL2 with libc-2.2.5 upgrade
  • Date: Thu, 12 Jan 2006 20:37:05 +0000 (UTC)

On Wed, 11 Jan 2006, David Moberg wrote:

sindi keesan wrote:
On Tue, 10 Jan 2006, David Moberg wrote:

I will probably try to compile a new static MPlayer sometime.

with svgalib support?

OK. But because it is statically compiled, you will need to use
the svgalib that I compile in. I will use SW81 svgalib - would
that work well?

If it is statically compiled, shouldn't ANY svgalib work?
Will we still need libvga.config?

You could have put seejpeg instead of zgv on the USB boot disk, since that
is the most common camera format, to leave space for other things.

seejpeg does not work with chipset VGA. Or at least it would not
when I last tried it.

I wonder why. I will try that some time.


There are many other packages - I am currently looking
through their list to see if there is anything that I want to
try while I have glibc-2.3 installed.

This implies that you have some way of uninstalling it.

mke2fs /dev/hda4

I would prefer something less drastic. I wonder if I could simply uninstall SW91 glibc, then copy over the SW81 2.2.5 solibs files from another computer, then delete the SW91 files, and ldconfig.


I have nothing important on that partition, so I can just
wipe it off the map and start over when I am done with
this glibc experiment.

I could not even reinstall glibc-2.2.5.

You may need to boot ramdisk BL2 and use that to
remove glibc-2.3.2, and then reinstall the links to
glibc-2.1. e.g.

ln -s libc-2.1.3.so libc.so.6
ln -s libm-2.1.3.so libm.so.6
ln -s ld-2.1.3.so ld-linux.so.2

Does ldconfig do that automatically?

I was thinking of compiling my own shared lynx 2.8.6dev16 but the final
release should be out eventually, as it has been two years since
2.8.5rel1. Should I compile against 2.2.5 so more BL users can use it?

You could try compiling it with 2.1 so that it would work with
BL2 and no libc upgrade. Or perhaps you want to try the
uClibc development system? You can get it at uclibc.org.
Do you want to help me when I run into problems with it?

The resulting binary would be smaller than static glibc, and
not have the broken networking bug (I think it is only in certain
glibc versions), and work on BL3/1. You could then keep
the uClibc build system around for the next time that you need
a static binary.

Can you explain more about that bug? Lynx worked with 2.2.5 glibcso, I think also with 2.1.3, not online with 2.3.2 when I compiled statically, but it works fine with 2.3.2 in someone's shared version. Is it the static glibc.a that is the problem, and only works with a matching glibcso on the computer?


David

David
_______________________________________________
BasLinux mailing list
BasLinux AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/baslinux


keesan AT sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org




Archive powered by MHonArc 2.6.24.

Top of Page