On Monday 21 January 2002 5:09 pm, Joao Cardoso wrote:
> On Monday 21 January 2002 7:28 am, Alan W. Irwin wrote:
> > On Mon, 21 Jan 2002, [iso-8859-1] Jo=E3o Cardoso wrote:
> > > On Sunday 20 January 2002 16:59, Alan W. Irwin wrote:
> > > | [...]But you may have some different configuration
> > > | that did not work as expected or there may be something wrong wit=
> > > | the m4 pre-processing that occurs on your machine.
> In the x06f.f file, after m4 processing, appears indeed a very long lin=
> the first fortran source line:
> ! Displays the plotter
>traceoff,traceon,translit,undef,undefine,undivert for PLPOIN <--- from t=
> comment until here is a one comment line! implicit none <--- this is
> another line
> integer i, j, k
> real*4 x, y
> character*3 text
> ! Full sized page for display
> So it seems that this is a m4 problem. But suse-7.2 is not that old, an=
> suse system is updated with the last changes... (rpm says that m4 was
> "Build Date: Fri 11 May 2001")
> The problem seem to be the word "symbols" in the comments and in the la=
> plmtex() arguments of file x06f.fm4; if I remove the word "symbols" fro=
> the comments, the lines will be no more expanded by m4 as above. What i=
> the real cure for this?
'info m4' says that:
Getting the defined macro names
The name of the currently defined macro can be accessed by `symbols=
which results in a sorted list of quoted strings. This contrasts w=
`dumpdef' which output can not be accessed by `m4' programs.
When given arguments, `symbols' returns the sorted subset of the
symbols currently defined:
symbols(`ifndef', `ifdef', `define', `undef')
I can't however avoid "symbols" to be expanded by m4, by quoting it, as i=
`symbols'. The quick cure for the release is to just remove the word--aft=
all it is just a comment. Comments?
> > > jcard@... > g77 --version
> > > GNU Fortran 0.5.25 19991024 (release)
> > >
> > > jcard@... > m4 --version
> > > GNU m4 1.4o
> > Again, I cannot reproduce the problem you have reported. I configured
> > exactly as you above on a clean checkout. All the major flags at the=
> > of config message were identical to yours. The driver lists looked t=
> > same (although that should not matter). My system found f77 rather th=
> > g77, but on Debian woody that is a symlink to g77.
> > I get the following:
> > f77 --version
> > GNU Fortran 0.5.25 20010319 (prerelease)
> > [+ lots of stuff about the lack of warranty, etc.]
> > m4 --version
> > GNU m4 1.4
> > make fdemos works like a charm, and I even tried x06f and x07f and th=
> > produced the same boring (;-) results as always.
> > I can think of two possibilities.
> > (1) Somehow your plplot system is confused by
> > a mix of old and new results. Please try again with a clean checkout=
> > you didn't have that already).
> > (2) I am also somewhat concerned about the two-yr old date on your g7=
> > compiler compared to mine. Maybe there is too long a line (as mentio=
> > in one of your error messages) for your old compiler. In that case, =
> > the longest line in your x06f.f source, find the equivalent line in
> > x06f.fm4 and split it into two lines (by using almost any character i=
> > the 6th column for the continued line as you can see from other *.fm4
> > files that have continuations) and try again. If a line split solves=
> > problem, go ahead and commit the modified x06f.fm4 results. And
> > similarly for x07f.fm4 assuming that problem is due to the same cause=
> > I don't want this to drag on so while Joao is doing further tests wit=
> > clean checkouts/and or line splitting will others please take a few
> > minutes to try to reproduce the bug? We may need more eyeballs on th=
> > one to solve it, and I am hamstrung because I cannot reproduce it.
> > Thanks in advance.
> > Alan
> > _______________________________________________
> > Plplot-devel mailing list
> > Plplot-devel@...
> > https://lists.sourceforge.net/lists/listinfo/plplot-devel
> Plplot-devel mailing list