workbench-5.1.1-alpha on Fedora 9

8 Comments

1. David Freeman
   Posted March 9, 2009 at 9:03 am | Permalink

   The line with
   ‘ln -s /usr/include/ctemplate google’
   should read as
   ‘ln -s /usr/include/ctemplate /usr/include/google’
   if my failure to do ‘bash autogen.sh’ until creating the symbolic link is any proof. Just taking notes here as much as anything, since I imagine a number of people will continue to look at this helpful recipe/guide but hit that snag.

   Thanks again.

2. Geert
   Posted March 10, 2009 at 1:03 am | Permalink

   Any news on the Mac version?

3. byte
   Posted March 10, 2009 at 7:03 am | Permalink

   Hi!

   Well, it shouldn’t have to be on a Wiki - this stuff should just work. Its cluttered up on a weblog, because its still in alpha and well, doesn’t work as well yet

   Compiling WB from source does not require you to have mysql-gui-tools. They’re independent.

   Now, I’m in a rock and a hard place. 5.1.1-alpha is well, mostly outdated by today’s standards. We’ve hacked on the tree much, and I’ve sent in a few patches to ensure more goodness with gcc-4.3. However, the source tree is *drumroll* internal only.

   The workbench team is working on how to start sharing this code, as soon as possible. Its a priority to get it on Launchpad at some stage.

   I wish I can give you more concrete answers, but there’s no point in me promising something that I have no ability to deliver on (I’m not involved in the process)

   Hope this helps… Watch the workbench blog as well as mine if you’re interested in the future, post-alpha

   Thanks for trying the software (or trying to) as well

4. Landon
   Posted March 10, 2009 at 7:03 am | Permalink

   I just purchased WB SE and really like it. Am looking forward to seeing it running on Linux and particularly on Fedora. Great job!

5. David Freeman
   Posted March 10, 2009 at 7:03 am | Permalink

   Sorry Colin,

   My first post was ruined by my attempt to pseudo-quote a string with double less-than signs followed by the string, then double greater-than signs –so the heart of the text was omitted and therefore the comment was rendered useless. I am sorry for mixing things up by that mistake.

   After noticing how my comment/question was parsed, I reintroduced the same remark with the same knee-jerk “don’t substitute a subset of $PATH when you only want to append/prepend to it” reaction that I had after imbibing your generous, step-by-step howto here. Thank you again for it.

   I see now that indeed we are talking about the PKG_CONFIG environment variable rather than $PATH, which I kind of suspected but did not make register. I certainly would like to see this process Wikified rather than clutter up the weblog, so please cleanse the comments as soon as you see fit.

   I have an ulterior motive here:

   I would like to ask whether or not compiling from the WB source (still) requires a successful compilation of the mysql-gui-tools source, and for whatever pointers you might share regarding this substantial hurdle for my recent reinstallation of FC9. Might you profile the WB-ready package configuration for FC9?

   Thanks for everything here, Colin!

6. byte
   Posted March 10, 2009 at 9:03 am | Permalink

   Hi David,

   Regarding your first comment, I don’t know what you’re referring to . There is no copy paste scenario, you’re expected to use either one of the include files that are missing.

   Now, with the second post, I made a tiny boo boo (make note to self: don’t write technical blog posts when in a semi-drunken and tired state)

   You want to do:
   export PKGCONFIG_PATH= instead of export PATH.

   Sorry, I fixed the blog post

7. David Freeman
   Posted March 11, 2009 at 4:03 am | Permalink

   [Tried to use a ghetto macron with doubled less-than/greater-than characters and got parsed into ellipsis; sorry for the repost.]

   Thanks to you for this Colin and to the WB team for all the refinement entailed by the rewrite and delivery of my ERD tool of choice.

   I think that in view of the copy/paste scenario, a correction of
   export PATH=/usr/local/lib/pkgconfig.
   to either
   export PATH=$PATH:/usr/local/lib/pkgconfig; $(echo $COMMAND_STRING)
   or the limited scope
   PATH=$PATH:/usr/local/lib/pkgconfig $(echo $COMMAND_STRING)
   might well avoid a scratched head or two.

8. David Freeman
   Posted March 11, 2009 at 8:03 am | Permalink

   Thanks to you for this Colin and to the WB team for all the refinement entailed by the rewrite and delivery of my ERD tool of choice.

   I think that in view of the copy/paste scenario, a correction of
   <>
   to either
   <>
   or
   <>
   might well avoid a scratched head or two.