Re: [Ltib] MySQL Upgrade

[Rajaram Ghosh]

Hi Stuart,
Thanks for Your Guidance, I did Some Work over the Weekend to Upgrade to
MySQL-5.1.61 (the MySQL-5.5 Seems to Use cmake instead of autotools, Need to
Work Further), Please Review the MySQL-5.1.61 Work, I will Need Feedback. 

Here's What I have Done

1) Downloaded the 'mysql-5.1.61.tar.gz' Tarball from
http://dev.mysql.com/get/Downloads/MySQL-5.1/mysql-5.1.61.tar.gz/from/http:/
/mysql.borsen.dk/ 

2) Placed the MySQL-5.1.61 Source Tarball in /opt/freescale/pkgs

3) Edited the dist/lfs-5.1/mysql/mysql.spec File

3) Unpacked the Source with 

$ ./ltib -m prep -p mysql

4) Modified/Added the Following Files in rpm/BUILD/mysql-5.1.61 based on the
OpenWrt Patch for MySQL-5.1.53
(https://dev.openwrt.org/browser/packages/libs/mysql/patches/500-cross_compi
le.patch, and
https://dev.openwrt.org/browser/packages/libs/mysql/patches/501-disable-pthr
ead-and-tests.patch)

mysql-5.1.61/configure
mysql-5.1.61/extra/Makefile.am
mysql-5.1.61/extra/Makefile.in
mysql-5.1.61/libmysql/Makefile.in
mysql-5.1.61/sql/Makefile.am    
mysql-5.1.61/sql/Makefile.in
mysql-5.1.61/sql/lex_hash.h
mysql-5.1.61/storage/innodb_plugin/plug.in 


These Solved Primarily the Below Two Issues, Cross Compile Check during
./configure and lex_hash Which Gets Build for the Target System but Expected
to Run on Host 

----------------------------------------------------------------------------
----------------------------------
checking for sched_yield... (cached) yes
checking for fdatasync... (cached) yes
checking for localtime_r... (cached) yes
checking whether byte ordering is bigendian... (cached) yes
checking whether GCC atomic builtins are available... configure: error: in
`/home/rajaram/ltib-mpc8308erdb-20100413/rpm/BUILD/mysql-5.1.61':
configure: error: cannot run test program while cross compiling
See `config.log' for more details.
error: Bad exit status from
/home/rajaram/ltib-mpc8308erdb-20100413/tmp/rpm-tmp.92007 (%build)


RPM build errors:
    Bad exit status from
/home/rajaram/ltib-mpc8308erdb-20100413/tmp/rpm-tmp.92007 (%build)
Build time for mysql: 54 seconds

Failed building mysql


f_scbuild() returned an error, exiting
traceback:
 main:560

Exiting on error or interrupt

----------------------------------------------------------------------------
----------------------------------
make[2]: Leaving directory
`/home/rajaram/ltib-mpc8308erdb-20100413/rpm/BUILD/mysql-5.1.61/sql'
./gen_lex_hash > lex_hash.h-t
/bin/sh: ./gen_lex_hash: cannot execute binary file
make[1]: *** [lex_hash.h] Error 126
make[1]: Leaving directory
`/home/rajaram/ltib-mpc8308erdb-20100413/rpm/BUILD/mysql-5.1.61/sql'
make: *** [all-recursive] Error 1
error: Bad exit status from
/home/rajaram/ltib-mpc8308erdb-20100413/tmp/rpm-tmp.12104 (%build)


RPM build errors:
    Bad exit status from
/home/rajaram/ltib-mpc8308erdb-20100413/tmp/rpm-tmp.12104 (%build)
Build time for mysql: 152 seconds

Failed building mysql


f_scbuild() returned an error, exiting
traceback:
 main:560

Exiting on error or interrupt

----------------------------------------------------------------------------
----------------------------------

5) Build, Install and Deploy the MySQL Package with 

$ ./ltib -m scbuild -p mysql
$ ./ltib -m scinstall -p mysql
$ ./ltib -m scdeploy -p mysql


The rootfs Image Size was 10MB Bigger Compared to When Building with
mysql-4.1.12, The Primary Reason being Bigger Size of 'mysql-test' Directory
(in the MySQL Install Folder '/usr'). For this I have Removed the
'mysql-test' and 'sql-bench' Directory after Install. If the MySQL Test and
Benchmark Suit is Required to Check MySQL is Working Fine in the Target
System (Must be Done Initially), Then Remove the Following Lines from the
'mysql.spec' File Under '%Install'

rm -fr $RPM_BUILD_ROOT/%{pfx}/%{_prefix}/mysql-test
rm -fr $RPM_BUILD_ROOT/%{pfx}/%{_prefix}/sql-bench

Attached is the 'mysql-5.1.61-1326634483.patch' and the 'mysql.spec' File
(Not Sure if Attachments are Allowed).

Please Help Evaluating, Thanks.

Regards
Rajaram Ghosh




-----Original Message-----
From: Stuart Hughes [mailto:address@hidden 
Sent: Friday, January 13, 2012 6:55 PM
To: Rajaram Ghosh
Cc: address@hidden
Subject: Re: [Ltib] MySQL Upgrade

Hi Rajaram,

You'll need to look on the website http://ltib.org/ (FAQ) and under the 
docs in the distribution.  There are some hints there.

Regards, Stuart

On 13/01/12 10:24, Rajaram Ghosh wrote:
> Hi Stuart,
> Please Give Us Some Pointers on How to Go about Upgrading the MySQL, and
PHP
> (We would Like to have PHP Working with MySQL, as We are Building a LAMP
> Server). We Don't have any Prior Knowledge about Modifying/Upgrading
things
> in Ltib, So Far Just Using the Ltib BSP as is.
>
> Appreciate Your Guidance, Thanks.
>
> Regards
> Rajaram
>
> -----Original Message-----
> From: Stuart Hughes [mailto:address@hidden
> Sent: Friday, January 13, 2012 2:18 PM
> To: Rajaram Ghosh
> Cc: address@hidden
> Subject: Re: [Ltib] MySQL Upgrade
>
> On 12/01/12 16:13, Rajaram Ghosh wrote:
>> Hi,
>> There was an Old Discussion about MySQL Used in Ltib being an Old Version
>> (http://lists.gnu.org/archive/html/ltib/2008-03/msg00005.html ).
>>
>> We are Using MySQL, and have the Need to Support Database Triggers,
> Events,
>> and Stored Procedures. The MySQL Version Used in Ltib is 4.1, Which
> doesn't
>> Support all these Features. We are Using a Ltib BSP from Freescale
>> (ltib-mpc8308erdb-20100413.iso). How Do We add Support for the Latest
> MySQL
>> (at least 5.1 or above), and What are the other Packages that also Need
>> Upgrade because of MySQL.
> You'll need to upgrade the MySQL package, I don't think it has many
> other dependent packages.
>> While selecting PHP from the Package List it Automatically Selects MySQL,
> is
>> it an Expected Behavior.
> Yes.  We wanted to make sure MySQL support was built into the PHP engine
> that was built.
>
> Regards, Stuart
>

mysql.spec
Description: Binary data

mysql-5.1.61-1326634483.patch
Description: Binary data