Coda File System

Re: coda 6.0.2 compile failure

From: Jan Harkes <jaharkes_at_cs.cmu.edu>
Date: Tue, 7 Oct 2003 16:10:39 -0400
On Tue, Oct 07, 2003 at 11:27:23AM -0700, Eric Sandall wrote:
> Quoting Jan Harkes <jaharkes_at_cs.cmu.edu>:
> > On Tue, Oct 07, 2003 at 10:00:57AM -0700, Eric Sandall wrote:
> > > When compiling coda 6.0.2 I receive the following error:
> > > 
> > > g++ -fno-exceptions -fcheck-new -x c++ -Wall -MD -DHAVE_CONFIG_H -I.
> > > -I/usr/src/coda-6.0.2/include -I/usr/src/coda-6.0.2 -march=athlon-mp -mmmx
> > > -mfpmath=sse -msse -m3dnow  -c resolver_parser.c
> > > y.tab.c: In function `int yyparse()':
> > > y.tab.c:1331: error: parse error before `goto'
> > > y.tab.c:1322: warning: label `yyerrlab1' defined but not used
> > > make[3]: *** [resolver_parser.o] Error 1
> > > make[3]: Leaving directory `/usr/src/coda-6.0.2/coda-src/asr'
> > 
> > Broken bison release (or gcc-overoptimization), you need to upgrade to
> > the fixed version (1.875a?) or edit the template code in
> > /usr/share/bison/yacc.c.
> 
> We don't have 1.875a as the GNU FTP server was hacked and they haven't
> put this file up, but 1.875 is available.  Will update the package
> when it's available.

http://packages.debian.org/unstable/devel/bison.html

There is a link to the pristine source tarball at the bottom of the
page.

> > > I then receive this error:
> > > 
> > > gcc -fno-exceptions -Wall -MD -DHAVE_CONFIG_H -I.
> > -I/usr/src/coda-6.0.2/...
> > > ../util/libutil.a(getsecret.o)(.text+0x10): In function `HashSecret':
> > > : undefined reference to `MD5_Init'
> > 
> > This depends on whether you have the openssl development headers
> > installed. If openssl-dev exists it should try to use their
> > implementation, otherwise it should use the 'reference C implementation'
> > which is built and included in lib-src/base/libbase.a.
> 
> I just used ./configure && make server-install to get this error, so configure
> isn't detecting properly.  I have openssl installed (from source) and other
> packages link with it just fine.

Ok, when not explicitly enabled, we don't link against the openssl
library and it should have compiled md5c.o in lib-src/base.

Could you send me the output of the configure run and the config.status
file. Oh, and the version of autoconf that you're using.

Jan
Received on 2003-10-07 16:12:42