From: Tom von Alten (tom_vonalten@boi.hp.com)
Date: Fri Jul 16 1999 - 10:09:03 CDT
Just getting around to unpacking this and trying it out. I have not
attempted to apply any of the patches subsequent to Daniel's version.
The following messages from my compiler
(on hp-ux 10.20, what /bin/cc:
LINT A.10.32.03 CXREF A.10.32.03
HP92453-01 A.10.32.03 HP C Compiler
/usr/lib/libc: $Revision: 76.3 $)
may be of interest:
cc -c -g -O -Ae date.c
cc: "date.c", line 294: warning 562: Redeclaration of "my_mktime" with a
different storage class specifier: "my_mktime" will have internal linkage.
cc -c -g -O -Ae parse.c
cc: warning 5004: Uninitialized variable "replynum" in function
"fixreplyheader" (5004)
cc -c -g -O -Ae threadprint.c
cc: "threadprint.c", line 127: warning 562: Redeclaration of
"format_thread_info" with a different storage class specifier:
"format_thread_info" will have internal linkage.
cc: "threadprint.c", line 173: warning 562: Redeclaration of
"print_replies" with a different storage class specifier: "print_replies"
will have internal linkage.
At the very end, when it goes to stitch all the object files together, I
get a big list of "pxdb internal warning"s, like
pxdb internal warning: cu[19]: SLT_SRCFILE[238] out of synch
ending with
pxdb: internal error. File won't be debuggable (still a valid executable)
I have no idea what all that means (I'm supposed to "contact (my) HP
support representative." :) This happened on 2a21 also, but the executable
seemed to work just fine.
Initial testing shows that v2a23 works just fine, and that the message time
problems (that I reported for 2a21) have been fixed, and archive locking
looks A-OK.
Thanks to all who contributed!
_____________ Hewlett-Packard Computer Peripherals Bristol
Tom von Alten mailto:Tom_vonAlten@boi.hp.com
This posting is for informational purposes only.
It is not a statement of the Hewlett-Packard Co.