Good morning,
I am trying to build MySQL from source on Solaris 6. A pre-compiled
version is not available for Solaris 6 and we cannot upgrade the OS to
Solaris 8.
I currently have Ver 9,38 Ditrib 3.22.32 installed, but the main MySQL
Server (the one one Solaris is used as a client only) has
in England and Wales No 3027851 VAT Reg No 778499447
-Original Message-
From: mysql [mailto:[EMAIL PROTECTED]
Sent: 26 July 2007 13:24
To: Giulio Troccoli
Cc: mysql@lists.mysql.com
Subject: Re: Error compiling on Solaris 6
Giulio
did you take into consideration
Giulio
did you take into consideration that the Solaris make is not the GNU
make? and that you possibly have to install first the GNU make before
making MySQL?
suomi
Giulio Troccoli wrote:
Good morning,
I am trying to build MySQL from source on Solaris 6. A pre-compiled
version is not
I have tried multiple times to build a version of 3.23.55 with support for
innodb under Solaris 2.6. I can not upgrade the version of the OS.
Here is the error:
source='mysql.cc' object='mysql.o' libtool=no \
depfile='.deps/mysql.Po' tmpdepfile='.deps/mysql.TPo' \
depmode=gcc3 /bin/ksh
Description:
I'm trying to compile mysql on solaris 2.6. Getting these errors:
mysql.cc: In function `int sql_connect(char*, char*, char*, char*, unsigned
int)':
mysql.cc:2175: `sleep' undeclared (first use this function)
mysql.cc:2175: (Each undeclared identifier is reported only
Brad Teale writes:
A couple of questions about compiling on Solaris.
1) Are the Sun Workshop 6 compilers supported for MySQL and MySQL++?
1a) Can you use the -native flag without problems?
2) Is the binary distribution compiled with Sun or GNU compilers?
Background Info:
We
Brad Teale writes:
I found the answers to my previous question about MySQL in the manual. Doh!
However, when I tried to compile MySQL, I ran into the following error:
[skip]
processors
hash.c, line 189: reference to static variable hash_key in inline extern
function
hash.c, line 229:
A couple of questions about compiling on Solaris.
1) Are the Sun Workshop 6 compilers supported for MySQL and MySQL++?
1a) Can you use the -native flag without problems?
2) Is the binary distribution compiled with Sun or GNU compilers?
Background Info:
We are currently trying to ingest
I found the answers to my previous question about MySQL in the manual. Doh!
However, when I tried to compile MySQL, I ran into the following error:
/bin/sh ../libtool --mode=compile cc
-DDEFAULT_CHARSET_HOME=\/export/home/bteale/mysql-3.23.47\
-DDATADIR=\/export/home/bteale/mysql-3.23.47/var\
.
-Original Message-
From: Alan W. Rateliff, II [mailto:[EMAIL PROTECTED]]
Sent: 05 December 2001 15:15
To: Matthew Darcy
Subject: Re: Problems compiling under Solaris 2.6
On 05-Dec-01, Matthew Darcy said something totally profound about Problems
compiling under Solaris 2.6 that made me ponder
Hello,
when trying to compile mysql-3.23.37 on solaris 8, using either just
./configure or
CC=gcc CXX=gcc CXXFLAGS=-O3
./configure --prefix=/usr/local/mysql --with-low-memory --with-extra-charset
s=complex
I get the message:
checking return type of sprintf... configure: error: can not run
I'm having problems compiling mysql 3.23.37 on
Solaris 2.7. It gets to the final linking stage
and I get the following error:
/usr/local/lib/gcc-lib/sparc-sun-solaris2.7/2.95.1/libgcc.a: could not read symbols:
Bad value
Anyone have this happen to them before and/or
have a fix? I've also
Previously someone had mentioned that the issues covered by my FAQ (located at
http://users.talstar.com/forager/MySQL-HOWTO.html ) had been taken care of
with releases past 3.23.28. However, just tonight I found that the problem
with the broken Solaris term.h file still exists, and after
13 matches
Mail list logo
