Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199911182207.QAA18480@mercury.xraylith.wisc.edu> To: Steve Jorgensen cc: Mumit Khan , cygwin AT sourceware DOT cygnus DOT com Subject: Re: gcc/g77/gcj 2.95.2 for cygwin CD 1.0? In-Reply-To: Your message of "Thu, 18 Nov 1999 14:46:09 MST." <199911182146 DOT OAA18424 AT benson> Date: Thu, 18 Nov 1999 16:07:04 -0600 From: Mumit Khan Steve Jorgensen writes: > > Ok, I've got everything required, and followed the directions > below, and very shortly into the build (running make), I get the > following error.. > > make[1]: Entering directory `/tmp/gcc-2.95.2-build/gcc' > cd /usr/local/src/gcc/src/gcc-2.95.2/gcc && autoheader > autoheader: not found > make[1]: *** [/usr/local/src/gcc/src/gcc-2.95.2/gcc/cstamp-h.in] Error 127 > make[1]: Leaving directory `/tmp/gcc-2.95.2-build/gcc' > make: *** [all-gcc] Error 2 > > I've looked everwhere I can think of, and haven't been able to find > autoheader.. Am I missing something? The problem is that when you patch your sources, the timestamps get messed up and the build process tries to remake the auto-generated files again even if there's no need. It's too tedious to make a diff/patch file that maintains the right order so that autogenerated files are patched *after* the ones they depend on. Of course, you can just get autoconf and automake packages from ftp://sourceware.cygnus.com/pub/ or ftp://ftp.gnu.org/pub/gnu/ and let it regenerate these files again. Or, I can just upload the whole gcc-2.95.2 source tree already patched that you can download and use that instead. Would that work better? Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com