In article <20031103160729.GS2865021@MrPomeroy2>
jkunz@unixag-kl.fh-kl.de wrote:

> This is for sure incorrect. I am very aware that this is an evil hack
> and I expected that this breaks other things. It cured the symptom, not
> the disease. I should have made this more clear in my mail. I was not
> able to find the real problem as I don't have such a deep in-detail
> knowledge of kernel internas and I didn't had the time to investigate
> all this in the mean time.

Well, I think I couldn't find the problem without your investigation,
and I still appreciate your work. :-)

Anyway, it seems -current kernel still has some problems.
Some binaries on sd don't work, or get ramdom hangs.
I also newer binaries built from -current source tree
(with attached patch), but even /sbin/init doesn't work
and it can't reach single user.
---
Izumi Tsutsui
tsutsui@ceres.dti.ne.jp

Index: libexec/ld.elf_so/arch/hppa/Makefile.inc
===================================================================
RCS file: /cvsroot/src/libexec/ld.elf_so/arch/hppa/Makefile.inc,v
retrieving revision 1.2
diff -u -r1.2 Makefile.inc
--- libexec/ld.elf_so/arch/hppa/Makefile.inc	24 Sep 2002 12:12:08 -0000	1.2
+++ libexec/ld.elf_so/arch/hppa/Makefile.inc	4 Nov 2003 11:59:18 -0000
@@ -14,4 +14,4 @@
 LDFLAGS+= --script ${.CURDIR}/arch/hppa/ld.so.script
 
 # XXX fredette - the libgcc millicode is needed here:
-LDADD=`$(CC) -print-libgcc-file-name`
+LDADD=-lgcc_pic
Index: share/mk/bsd.lib.mk
===================================================================
RCS file: /cvsroot/src/share/mk/bsd.lib.mk,v
retrieving revision 1.239
diff -u -r1.239 bsd.lib.mk
--- share/mk/bsd.lib.mk	26 Oct 2003 03:29:44 -0000	1.239
+++ share/mk/bsd.lib.mk	4 Nov 2003 11:59:19 -0000
@@ -134,7 +134,7 @@
 APICFLAGS?= -k
 # XXX libraries often need the millicode functions in libgcc.a,
 # so we have to work around the -nostdlib:
-LDADD+= `${CC} -print-libgcc-file-name`
+#LDADD+= -L${_GCC_LIBGCCDIR} -lgcc_pic
 
 .else