Re: Re: MySQL port compile problems [was Re: rb-rubygems does not work]

[email protected] Fri, 25 Aug 2006 16:34:18 -0700
Newsgroups gmane.os.opendarwin.darwinports
Message-ID <[email protected]>
On 8/25/06, Ryan Schmidt <[email protected]> wrote:
>
> On Aug 26, 2006, at 00:16, [email protected] wrote:
>
> > pdating my ports tree, i gave 5.0.24 a go on my ppc and it still died
> > on the SHA1 errors.
>
> I don't have anything useful to say to that. I can't explain it. I
> upgraded just fine on my PowerBook G4.

quite right, i tired on another ppc machine (upgrading from 1.211 to
1.320 in the process) and didn't have a problem with the mysql5 port.
my main machine must have a wacked environment.

> > strangely though, on my intel machine, after i had upgraded from
> > 5.0.22 to 5.0.24 (without the SHA1 issue seen on my ppc), my rails
> > applications became quite unhappy accessing the database. it would
> > often work on the first try but the second would die. i needed to
> > uninstall, clean and reinstall rb-mysql5 and then it worked without a
> > problem. is this expected?
>
> I wouldn't have expected that, but then again I've never used Ruby.
> I've used PHP, which is compiled with MySQL support, and the
> expectation there would be that PHP was compiled with the MySQL
> 5.0.22 libraries, and updating to MySQL 5.0.24 does not pose a
> problem for this. PHP remains compiled against the 5.0.22 libraries,
> but these should be able to access a 5.0.24 server with no difficulties.

yeah i don't really get it, but at least the uninstall/clean/install worked out.

regards,
jean-pierre