Article View: gnu.gcc.bug
Article #1855problem with fixincludes in 1.30
From: "Karl Berry."
Date: Thu, 20 Oct 1988 17:28
Date: Thu, 20 Oct 1988 17:28
16 lines
938 bytes
938 bytes
This is on a Sun 3 running 3.4. The `find' that is done at the top of fixincludes on /usr/include found the directories as well as the plain files. I changed the line to be files=`find . -type f -print` and it no longer had that problem. (But if the -print came first, it did.) Also, I had a problem with the GNU egrep returning status zero even if no matches were found. fixincludes relies on the status being nonzero if no matches were found, as the system grep behaves. This bug is fixed in GNU grep 1.1, the latest release. Karl. karl@umb.edu
Technical Details
Message-ID:
<8810201954.AA04503@prep.ai.mit.edu>Path:
arc1-ca.pugleaf.net!utzoo!telly!ddsw1!mcdchg!rutgers!mailrus!tut.cis.ohio-state.edu!umb.edu!karlShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!telly!ddsw1!mcdchg!rutgers!mailrus!tut.cis.ohio-state.edu!umb.edu!karl
From: karl@umb.edu ("Karl Berry.")
Newsgroups: gnu.gcc.bug
Subject: problem with fixincludes in 1.30
Message-ID: <8810201954.AA04503@prep.ai.mit.edu>
Date: 20 Oct 88 17:28:16 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 16