home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!bonnie.concordia.ca!IRO.UMontreal.CA!CC.UMontreal.CA!duperval
- From: duperval@ERE.UMontreal.CA (Duperval Laurent)
- Newsgroups: comp.os.linux
- Subject: Re: Installing gcc
- Message-ID: <1992Sep11.050515.10419@cc.umontreal.ca>
- Date: 11 Sep 92 05:05:15 GMT
- References: <1992Sep5.052329.24698@cc.umontreal.ca> <bjl.715689694@freyr> <pgr.140851.05Sep1992@prg.ox.ac.uk>
- Sender: news@cc.umontreal.ca (Administration de Cnews)
- Organization: Universite de Montreal
- Lines: 32
-
- In article <pgr.140851.05Sep1992@prg.ox.ac.uk> pgr@prg.ox.ac.uk (Partially Grown Rhododendron) writes:
- >In <bjl.715689694@freyr>, B.J.Lippolt@research.ptt.nl writes:
- >> If you still use the minix fs, you can't have filenames > 14. But this is
- >> not a problem when installing GCC. The kernel automatically chops off
- >> all characters > 14. So even if your real filename is 2.2.2dmisc.tar
- >> and in the install script it is 2.2.2dmisc.tar.Z there should be no problem.
- >
-
- Well... I'm not going to talk about the install script because before I had
- time to realize what Ben mentioned, I hacked and chopped away, with great
- conviction (the script, that is). I successfully installed gcc so it's no big
- deal.
-
- The only reason the script works is because it uses zcat and/or tar -z????
- (I've no brains so I don't remewmber what the options are). Using uncompress
- with 2.2.2dmisc.tar.Z would generate 2.2.2dmisc.tar
-
- which causes a problem. I just tried uncompressing a file
- with 16 chars and I get a corrupt input error message.
-
- Therefore,
-
- >I think the simplest solution would be to make sure that the next release
- >of the files (2.2.2e, or whatever) keeps to under the 14 characters...
- >it would certainly have cut down the amount of noise, and would probably
- >have stopped some people's confusion...
- >
- --
- Laurent Duperval
- duperval@ere.umontreal.ca
- duperval@jsp.umontreal.ca
- If you gotta go, go happy... or surprised. -Me
-