Summary: | MySQLCC will not compile with MySQL 4.1.3-beta | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Duncan Hill <gentoo-bugs> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | aross |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Modified ebuild
Patch as per URL in bug |
Description
Duncan Hill
2004-08-18 01:43:28 UTC
Created attachment 37647 [details]
Modified ebuild
Contains epatch line for using patch to fix bug.
Created attachment 37650 [details, diff]
Patch as per URL in bug
Fixes compile issue. I realise that MySQLCC is deprecating, but it's still a
damn useful tool, and making it support the upcoming engines won't hurt.
'Works for me'
Surely MySQLCC will still fail to compile against versions of MySQL which are not EXACTLY 4.1.3 or 5.0.1 ? Blah, this is what I get for searching for patches when doing work. Yes, it would. Assuming the API change is permanent, and that #if can use >=, changing the == to >= would suffice I think. Alternately, modifying the epatch test to check to see if the version being emerged is > 4.1.3 or 5.0.1 would also work? As far as I can see these mysql versions are not even in portage. This let me think why mysqlcc should stay in the tree, when there is no problem for you to get along with this development stuff on your own. You'll surly be able to maintain a mysqlcc ebuild in your local overlay. Anyway, I changed the patch to >=4.1.3, added a warning and marked it stable on x86 to let users of 0.9.3 know about it. In a few days teh ebuild will be masked and fade away after a while. |