From owner-freebsd-questions Wed Feb 4 22:47:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21772 for questions-outgoing; Wed, 4 Feb 1998 22:47:28 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21765 for ; Wed, 4 Feb 1998 22:47:20 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id BAA26846 for ; Thu, 5 Feb 1998 01:47:18 -0500 (EST) Date: Thu, 5 Feb 1998 01:47:18 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: questions@FreeBSD.ORG Subject: MySQL 3.2.22-23 fails to compile Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" The two newest versions of MySQL fail to compile on 2.2-stable or 3.0. The following errors occur: >>> Making all in Docs >>> Making all in readline >>> Making all in client >>> c++ -O -g -O2 -fno-implicit-templates -DDBUG_OFF -o mysql mysql.o >>> readline.o sql_string.o completion_hash.o -L../readline -lreadline >>> -ltermcap -L. -lmysqlclient -lm -lcompat >>> rltty.c:399: Undefined symbol `___error' referenced from text segment >>> rltty.c:431: Undefined symbol `___error' referenced from text segment >>> rltty.c:433: Undefined symbol `___error' referenced from text segment >>> bind.c:615: Undefined symbol `___error' referenced from text segment >>> input.c:259: Undefined symbol `___error' referenced from text segment >>> input.c:421: Undefined symbol `___error' referenced from text segment >>> input.c:437: Undefined symbol `___error' referenced from text segment >>> input.c:455: Undefined symbol `___error' referenced from text segment >>> *** Error code 1 Other folks trying this running similar FBSD systems get the same result. Monty (the MySQL guy) got it to go on a 2.2.5-RELEASE box. Here's some of his comments: Has anyone a explanation for this? I have tested MySQL 3.21.22 and 3.21.23 on a 'FreeBSD 2.2.2-RELEASE i86pc' without any problems. The above is an link error that shouldn't be MySQL releated (There is no symbol __error in the MySQL source). Can you find from where this symbol orginates ? (Problably some header file in /usr/include). There is also a possibility that your gcc include files are wrong! (This is a common source of grief with gcc on Solaris) Check that the include files in the gcc-lib directory is from FreeBSD 2.2.2 and not from an earlier FreeBSD version! It's of possible that your c++ doesn't work properly! If your c++ is g++, then it may help if you use the above configure line. The difference between using gcc and g++ in compiling C++ code is that gcc doesn't depend on the libstdc++ library. Start talking about symbols, linkers, and g++ problems, and I'm lost. Does anyone have any ideas? Is there anyone that would like to partner up with Monty to help out with future releases? He seems to develop primarily for Linux and Solaris, so the FBSD version usually lags a bit. Thanks, Charles Sprickman spork@super-g.com ----