Date: Mon, 08 Mar 2004 11:02:07 +1000 From: Mark Sergeant <msergeant@snsonline.net> To: JG <amd64list@jpgsworld.com> Cc: freebsd-amd64@freebsd.org Subject: RE: Best way to compile Mysql 4.1.x with Linuxthreads support on AMD64? Message-ID: <1078707727.1307.1.camel@localhost> In-Reply-To: <5.2.0.9.2.20040307162901.04125088@mail.ojoink.com> References: <5.2.0.9.2.20040307162901.04125088@mail.ojoink.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-BR5J2sFLUQDJz8KTJI1p Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Mon, 2004-03-08 at 10:32, JG wrote: > At 07:43 AM 3/7/2004 -0500, you wrote: > > >> I'm just not sure what the best way to compile it is. > > >> How do you compile Mysql on AMD64? > > > >Kris Kennaway: > > > cd /usr/ports/databases/mysql-server41-server; make > > > >As I recall, I just downloaded the current MySQL 4.1 sources from mysql.= com > >and built them. > > > >Running rock-solid for over a month in production use now: dual Opteron = 242 > >on a Tyan K8S Pro. >=20 > I may have to try that next, as the port is still semi-broken: >=20 >=20 > After installing mysql41-server from ports with SKIP_DNS_CHECK=3Dyes and = it=20 > won't start up... >=20 > My mysql log output: >=20 > 040307 15:22:33 mysqld started > 040307 15:22:34 InnoDB: Database was not shut down normally! > InnoDB: Starting crash recovery. > InnoDB: Reading tablespace information from the .ibd files... > InnoDB: Restoring possible half-written data pages from the doublewrite > InnoDB: buffer... > 040307 15:22:34 InnoDB: Starting log scan based on checkpoint at > InnoDB: log sequence number 0 43634. > InnoDB: Doing recovery: scanned up to log sequence number 0 43634 > 040307 15:22:34 InnoDB: Flushing modified pages from the buffer pool... > 040307 15:22:34 InnoDB: Started; log sequence number 0 43634 > 040307 15:22:34 Fatal error: Can't open privilege tables: Table=20 > 'mysql.host' doesn't exist > 040307 15:22:34 mysqld ended >=20 > I've looked on google a bit for this & it sounds like the system tables=20 > aren't being fully created or something. >=20 >=20 There is a known bug with mysql4.x, amd64 and innodb. If you can avoid using innodb then you shouldn't have any problems. > What a mess this is so far... but I'm very curious how this AMD64 Mysql=20 > box on FreeBSDwill stack up against > Linux - so I will continue on till I get it all working - and then report= =20 > the various benchmarks. >=20 >=20 >=20 > _______________________________________________ > freebsd-amd64@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-amd64 > To unsubscribe, send any mail to "freebsd-amd64-unsubscribe@freebsd.org" --=20 Mark Sergeant <msergeant@snsonline.net> SNSOnline Technical Services --=-BR5J2sFLUQDJz8KTJI1p Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAS8YPbS4ZEpHb8t0RArhlAJ9M6Ov2Zm4+8TOUqpQFofaaftIVRACaAtTw U7eH97o+r7K47/6mygjW+aA= =2Ble -----END PGP SIGNATURE----- --=-BR5J2sFLUQDJz8KTJI1p--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1078707727.1307.1.camel>