Very Computer

cc -Iinclude -D__KERNEL__=1 -I../include -Wall -Wstrict-prototypes -O2 \
-fomit-frame-pointer -m486 -DSOCKSYS_MAJOR=30 -DIBCS_TRACE -DVERBOSE_ERRORS \
-DCOFF_TRACE -DEMU_BSD -c vtkd.c

In file included from vtkd.c:32:
include/ibcs/ibcs.h:32: warning: function declaration isn't a prototype
vtkd.c:39: `KDDISPTYPE' undeclared here (not in a function)
vtkd.c:39: initializer element for `trantab.out_ioctl' is not constant
vtkd.c:51: `KIOCINFO' undeclared here (not in a function)
vtkd.c:51: initializer element for `trantab.out_ioctl' is not constant
make: *** [vtkd.o] Error 1

Note: I am running 1.1.64.

I have seen a message on the net stating that one could simply define
these missing "defines", and another message stated that this would
cause a memory leak.

So, how should I fix this. I would really like to demo WP6.0 working
to show my boss, so I could order several copies before the end of
the year. (We have some money to spend!)

Thanks in advance,

George Erhart

: I finally managed to get the WP6.0 statically linked demo, thanks to
: Jeff Uphoff and his 1MB per chunk version of the tar file. Anyway,
: I fetched the current copy of iBCS from tsx-11.mit.edu, /pub/linux/ALPHA
: and put the code in my /usr/linux/ibcs directory. The compile fails
: with the following error message:

: vtkd.c:39: `KDDISPTYPE' undeclared here (not in a function)
: vtkd.c:51: `KIOCINFO' undeclared here (not in a function)

: Note: I am running 1.1.64.

: I have seen a message on the net stating that one could simply define
: these missing "defines", and another message stated that this would
: cause a memory leak.

This latter message was just plain ridiculous.

: Comment (or, better, ifdef) out the lines in ibcs/vtkd.c which have the
: symbols in question.  They were apparently removed in 1.1.63.

        Unfortunately, this doesn't do the trick.  Sure, iBCS compiles fine,
but when I try to run the WP60 Demo.. bye bye memory.  (And then eventually...
CRASH).

        Is anyone working on this?  I hope?  I'd be happy to use a slightly
older kernel, but, 1.1.64 doesn't crash the way the older ones did when I ran
CSLIP.  I'm kind of in a bind here.. do I stick with the kernel that can run
the iBCS... or stick with the one that does the networking better..

        Help?

                                                Jason

--
Jason Van Patten                  | If at first you don't succeed, keep |
Clarkson University               | on sucking till you do succeed.     |

                                  |                 (The Three Stooges) |
            ** Any opinions expressed here are actually
               yours, you just don't know it, yet. **

: In file included from vtkd.c:32:
: include/ibcs/ibcs.h:32: warning: function declaration isn't a prototype
: vtkd.c:39: `KDDISPTYPE' undeclared here (not in a function)
: vtkd.c:39: initializer element for `trantab.out_ioctl' is not constant
: vtkd.c:51: `KIOCINFO' undeclared here (not in a function)
: vtkd.c:51: initializer element for `trantab.out_ioctl' is not constant
: make: *** [vtkd.o] Error 1

: Note: I am running 1.1.64.

: So, how should I fix this. I would really like to demo WP6.0 working

Comment out the lines 38 and 51.  Go back to 1.1.63 or else the xwp version
will seg fault, and upon recompiling it will run ok.  Well, I say this based
on my 5.1 seg faulting under x windows using 1.1.64, maybe 6.0 doesn't.

--

: : Comment (or, better, ifdef) out the lines in ibcs/vtkd.c which have the
: : symbols in question.  They were apparently removed in 1.1.63.

:       Unfortunately, this doesn't do the trick.  Sure, iBCS compiles fine,
: but when I try to run the WP60 Demo.. bye bye memory.  (And then eventually...
: CRASH).

:       Is anyone working on this?  I hope?  I'd be happy to use a slightly
: older kernel, but, 1.1.64 doesn't crash the way the older ones did when I ran
: CSLIP.  I'm kind of in a bind here.. do I stick with the kernel that can run
: the iBCS... or stick with the one that does the networking better..

:       Help?

:                                               Jason

Get the help from that guy who said that report about memory leak is
"plain ridiculous." He knows, he is smart..

-PP

: --
: Jason Van Patten                | If at first you don't succeed, keep |
: Clarkson University             | on sucking till you do succeed.     |

:                                 |                 (The Three Stooges) |
:           ** Any opinions expressed here are actually
:              yours, you just don't know it, yet. **
:  

: Get the help from that guy who said that report about memory leak is
: "plain ridiculous." He knows, he is smart..

Plainly ridiculous was the claim that a memory leak is caused
by randomly defining, or ifdeffing, or deleting KDDISPTYPE etc.

Quote:>:   Unfortunately, this doesn't do the trick.  Sure, iBCS compiles fine,
>: but when I try to run the WP60 Demo.. bye bye memory.  (And then eventually...
>: CRASH).

Karl

-------------------------------------------------------------------------
Vitrociset S.p.A.                               Tel   : +(49) 6151 902041
European Space Agency                           Fax   : +(49) 6151 904041