Andrew Ross wrote:
(1) Normally, I believe it should be the user's responsibility to set the
flags appropriate for their compiler.
So what happens if you simply use
FC='ifort -assume byterecl'
?
If that works for all examples without messing them up, then perhaps we
should recommend that
Just a note that I can't seem to fix the problem in Ada example 17
(stripchart demo) wherein all of the legend strings appear on the
plot identical to the fourth one. I've tried a lot of things and at
this point I'm afraid it will have to be a known issue.
The crux is matching e.g. this
Doing gdb sessions in the build tree is pretty tricky because of all the
setup (e.g., setting environment variables) you have to do first. So I
don't
recommend it except for rare emergencies where you get errors in the build
tree but not the install tree. Furthermore, ctest doesn't have a
On Thursday, August 14, 2008 at 03:29:28 (-0700) Jerry writes:
Just a note that I can't seem to fix the problem in Ada example 17
(stripchart demo) wherein all of the legend strings appear on the
plot identical to the fourth one. I've tried a lot of things and at
this point I'm
On 2008-08-14 08:14-0600 [EMAIL PROTECTED] wrote:
My problem is that I'm building RPM packages and so it's pretty much
impossible to do the testing in the install tree. I'll work on a patch.
Thanks in advance, Orion. I suggest instead of using --debug, you use
--extra-verbose as the name of
On 2008-08-14 09:58-0500 Maurice LeBrun wrote:
For C C++, a const pointer means the memory it points to cannot be altered.
The pointer can. So for example
const char *foo = bar;
(or later reassignment) is perfectly legit.
After years of dabbling at C, this pointer stuff still makes my
On Thursday, August 14, 2008 at 10:18:32 (-0700) Alan W. Irwin writes:
On 2008-08-14 09:58-0500 Maurice LeBrun wrote:
For C C++, a const pointer means the memory it points to cannot be
altered.
The pointer can. So for example
const char *foo = bar;
(or later
On Thu, Aug 14, 2008 at 08:14:25AM -0600, [EMAIL PROTECTED] wrote:
Doing gdb sessions in the build tree is pretty tricky because of all the
setup (e.g., setting environment variables) you have to do first. So I
don't
recommend it except for rare emergencies where you get errors in the
On Thu, Aug 07, 2008 at 04:20:40PM +0100, Andrew Ross wrote:
Tcl is lagging well behind. We're lacking any dedicated tcl users to
help with this.
Now that the Fortran examples and bindings are so nicely in shape,
I want to dedicate some time to Tcl.
Having said that, while waiting for a
On Thu, Aug 07, 2008 at 04:20:40PM +0100, Andrew Ross wrote:
MSVC 6.0 does not like the long long type in plplot.h!
This is odd: things worked before - the problem is that this
compiler does not have a stdint.h, so the fallback is used.
Actually MSVC 6.0 on my machine does not like 64
On Thu, Aug 07, 2008 at 04:20:40PM +0100, Andrew Ross wrote:
MSVC 6.0 does not like the long long type in plplot.h!
This is odd: things worked before - the problem is that this
compiler does not have a stdint.h, so the fallback is used.
Actually MSVC 6.0 on my machine does not like 64
11 matches
Mail list logo
