On 10/20/2010 9:29 AM, Tim St. Clair wrote:
when using ExternalProject_Add with hand built version of cmake 2.8.2
seems to have a series of issues with auto tools relating to the env,
the afore mentioned example is a direct repo. Where it will fail in
RHEL 5.5 re-running aclocal (when I don't b
On Wed, Oct 20, 2010 at 8:19 AM, Bill Hoffman wrote:
> On 10/20/2010 9:08 AM, Tim St. Clair wrote:
>>
>> correction, I can see this issue with 2.8.2 i386 binaries vs. hand build.
>>
>
> Tim, it is still unclear to me what your problem is
when using ExternalProject_Add with hand built version of c
On 10/20/2010 9:08 AM, Tim St. Clair wrote:
correction, I can see this issue with 2.8.2 i386 binaries vs. hand build.
Tim, it is still unclear to me what your problem is and where you are
getting the binaries from.
So, a few questions:
1. Where did the binaries come from (i.e. cmake.org, s
correction, I can see this issue with 2.8.2 i386 binaries vs. hand build.
On Wed, Oct 20, 2010 at 7:40 AM, Tim St. Clair wrote:
> 2.8.0 vs. 2.8.2 hand made
>
> On Tue, Oct 19, 2010 at 4:24 PM, David Cole wrote:
>> What version are these stock i386 binaries you speak of?
>> Where did they come fr
2.8.0 vs. 2.8.2 hand made
On Tue, Oct 19, 2010 at 4:24 PM, David Cole wrote:
> What version are these stock i386 binaries you speak of?
> Where did they come from?
> For 2.8.1 and earlier the problem did not exist.
> For 2.8.2, the problem did exist.
> It should be fixed again in 2.8.3-rc2 and la
What version are these stock i386 binaries you speak of?
Where did they come from?
For 2.8.1 and earlier the problem did not exist.
For 2.8.2, the problem did exist.
It should be fixed again in 2.8.3-rc2 and later.
On Tue, Oct 19, 2010 at 4:18 PM, Tim St. Clair wrote:
> b4 I do this, because
b4 I do this, because it's a non-trivial investment on a
non-heterogeneous build cluster, can you explain why the i386 stock
binaries behave differently?
Cheers,
Tim
On Tue, Oct 19, 2010 at 2:58 PM, Bill Hoffman wrote:
> Try the 2.8.3 release candidate.
>
> In 2.8.2 the untar did not preserve fi
Try the 2.8.3 release candidate.
In 2.8.2 the untar did not preserve file times, and this could cause
auto-make to rerun when it really did not need to.
-Bill
On 10/19/2010 3:21 PM, Tim St. Clair wrote:
I've been able to consistently repro an issue using
ExternalProject_Add w/a configure bu
I've been able to consistently repro an issue using
ExternalProject_Add w/a configure build of cmake v.s. the i386
binaries online shows an issue whenever a it tries to call auto-conf
or auto-make as if the environment is hosed. When I use the stock
i386 binaries I do not see this issue and I'm ab
