Hello!
I have a recent current:
FreeBSD cichlids.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Tue Jan 11 13:18:21
CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/cichlids i386
I cannot build the CVS version of GNATS with this.
This is kinda strange, because with a kernel from Dec 18th I could do
this.
something must have changed.
Can one reproduce this, too? I can.
Please check out:
cvs "gnats" from :pserver:[EMAIL PROTECTED]:/cvs/gnats
type ./configure --with-full-gnats
(ignore the error for etc/ that stop the script
and then type "make"
I stop at:
[...]
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include strerror.c -o pic/strerror.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include strerror.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include strsignal.c -o pic/strsignal.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include strsignal.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include xatexit.c -o pic/xatexit.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xatexit.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include xexit.c -o pic/xexit.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xexit.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include xmalloc.c -o pic/xmalloc.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xmalloc.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include xstrdup.c -o pic/xstrdup.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xstrdup.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include xstrerror.c -o pic/xstrerror.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include xstrerror.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include basename.c -o pic/basename.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include basename.c
test x"no" != xyes || gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I.
-I./../include insque.c -o pic/insque.o
gcc -c -DHAVE_CONFIG_H -g -O2 -W -Wall -I. -I./../include insque.c
rm -f libiberty.a
ar rc libiberty.a argv.o choose-temp.o concat.o cplus-dem.o
fdmatch.o fnmatch.o getopt.o getopt1.o getruntime.o hex.o
floatformat.o objalloc.o obstack.o pexecute.o spaces.o splay-tree.o
strerror.o strsignal.o xatexit.o xexit.o xmalloc.o xstrdup.o
xstrerror.o basename.o insque.o
ranlib libiberty.a
now it just _hangs_.
I can now SIGINT it.
I can SIGINT a further call.
I can do nothing with a third call.
I EVEN cannot SIGKILL it!!
gdb tells me, that it stops at wait4().
Now it becomes strange.
I "cd" into the same dir, and now a "ls" hangs, too.
when I do a cd dir ; ls on 3 further consoles, the SYSTEM just hangs.
It _just_ hangs.
no error, it only hangs.
Please test, if this is the same case for you.
As said, this was not the case with a kernel from Dec. 18th, therefore
(same config-file) I'll not include the kernel-config here.
Alex
--
I doubt, therefore I might be.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message