1 Sep 2004 01:18
1 Sep 2004 04:14
problem running "make"
Eagle Net Support <support <at> eagle-access.net>
2004-09-01 02:14:41 GMT
2004-09-01 02:14:41 GMT
Hi, first time user. running Red Hat 9.0 I ran ./configure --with-include-gettext --enable-RPA --enable-NTLM no errors displayed on make I get [root <at> saturn fetchmail-6.2.5]# make expect conflicts: 2 shift/reduce yacc -d ./rcfile_y.y make: yacc: Command not found make: *** [rcfile_y.c] Error 127 I don't see or couldn't find anything in docs alluding to this error Can anybody help debug an install? joe eaglenet -- -- This message has been scanned for viruses and dangerous content, and is believed to be clean.
1 Sep 2004 08:08
Re: problem running "make"
Rob MacGregor <rob.macgregor <at> gmail.com>
2004-09-01 06:08:21 GMT
2004-09-01 06:08:21 GMT
On Tue, 31 Aug 2004 20:14:41 -0600, Eagle Net Support <support <at> eagle-access.net> wrote: > > I ran > > ./configure --with-include-gettext --enable-RPA --enable-NTLM > > no errors displayed > > on make I get > > [root <at> saturn fetchmail-6.2.5]# make > expect conflicts: 2 shift/reduce > yacc -d ./rcfile_y.y > make: yacc: Command not found > make: *** [rcfile_y.c] Error 127 > > I don't see or couldn't find anything in docs alluding to this error Hmmmm. "yacc: Command not found" seems pretty obvious to me. Install yacc! -- -- Rob MacGregor Whoever fights monsters should see to it that in the process he doesn't become a monster. Friedrich Nietzsche
1 Sep 2004 10:33
Re: problem running "make"
Eagle Net Support <support <at> eagle-access.net>
2004-09-01 08:33:04 GMT
2004-09-01 08:33:04 GMT
Rob MacGregor wrote: > On Tue, 31 Aug 2004 20:14:41 -0600, Eagle Net Support > <support <at> eagle-access.net> wrote: > > > > I ran > > > > ./configure --with-include-gettext --enable-RPA --enable-NTLM > > > > no errors displayed > > > > on make I get > > > > [root <at> saturn fetchmail-6.2.5]# make > > expect conflicts: 2 shift/reduce > > yacc -d ./rcfile_y.y > > make: yacc: Command not found > > make: *** [rcfile_y.c] Error 127 > > > > I don't see or couldn't find anything in docs alluding to this error > > Hmmmm. "yacc: Command not found" seems pretty obvious to me. > > Install yacc! > yacc was already installed locate shows it in /usr/local/bin/yacc reinstalled it anyway from bison. exact same error I don't know, where does "make" get the path to yacc as one idea. joe eaglenet > > -- > Rob MacGregor > > Whoever fights monsters should see to it that in the process he > doesn't become a monster. > Friedrich Nietzsche > > _______________________________________________ > Fetchmail-friends mailing list > Fetchmail-friends <at> lists.ccil.org > http://lists.ccil.org/cgi-bin/mailman/listinfo/fetchmail-friends > > -- > This message has been scanned for viruses and > dangerous content, and is believed to be clean. -- -- This message has been scanned for viruses and dangerous content, and is believed to be clean.
2 Sep 2004 04:24
Re: problem running "make"
Rob Funk <rfunk <at> funknet.net>
2004-09-02 02:24:11 GMT
2004-09-02 02:24:11 GMT
Eagle Net Support wrote: > yacc was already installed > locate shows it in /usr/local/bin/yacc > > reinstalled it anyway from bison. exact same error > > I don't know, where does "make" get the path to yacc as one idea. make gets its information from configure. Try removing config.cache and running ./configure again. Make sure /usr/local/bin is in your PATH when you do. Any chance you copied the directory from another machine where you'd compiled fetchmail before? -- -- ==============================| "A slice of life isn't the whole cake Rob Funk <rfunk <at> funknet.net> | One tooth will never make a full grin" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind"
2 Sep 2004 09:53
Re: problem running "make"
Eagle Net Support <support <at> eagle-access.net>
2004-09-02 07:53:50 GMT
2004-09-02 07:53:50 GMT
Rob Funk wrote: > Eagle Net Support wrote: > > yacc was already installed > > locate shows it in /usr/local/bin/yacc > > > > reinstalled it anyway from bison. exact same error > > > > I don't know, where does "make" get the path to yacc as one idea. > > make gets its information from configure. couldn't find a PATH entry to add /usr/local/bin in configure. checked files that looked possible like configure.in and a few others. I suspect a PATH entry somewhere is needed as when I view config.log I see a PATH statement list ***************paste in from log PATH: /usr/kerberos/sbin PATH: /usr/kerberos/bin PATH: /sbin PATH: /usr/sbin PATH: /usr/bin PATH: /bin PATH: /etc PATH: /usr/local PATH: /usr/X11R6/bin PATH: /home/support/bin **************************** and /usr/local/bin is not logged > > > Try removing config.cache no file "config.cache" This might be config.status. I did a make distclean in between runs of ./configure which seemed to be dumping any file configure created. > and running ./configure again. Make > sure /usr/local/bin is in your PATH when you do. > > Any chance you copied the directory from another machine where you'd > compiled fetchmail before? Not positive but I don't think so. no fetchmail files found on locate. Why what are you thinking? If I could locate the PATH entry I think this would be solved. joe eaglenet > > > -- > ==============================| "A slice of life isn't the whole cake > Rob Funk <rfunk <at> funknet.net> | One tooth will never make a full grin" > http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind" > > _______________________________________________ > Fetchmail-friends mailing list > Fetchmail-friends <at> lists.ccil.org > http://lists.ccil.org/cgi-bin/mailman/listinfo/fetchmail-friends > > -- > This message has been scanned for viruses and > dangerous content, and is believed to be clean. -- -- This message has been scanned for viruses and dangerous content, and is believed to be clean.
3 Sep 2004 00:38
Re: problem running "make"
Rob Funk <rfunk <at> funknet.net>
2004-09-02 22:38:23 GMT
2004-09-02 22:38:23 GMT
Eagle Net Support wrote: > couldn't find a PATH entry to add /usr/local/bin in configure. PATH is a Unix environment variable. See: http://wks.uts.ohio-state.edu/unix_course/intro-59.html Your PATH is normally set in a startup file in your home directory, such as .profile, .bash_profile, .bashrc, or .cshrc. The easiest thing to do as a quick fix just to get the compile to work would probably be this: PATH=$PATH:/usr/local/bin export PATH > > Try removing config.cache > > no file "config.cache" This might be config.status. I did a make > distclean in between runs of ./configure which seemed to be dumping > any file configure created. OK, as long as you're getting a new configuration that's fine. > > Any chance you copied the directory from another machine where you'd > > compiled fetchmail before? > > Not positive but I don't think so. no fetchmail files found on locate. > Why what are you thinking? I'm surprised you were even able to get a Makefile out of configure if it couldn't find yacc (or bison). One explanation would be that the Makefile was leftover from a previous run on a different machine. -- -- ==============================| "A microscope locked in on one point Rob Funk <rfunk <at> funknet.net> |Never sees what kind of room that it's in" http://www.funknet.net/rfunk | -- Chris Mars, "Stuck in Rewind"
RSS Feed