home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!swrinde!mips!darwin.sura.net!Sirius.dfn.de!Urmel.Informatik.RWTH-Aachen.DE!messua!dirkst
- From: dirkst@messua.informatik.rwth-aachen.de (Dirk Steinberg)
- Newsgroups: comp.os.linux
- Subject: Re: find 3.7 and fileutils 3.3 uploaded
- Message-ID: <dirkst.712335866@messua>
- Date: 28 Jul 92 15:04:26 GMT
- References: <14177@borg.cs.unc.edu> <dirkst.712334151@messua>
- Sender: news@Urmel.Informatik.RWTH-Aachen.DE (Newsfiles Owner)
- Organization: Rechnerbetrieb Informatik / RWTH Aachen
- Lines: 34
- Nntp-Posting-Host: messua
-
- faith@cs.unc.edu (Rik Faith) writes:
-
- >Here is a synopsis of my new uploads, as of Mon Jul 27 10:50:50 1992
-
- >Bug reports and comments to: faith@cs.unc.edu
-
- >*bin.tar.Z: linked static with gcc 2.2.2 (release version) under 0.96c.pl2
- ^^^^^^
- I think it is a bad practice to upload static binaries. They are totally
- useless for anyone who does not want to waste massive amounts of disk space.
- I have both Linux 0.96cpl2 and 386BSD 0.1 installed on my 486 and I prefer
- to use LINUX because it is more efficient and faster and it has shared
- libraries (and because gdb-4.6 and X386-1.2E work). The shared libraries
- are the single most biggest plus in favor of Linux, especially when it comes
- to X.
-
- We should always use the latest official gcc release shared images for
- uploading binaries. Starting from next release, these will be based on
- jump-tables anyway. If you really want, you can include /lib/libc.2.2.2
- in your tar file; for larger programs, this will get you to about the same
- total size.
-
- Alternatively, you could upload *.a's, but that requires the user to have
- gcc installed.
-
- >--
- >Rik Faith: faith@cs.unc.edu
-
- Dirk
- --
- ---
- Dirk W. Steinberg
- Aachen University of Technology
- email: dirkst@pool.informatik.rwth-aachen.de
-