List:General Discussion« Previous MessageNext Message »
From:Mark Date:May 7 2009 1:23pm
Subject:RE: Problems After MySql 5.1.34
View as plain text  
Depends on your OS, I guess. On FreeBSD you can just go to the

'php5-extensions' port, run a 'make config', and deselect everything but

the MySQL extension. Then it will only build for you. Very easy.



- Mark



From: Martin Gainty [mailto:mgainty@stripped] 
Sent: donderdag 7 mei 2009 15:15
To: admin@stripped; mysql@stripped
Subject: RE: Problems After MySql 5.1.34



this isnt mysql's fault that php has such abysmal build tools..try
requesting a web developer to simply download php and run the proprietary
binary tools
after a week of sleepless nights and endless searching for the right
dll/so/lib and endless searching for the right tools i guarantee they will
call no joy 
and implement the webapp in Java!

Disclaimer and Confidentiality/Verzicht und Vertraulichkeitanmerkung/Note de
déni et de confidentialité

This message is confidential. If you should not be the intended receiver,
then we ask politely to report. Each unauthorized forwarding or
manufacturing of a copy is inadmissible. This message serves only for the
exchange of information and has no legal binding effect. Due to the easy
manipulation of emails we cannot take responsibility over the the contents.

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
dient lediglich dem Austausch von Informationen und entfaltet keine
rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous
n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire
informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie
de ceci est interdite. Ce message sert à l'information seulement et n'aura
pas n'importe quel effet légalement obligatoire. Étant donné que les
peuvent facilement être sujets à la manipulation, nous ne pouvons accepter
aucune responsabilité pour le contenu fourni.

> From: admin@stripped
> Subject: RE: Problems After MySql 5.1.34
> Date: Thu, 7 May 2009 12:57:42 +0000
> To: mysql@stripped
> Gary wrote:
> > Welcome to the hell that is php + apache + mysql. If you upgrade your
> > MySql (especially major versions 5.0 => 5.1) you will also need to
> > recompile php against the new MySql client libs. We've had very
> > limited success trying to get it to work otherwise.
> Well, you don't actually have to recompile PHP entirely, of course: just
> its extension.
> @TS: Other than that, you basically need to recompile *everything* (or its
> mysql dynamic libraries) when you upgrade MySQL. This includes Perl, btw;
> so you'd need to build DBD:mysql as well (same for Python, etc).
> Walter wrote:
> > Any (major)upgrade of mysql client requires the dependent subsystem to
> > upgrade also. Anything else would be careless since you do not know if
> > interface has changed.
> Actually, you *do* know: that's what the changelog is for. :) When C
> header changes are made, an upgrade is in order. If not, when upgrading
> between minor versions, say, from 5.0.51 -> 5.0.67 (just an example), you
> won't need to recompile all system-wide MySQL client extensions. I've done
> this many times, without issue: you just need to be absolutely sure no
> header changes were made (when in doubt, recompile)..
> I recently upgraded to 5.1.34 as well; and it was indeed a hell. :) It's
> working just fine, but I spent several hours recompiling MySL client
> stuff; without doing so, your apps will likely behave erratically, or just
> segfault altogether.
> This isn't a MySL hell exclusively, btw. You'll get the same issue
> upgrading PostgreSQL, or BerkeleyDB, etc. It's just the nature of the
> beast.
> - Mark
> -- 
> MySQL General Mailing List
> For list archives:
> To unsubscribe:


Windows LiveĀ™: Keep your life in sync. Check it out.

Problems After MySql 5.1.34Johnny Stork6 May
  • Re: Problems After MySql 5.1.34Johnny Stork6 May
    • RE: Problems After MySql 5.1.34Gary Smith6 May
      • Re: Problems After MySql 5.1.34walter harms7 May
        • RE: Problems After MySql 5.1.34Mark7 May
          • RE: Problems After MySql 5.1.34Gary Smith7 May
            • Re: Problems After MySql 5.1.34 - THANKSJohnny Stork9 May
    • Re: Problems After MySql 5.1.34Joerg Bruehe7 May
  • Re: Problems After MySql 5.1.34Joerg Bruehe7 May
    • RE: Problems After MySql 5.1.34Gary Smith7 May
RE: Problems After MySql 5.1.34Mark7 May