On Sat, Jul 23, 2011 at 3:03 AM, Barry Smith wrote:
>
> Matt,
>
> When a user provides --download-packagename for any package that does not
> support --download- configure silently ignores their request leading the
> user to think that it actually did download the package.
>
> This is bec
Thanks, seems to work.
Barry
On Jul 22, 2011, at 8:10 PM, Matthew Knepley wrote:
> On Sat, Jul 23, 2011 at 3:03 AM, Barry Smith wrote:
>
> Matt,
>
> When a user provides --download-packagename for any package that does not
> support --download- configure silently ignores their
Matt,
When a user provides --download-packagename for any package that does not
support --download- configure silently ignores their request leading the user
to think that it actually did download the package.
This is because in package.py there is the code
def checkDownload(self
On Apr 20, 2011, at 1:43 PM, Matthew Knepley wrote:
> On Wed, Apr 20, 2011 at 1:24 PM, Barry Smith wrote:
>
> Matt,
>
> I wanted to add to valgrind.py a test that made sure valgrind.h was
> compilable. So I added a simple test
>
> self.checkCompile('#include ','RUNNING_ON_VALGRIND;\n')
On Wed, Apr 20, 2011 at 1:24 PM, Barry Smith wrote:
>
> Matt,
>
> I wanted to add to valgrind.py a test that made sure valgrind.h was
> compilable. So I added a simple test
>
> self.checkCompile('#include
> ','RUNNING_ON_VALGRIND;\n')
>
> the problem is I do not know where you stash the dir
Matt,
I wanted to add to valgrind.py a test that made sure valgrind.h was
compilable. So I added a simple test
self.checkCompile('#include ','RUNNING_ON_VALGRIND;\n')
the problem is I do not know where you stash the directory where the include
file is put therefor the test fails bec