Skip to content
Prev 4828 / 63421 Next

(HP-UX) scan: last line gets duplicated (PR#790)


        
Prof Brian D Ripley wrote:

            
That would be me. I reported this bug before, for R version
1.1.0
I would fix it, if I new how to. Perhaps you can suggest
something from the warning messages I get.

During compiling I get a lot of warning messages. These are for
scan.c:

	cc -I. -I../../src/include -I../../src/include
  -I/opt_local/opt/readline/include I/opt_local/opt/tk/include
  --I/opt_local/opt/tcl/include I/opt_local/opt/jpeg6/include
  -I/opt_local/opt/png/include I/opt_local/opt/ncurses/include
  -I/opt_local/opt/zlib/include I/users1/kleiweg/R-1.2.0-source
  --DHAVE_CONFIG_H D_HPUX_SOURCE +DA1.1 +DS1.1 -Wp,-H16000
  -I/opt_local/opt/readline/include I/opt_local/opt/tk/include
  --I/opt_local/opt/tcl/include I/opt_local/opt/jpeg6/include
  -I/opt_local/opt/png/include I/opt_local/opt/ncurses/include
  -I/opt_local/opt/zlib/include I/users1/kleiweg/R-1.2.0-source
  -L/opt_local/opt/readline/lib -L/opt_local/opt/tk/lib
  -L/opt_local/opt/tcl/lib -L/opt_local/opt/jpeg6/lib
  -L/opt_local/opt/png/lib -L/opt_local/opt/ncurses/lib
  -L/opt_local/opt/zlib/lib L/users1/kleiweg/R-1.2.0-source -Aa -c
  -scan.c -o scan.o
cc: "scan.c", line 65: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 65: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 72: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 72: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 109: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 109: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 300: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 300: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 309: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 309: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 336: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 336: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 350: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 350: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 449: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 449: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 478: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 478: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 858: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 858: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 919: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 919: warning 563: Argument #1 is not the correct type.
cc: "scan.c", line 957: warning 604: Pointers are not assignment-compatible.
cc: "scan.c", line 957: warning 563: Argument #1 is not the correct type.

I get these type of warnings when compiling other sources too:
	sock.c
	sys-std.c
	connections.c
	g_alab_her.c
	../../../R/src/main/gram.y
	iosupport.c
	main.c
	plot3d.c
	saveload.c

Other warnings I get are:

cc: "loglin.c", line 236: warning 562: Redeclaration of "collap"
  with a different storage class specifier: "collap" will have
  internal linkage.
cc: "loglin.c", line 315: warning 562: Redeclaration of "adjust"
  with a different storage class specifier: "adjust" will have
  internal linkage.

cc: "dataentry.c", line 1309: warning 562: Redeclaration of
  "closewin" with a different storage class specifier: "closewin"
  will have internal linkage.
cc: "dataentry.c", line 1553: warning 562: Redeclaration of
  "popupmenu" with a different storage class specifier:
  "popupmenu" will have internal linkage.
cc: "dataentry.c", line 1653: warning 562: Redeclaration of
  "popdownmenu" with a different storage class specifier:
  "popdownmenu" will have internal linkage.

cc: "fexact.c", line 315: warning 562: Redeclaration of "f2xact"
  with a different storage class specifier: "f2xact" will have
  internal linkage.
cc: "fexact.c", line 842: warning 562: Redeclaration of "f3xact"
  with a different storage class specifier: "f3xact" will have
  internal linkage.
cc: "fexact.c", line 1188: warning 562: Redeclaration of
  "f4xact" with a different storage class specifier: "f4xact" will
  have internal linkage.
cc: "fexact.c", line 1413: warning 562: Redeclaration of
  "f5xact" with a different storage class specifier: "f5xact" will
  have internal linkage.
cc: "fexact.c", line 1572: warning 562: Redeclaration of
  "f6xact" with a different storage class specifier: "f6xact" will
  have internal linkage.
cc: "fexact.c", line 1623: warning 562: Redeclaration of
  "f7xact" with a different storage class specifier: "f7xact" will
  have internal linkage.
cc: "fexact.c", line 1726: warning 562: Redeclaration of
  "f8xact" with a different storage class specifier: "f8xact" will
  have internal linkage.
cc: "fexact.c", line 1770: warning 562: Redeclaration of
  "f9xact" with a different storage class specifier: "f9xact" will
  have internal linkage.
cc: "fexact.c", line 1803: warning 562: Redeclaration of
  "f10act" with a different storage class specifier: "f10act" will
  have internal linkage.
cc: "fexact.c", line 1871: warning 562: Redeclaration of
  "f11act" with a different storage class specifier: "f11act" will
  have internal linkage.
cc: "fexact.c", line 1896: warning 562: Redeclaration of
  "prterr" with a different storage class specifier: "prterr" will
  have internal linkage.
cc: "fexact.c", line 1921: warning 562: Redeclaration of "iwork"
  with a different storage class specifier: "iwork" will have
  internal linkage.