Bug #72 big5.xml not found when compiling with --with-charset=big5
Submitted: 14 Feb 2003 2:27 Modified: 28 May 2003 6:26
Reporter: Lenz Grimmer Email Updates:
Status: Closed Impact on me:
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1 OS:Linux (Linux)
Assigned to: Alexander Barkov CPU Architecture:Any

[14 Feb 2003 2:27] Lenz Grimmer
From: Ian Li <ianlius@yahoo.com> 
To: mysql@lists.mysql.com 
Subject: Character set issue in 4.1 
  I am trying out mysql-4.1. 
I got the source code; 
configured it using --with-sharset=big5; 
successfully build it and got it installed. 
However, the following error occurrs, 
while mysqld is starting up. 
/usr/local/libexec/mysqld start 
/usr/local/libexec/mysqld: File 
'/usr/local/share/mysql/charsets/big5.xml' not found 
(Errcode: 2) 
/usr/local/libexec/mysqld: Character set 'big5' is not 
a compiled character set and is not specified in the 
'/usr/local/share/mysql/charsets/Index.xml' file 
030203 22:26:56  Aborting 
030203 22:26:56  /usr/local/libexec/mysqld: Shutdown 
Appreciate if anyone could shed some light on this. 
(My system is Red 8.0. ) 
-- ian 

How to repeat:
[15 May 2003 5:05] Alexander Barkov
I fixed so --with-charset=big5 is working now.
What to do with other charset/collations? We still don't have
an arrangement. Should I add all ~75 collations into configure.in?
Should --with-charset= accept collations too, so one is able to write both:

Or should be another argument for collation:
  --with-charset=latin1 --with-collation=latin1_danish_ci

If we want separate switches, how should we check in configure if
the collation is valid for the character set?
[28 May 2003 6:26] Alexander Barkov
Thank you for your bug report. This issue has already been fixed
in the latest released version of that product, which you can download at 

Ok. This is now fixed. ./configure --with-charset is up-to-date now.
[9 Jun 2003 22:08] [ name withheld ]
I am having the same problem while compiling with-charset=gb2312 in 4.1-Alpha in RedHat 8.0.

I downloaded the tarball after May 28th and the problem with gb2312 remains. Please check if the fix for big5 works on gb2312.

Thank you.

[10 Jun 2003 2:53] Alexander Keremidarski
What Alexander Barkov means is that it is fixed in source tree and fix will be included in next release - 4.1.1

4.1.0 is released before May 28th and we never change files on download area. We only add new ones with different release number.

If you want to see changes between releases download MySQL from BitKeeper trees as described at http://www.mysql.com/doc/en/Installing_source_tree.html