Re: [email@example.com: Excessive size of s390 vim binary]
When I refer to s390, I mean OS/390 or z/OS. My work environment is Unix
System Services on a IBM eServer zSeries mainframe. I am NOT working in
As I said before, strip(1) in OS/390 is equivalent to touch(1).
Sorry for the confusion.
Phone: (845) 435-9115
Tie Line: 295-9115
Rick Troth <firstname.lastname@example.org>
09/19/2001 01:53 PM
To: Wichert Akkerman <email@example.com>
cc: firstname.lastname@example.org, email@example.com, "Anthony
Subject: Re: [firstname.lastname@example.org: Excessive size of s390 vim binary]
> I just got this on the vim-dev list. If this is indeed so (strip does
> not work on s390) does that mean Debian policy forces us to have
> large unstripped binaries on s390?
I think there is a mix-up between z/OS (and OS/390) and Linux/390
in this discussion. 'strip' works just fine on Linux/390.
> standard Unix/Linux system this is fine, as one can strip(1) a binary to
> remove the debugging info. On an s390 system, strip is identical to
> touch(1), and cannot remove the symbols from the file.
'strip' on Linux/390 removes symbolics just like on any other UNIX.
The term "S/390" is vague: did you mean OS/390 or Linux/390?
'strip' on Linux/390 is NOT identical to 'touch'.
> | On some UNIX systems, strip removes debug information from an
> | On z/OS, the debug information can only be removed by recompiling.
> | does not modify the contents of any executable file--it is
> | equivalent to touch file.
Common problem, people forget that:
z/OS != Linux/zSeries
OS/390 != Linux/390
We are talking about two different 'strip' programs.
Rick Troth, BMC Software, Inc. <email@example.com>
2101 City West Blvd., Houston, Texas, USA, 77042 1-800-841-2031
* T H E B E S T L I T T L E S O F T W A R E H O U S E I N T E X A S