> > The small problem in mysql is it does not check if parameter is
> > correct in configure script - this produced the problem...
> > Peter mailto:[EMAIL PROTECTED]
Yes, I don't know of any clear way of handling this with
autoconf. Basically, if your option starts wi
Ok :)
the problem solved. It was a wrong glibc after all.
Regards,
Heikki
At 01:07 PM 8/8/01 +0400, you wrote:
>Hello Heikki,
>
> Sorry for confuse. The problem is The first complied binary I've
> checked which was fine was complied with --with-other-glibc=XXX
> therefore the correct option
Peter Zaitsev writes:
> Hello Michael,
>
> Tuesday, August 07, 2001, 10:20:18 PM, you wrote:
>
> The question is which place do you do aply timezone ?
>
> I found the following interesting thing: Then mysql is started it uses
> correct timestamp, therefore INNODB is started with wrong timestamp
On Tuesday 07 August 2001 09:10, Heikki Tuuri wrote:
> Hi!
>
> No idea what is wrong. Below is the code which
> prints the timestamp in InnoDB:
> .
>
> struct tm cal_tm;
> struct tm* cal_tm_ptr;
> time_t tm;
>
> time(&tm);
>
> #ifdef HAVE_LOCALTIME_R
> localtime_
TED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Tuesday, August 07, 2001 5:41 PM
Subject: Re: Timezone problem.
>Hello Michael,
>
>Tuesday, August 07, 2001, 10:20:18 PM, you wrote:
>
>OK guys I think I've found the problem
Hello Michael,
Tuesday, August 07, 2001, 10:20:18 PM, you wrote:
OK guys I think I've found the problem.
It seems like new innodb version (40b) does something bad with time.
I've tested 3 binaries
1) Plain .40 with normal GLIBC -> OK
2) Plain .40 with patched GLIBC -> OK
3) Plain .40 with new
Peter Zaitsev writes:
> Hello mysql,
>
> It seems like you made an incomportable changes in 3.23.40 without
> taking a time to write a release note :(
>
> The mysql 3.23.39 used the system timezone by default:
>
> maindb:/spylog/mysql/logs # date
> Tue Aug 7 13:31:56 MSD 2001
>
> | tra
