Re: A proposal for Midnight Commander

[Ali Akcaagac <aliakc web de>]

On Fri, 2003-11-14 at 21:24, Rob Ristroph wrote:
> Are patches being rejected ? One way to get a new feature
> accepted would be to post the patch or whole source on the
> web, even if the maintainer didn't like it at first,
> widespread use of the changes might change minds.

I'm not the person writing patches which are supposed to be rejected
afterwards. I first make a proposal and if it's being agreed on then we
can talk about making patches. I am willing to write a couple of parts
to remove glib dependency.

> Your 4.1.40 is likely unstripped, because it doesn't strip the
> copy in the source tree (in fact make install doesn't strip it
> either). It is likely stripping will save you more space than
> glib. Also look at "ldd /tmp/s/mc-4.1.40-pre8/src/mc" and "ldd
> /usr/local/bin/mc". It is likely that you link in one or two
> unneeded libraries.

I don't know what you are using here but it's most likely NOT the
mc-4.1.40MP that I was refering to but to answer at least one question
it was stripped by me afterwards before I mentioned the values.

> libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x40024000)
> libncurses.so.5 => /lib/libncurses.so.5 (0x40048000)
> libext2fs.so.2 => /lib/libext2fs.so.2 (0x40088000)
> libcom_err.so.2 => /lib/libcom_err.so.2 (0x4009c000)
> libc.so.6 => /lib/libc.so.6 (0x4009e000)
> libgpm.so.1 => /lib/libgpm.so.1 (0x401c1000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)

Yeah only strange thing is, where did you get the glib dependency from ?
Midnight Commander 4.1.40 MP doesn't have any glib dependencies in it.
It doesn't link to it, it doesn't search for it and it doesn't require
it. So the only conclusion is you are ldd'ing a totally wrong binary
here.

http://mc.linuxinside.com/

> Ok, but consider which is easier -- dealing with the separate
> 4.1.40 tree, or just adding --without-x to your configure flags ?

I think you don't exactly know what you are writing here (no offense but
I don't know how else I can explain it). --without-x has nothing to do
with glib not staying a dependency inside mc.

Again, I'm not worried about the size (well not entirely true). It
doesn't really matter whether there are a few bytes difference (as long
as it's a few bytes). To say the truth mc-4.6.0 can be stripped down to
a 360376 bytes binary without any options enabled, compiled with -Os and
stripped, whereas the mc-4.1.40MP is around 536524 bytes binary without
any options, compiled with -Os and stripped. But the glib library is
around 500kb which makes the nice stripped 360376 bytes binary of
mc-4.6.0 look like a worthless value.