zsh-workers
 help / color / mirror / code / Atom feed
* PATCH: build problem with signals on HP/UX,ia64
@ 2004-03-11 17:53 Oliver Kiddle
  0 siblings, 0 replies; only message in thread
From: Oliver Kiddle @ 2004-03-11 17:53 UTC (permalink / raw)
  To: Zsh workers

I traced the cause of the signals problem on HP/UX (ia64). The cause
was the preprocessor output as opposed to awk. The relevant lines of
sigtmp.out look like this:

#line 3
XXNAMES XXSIGHUP 1
 XXNAMES XXSIGINT 2
 XXNAMES XXSIGQUIT 3
 XXNAMES XXSIGILL 4

with all subsequent signals also indented by one space. signames2.awk's
regex looks like this:
  /^XXNAMES XXSIG[A-Z][A-Z0-9]*[\t ][\t ]*[1-9][0-9]*/ {

Obvious fix would be to add ` ?' to the beginning but the patch below adds
`[\t ]*' because I'm supposing that some other preprocessor might someday
decide to use some other indentation. I'll hold off till tomorrow before
committing this.

Current status with respect to HP testdrive machines is as follows:

Tru64 4.1               - couldn't log on so untried
Tru64 5.1   ev7     cc  - builds and tests fine
Tru64 5.1   ev7     gcc - untried (gcc was a broken symlink)
HP/UX 11.11 PA-RISC cc  - builds fine, completion tests using zpty hang,
                          otherwise fine
HP/UX 11.11 PA-RISC gcc - builds fine, tests fine except zpty fails to load
HP/UX 11.22 Itanium gcc - builds fine, tests fine[*], zpty fails to load
HP/UX 11.22 Itanium cc  - signals problem above, with the fix, all is okay:
                          build fine and and test okay (except Y01 zpty hang).
I was trying HP/UX 11.23 yesterday with similar results to 11.22. Haven't
tried it today. Haven't tried their BSD machines either.

Compilers on the Itanium systems seem to be quite different from those
on PA-RISC.

Since zpty failing is far from critical, that really just leaves AIX to
worry about. Unless we want to clear up the compiler warnings too.

Oliver

[*] actually a test in A04 fails because rm -f * didn't get rid of all
the files (it is not a local filesystem and rm fails a bit). I also get
[[ -g ... ]] tests failing on all HP testdrive systems because you
can't set setgid on files. Would it perhaps be worth doing tests with
files in /tmp or /var/tmp if we find it to be writable. That'd remove a
lot of NFS related failures.

Index: Src/signames2.awk
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/signames2.awk,v
retrieving revision 1.2
diff -u -r1.2 signames2.awk
--- Src/signames2.awk	3 Mar 2004 10:42:59 -0000	1.2
+++ Src/signames2.awk	11 Mar 2004 17:39:01 -0000
@@ -6,7 +6,7 @@
 # NB: On SunOS 4.1.3 - user-functions don't work properly, also \" problems
 # Without 0 + hacks some nawks compare numbers as strings
 #
-/^XXNAMES XXSIG[A-Z][A-Z0-9]*[\t ][\t ]*[1-9][0-9]*/ {
+/^[\t ]*XXNAMES XXSIG[A-Z][A-Z0-9]*[\t ][\t ]*[1-9][0-9]*/ {
     sigindex = index($0, "SIG")
     sigtail = substr($0, sigindex, 80)
     split(sigtail, tmp)


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2004-03-11 17:54 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-11 17:53 PATCH: build problem with signals on HP/UX,ia64 Oliver Kiddle

Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).