Brian and I spun up the Fedora15 node a week ago, and he has notes on what we had to do to make Drizzle build on it. Brian, could you give Henrik and myself those notes?
I need to create a new replacement F15 node, but the one we did create now doesn't have at root access or sudo access. When I get those notes, I will create a new F15. On investigation, we don't have sudo access to the f14 and f13 nodes either. <facepalm> I do know a doc where the root passwords are, I will get that from Monty, and then will create a hingo user on the RPM based machines. ..m On Tue, Jan 10, 2012 at 12:15 AM, Henrik Ingo <[email protected]> wrote: > Actually, my questions need answering first: What non-standard things > have you done that makes this build on RHEL/Centos 5.x? For me recent > versions of trunk require too new versions of flex and bison. > > Perhaps just give me most recent version of Fedora for starters, that > should work best. > > henrik > > On Tue, Jan 10, 2012 at 10:07 AM, Henrik Ingo <[email protected]> > wrote: >> One with RHEL, CentOS or Fedora. Eventually of course all of them >> since we want to test and build rpms on all variants. >> >> henrik >> >> On Tue, Jan 10, 2012 at 1:40 AM, Mark Atwood <[email protected]> wrote: >>> HI Henrik, >>> >>> Which machines do you need sudo access to? >>> >>> ..m >>> >>> On Sat, Jan 7, 2012 at 1:41 PM, Henrik Ingo <[email protected]> >>> wrote: >>>> Hi Mark >>>> >>>> I don't have access to our boxes that are Jenkins slaves. Could you >>>> either a) give me root access, or b) look into this yourself. ( b >>>> shouldn't be too difficult, at least try just a yum install first ...) >>>> >>>> + make rpm >>>> ... >>>> rpmbuild --define="_topdir `pwd`/support-files/rpm/" -ba >>>> support-files/rpm/SPECS/drizzle7.spec >>>> error: Failed build dependencies: >>>> protobuf-devel is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> pam-devel is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> gnutls-devel is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> chrpath is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> doxygen is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> gettext-devel is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> boost-devel >= 1.39 is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> boost-iostreams is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> v8-devel is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> gcc-c++ >= 4.4 is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> libuuid-devel is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> libcurl-devel is needed by drizzle7-2011.11.29.2491-1.x86_64 >>>> >>>> I'm a bit surprised by some of these, like gcc, boost and protobuf not >>>> being there. Do you install them from source and not as rpms? >>>> >>>> I personally only tested on CentOS 6, but we seem to have only >>>> CentOS/rhel 5.x Jenkins slaves. So I'm not 100% sure all of the above >>>> are found on a 5.x. In fact, v8 doesn't exist in standard 5.x repos, >>>> but I can change the .spec file to not try to build that on el5. >>>> >>>> henrik >>>> >>>> >>>> >>>> On Sat, Jan 7, 2012 at 11:32 PM, Henrik Ingo <[email protected]> >>>> wrote: >>>>> And here's the merge request where the same code is moved into main >>>>> drizzle repository instead: >>>>> >>>>> https://code.launchpad.net/~hingo/drizzle/drizzle-integrate-packaging-rpm/+merge/87862 >>>>> >>>>> You can now do 'make rpm' directly from drizzle sources. (In fact you >>>>> could do that since last week already since Brian committed something >>>>> similar, but this one builds on how packages were built in Drizzle 7 >>>>> so should be more compatible for upgrades and such.) >>>>> >>>>> Here's my ongoing work to build rpms automatically in Jenkins: >>>>> >>>>> http://jenkins.drizzle.org/job/drizzle-pkg-rpm-template/configure >>>>> >>>>> henrik >>>>> >>>>> >>>>> >>>>> On Fri, Jan 6, 2012 at 11:40 PM, Henrik Ingo <[email protected]> >>>>> wrote: >>>>>> Hi BJ >>>>>> >>>>>> Since we agreed on all review points I now pushed my work into >>>>>> https://code.launchpad.net/~drizzle-developers/pkg-drizzle/drizzle7-dev.rpm >>>>>> >>>>>> I wanted to do that so I can record a correct bzr revno into my next >>>>>> commit log, which is to copy that working code into a lp:drizzle >>>>>> branch. (I already have it working, but accidentally committed a >>>>>> source tarball into it, so need to redo :-) >>>>>> >>>>>> henrik >>>>>> >>>>>> -- >>>>>> [email protected] >>>>>> +358-40-8211286 skype: henrik.ingo irc: hingo >>>>>> www.openlife.cc >>>>>> >>>>>> My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 >>>>> >>>>> >>>>> >>>>> -- >>>>> [email protected] >>>>> +358-40-8211286 skype: henrik.ingo irc: hingo >>>>> www.openlife.cc >>>>> >>>>> My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 >>>> >>>> >>>> >>>> -- >>>> [email protected] >>>> +358-40-8211286 skype: henrik.ingo irc: hingo >>>> www.openlife.cc >>>> >>>> My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 >> >> >> >> -- >> [email protected] >> +358-40-8211286 skype: henrik.ingo irc: hingo >> www.openlife.cc >> >> My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 > > > > -- > [email protected] > +358-40-8211286 skype: henrik.ingo irc: hingo > www.openlife.cc > > My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559 _______________________________________________ Mailing list: https://launchpad.net/~drizzle-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~drizzle-discuss More help : https://help.launchpad.net/ListHelp
