Message: previous - next
Month: March 2011

Re: [trinity-devel] Bugs, bugs, bugs

From: Timothy Pearson <kb9vqf@...>
Date: Fri, 04 Mar 2011 22:12:26 -0600
On 03/04/2011 10:03 PM, Darrell Anderson wrote:
> Sounds like a good idea to me. But...
> Is the current effort toward supporting cmake negating building with automake? That is, can svn still be built with automake scripts or is that option now a dead end?
Automake should work on the distributions and platforms that it 
originally did, i.e. autoconf <= 2.63 and automake <= 1.12 IIRC.  It 
will not work with versions of autoconf/automake higher than that due to 
the unfixable problems that have forced our hasty move to CMake.
> The wiki seems to contain the information I need to rewrite my build scripts, but I'm no developer and will need time to make that transition and fully test. The wiki states that only a handful of packages are fully tested with cmake. Does that mean Trinity is in no man's land right now with respect to building all packages? Or do some packages have to be built with cmake and others with automake? Or can either build process be used?
Unfortunately, the answer is yes if you do not fit into the version 
brackets I mentioned above.  Work is progressing rapidly I am glad to 
say, but it will still take some time.
> If I no longer can build with automake then I have to learn about cmake and revise all of my build scripts. My challenge is if automake no longer is supported in svn, then I am unable to help test any patches.
> If I can still build svn with automake then I'll help test patches.
Yes you can, but only on your Slackware 12 system I think.  Slackware 13 
most likely bumped the autoconf/automake versions too high for Trinity 
to compile, just like all the other major distros.
> Side note to developers: please do not automatically close a report until the original filer reports the status of the patch. Let's build quality software and not just count beans. :) Also note in the bugzilla all packages that need to be rebuilt to test a specific bug report. A bug report might related to one app, but might require rebuilding more than one package.
+1.  That is bad practice. :)  Now after a certain number of days/weeks 
with no response the bug should probably be closed as it has been 
abandoned, but if the original reporter responds in a timely fashion the 
bug status should be left alone by the developer(s).
> Notice that even with a dual core machine, building the entire suite of core packages and a handful of others requires about five to six hours. Testing patches will take time, especially when new build problems arise.
Understood.  I have a full build farm here and it can still take a day 
to rebuild all of Trinity from scratch.
> Darrell