resolving dependencies...
looking for inter-conflicts...

Targets (10): apr-1.4.2-1  unixodbc-2.3.0-1  apr-util-1.3.10-2  apache-2.2.17-1  libxml2-2.7.8-1  php-5.3.6-1  php-apache-5.3.6-1  libmysqlclient-5.5.10-2  mysql-clients-5.5.10-2  mysql-5.5.10-2

Total Download Size:    17.93 MB
Total Installed Size:   151.54 MB

:: Retrieving packages from extra...
downloading apr-1.4.2-1-x86_64.pkg.tar.xz...
downloading unixodbc-2.3.0-1-x86_64.pkg.tar.xz...
downloading apr-util-1.3.10-2-x86_64.pkg.tar.xz...
downloading apache-2.2.17-1-x86_64.pkg.tar.xz...
downloading libxml2-2.7.8-1-x86_64.pkg.tar.xz...
downloading php-5.3.6-1-x86_64.pkg.tar.xz...
downloading php-apache-5.3.6-1-x86_64.pkg.tar.xz...
downloading libmysqlclient-5.5.10-2-x86_64.pkg.tar.xz...
downloading mysql-clients-5.5.10-2-x86_64.pkg.tar.xz...
downloading mysql-5.5.10-2-x86_64.pkg.tar.xz...
checking package integrity...
checking for file conflicts...
installing apr...
installing unixodbc...
installing apr-util...
installing apache...
Optional dependencies for apache
    lynx: apachectl status
installing libxml2...
installing php...
installing php-apache...
installing libmysqlclient...
installing mysql-clients...
installing mysql...
Installing MySQL system tables...
110404 20:08:30 - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help diagnose
the problem, but since we have already crashed, something is definitely wrong
and this may fail.

key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=151
thread_count=1
connection_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 134068 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x13a6e30
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
usr/bin/mysql_install_db: line 428:  1700 Done                    { echo "use mysql;"; cat $create_system_tables $fill_system_tables; }
      1701                       | eval "$filter_cmd_line"
      1702 Segmentation fault      | $mysqld_install_cmd_line > /dev/null

Installation of system tables failed!  Examine the logs in
/var/lib/mysql for more information.

You can try to start the mysqld daemon with:

    shell> /usr/bin/mysqld --skip-grant &

and use the command line tool /usr/bin/mysql
to connect to the mysql database and look at the grant tables:

    shell> /usr/bin/mysql -u root mysql
    mysql> show tables

Try 'mysqld --help' if you have problems with paths.  Using --log
gives you a log in /var/lib/mysql that may be helpful.

Please consult the MySQL manual section
'Problems running mysql_install_db', and the manual section that
describes problems on your OS.  Another information source are the
MySQL email archives available at http://lists.mysql.com/.

Please check all of the above before mailing us!  And remember, if
you do mail us, you MUST use the /usr/scripts/mysqlbug script!

Optional dependencies for mysql
    perl-dbi
    perl-dbd-mysql