Re: [mobius-development] Cygwin + Mobius

[prakash s. <hel...@ho...>]

Hi Tim/Rahman/Others,
   I would like to know if the CVS is updated and if I can download the 
source code afresh. Do (all of you/atleast some of you) have a MSN or a 
Yahoo ID ? I think it would be a good idea to have each of us included in 
our Messengers since it would enable us to have closer interactions and also 
a better reachability.

My MSN ID is hel...@ho...

Thanking you
Prakash S


>From: "Tim Robinson" <tim...@ic...>
>To: <mob...@li...>
>Subject: Re: [mobius-development] Cygwin + Mobius
>Date: Sun, 21 Jul 2002 19:13:39 +0100
>
> > ../make.actions:27: dllmain.d: No such file or directory
> > ../make.actions:27: syscall.d: No such file or directory
>[...]
>
>Don't worry about these missing .d files; they get generated automatically
>as necessary.
>
> > make[1]: *** No rule to make target `/mn/lib/libc_s.lib', needed by
> > `/mn/bin/libsys.dll'.  Stop.
>[...]
>
>This is OK: libsys relies on libc, which hasn't been built at this point.
>However, the libsys.dll file isn't necessary to build libc. IIRC the main
>makefile builds libsys twice: before and after building libc.
>
> > ctype/towupper.c: In function `towupper':
> > ctype/towupper.c:14: syntax error before `*'
> > ctype/towupper.c:15: `wc' undeclared (first use in this function)
> > ctype/towupper.c:15: (Each undeclared identifier is reported only once
> > ctype/towupper.c:15: for each function it appears in.)
> > ctype/towupper.c:15: warning: implicit declaration of function
> > `__lookup_unicode'
> > make[1]: *** [ctype/towupper.o] Error 1
>[...]
>
>There's something wrong here which is interfering with the building of 
>libc.
>Looks like I committed towupper.c to the CVS without trying to rebuild it
>first.
>
> > nasm -M i386/bsp.asm > i386/bsp.d
> > nasm: not found
> > make[1]: *** [i386/bsp.d] Error 127
>[...]
>
>You seem to be missing NASM... I forgot to mention that you need NASM to
>build the kernel.
>
> > make[2]: *** No rule to make target `/mn/lib/kernel.lib', needed by
> > `/mn/bin/ata.drv'.  Stop.
>[...]
>
>Without building the kernel, you can't build any drivers, because they've
>got nothing to link to.
>
> > tty.c: In function `TtyRequest':
> > tty.c:577: structure has no member named `buffer'
> > tty.c: In function `TtyAddDevice':
> > tty.c:593: structure has no member named `request'
> > tty.c:594: structure has no member named `isr'
> > tty.c: In function `DrvInit':
> > tty.c:616: structure has no member named `request'
> > tty.c:617: structure has no member named `isr'
> > make[2]: *** [tty.o] Error 1
>[...]
>
>This looks like an out-of-date TTY driver in the CVS.
>
> > make[2]: *** No rule to make target `/mn/lib/tty.lib', needed by
> > `/mn/bin/keyboard.drv'.  Stop.
>[...]
>
>The keyboard driver relies on the TTY one.
>
> > shell.c: In function `ShNormalizePath':
> > shell.c:154: structure has no member named `standard_attributes'
> > shell.c: In function `ShCmdDir':
> > shell.c:207: warning: implicit declaration of function `FsOpenSearch'
> > shell.c:216: structure has no member named `standard_attributes'
> > shell.c:218: structure has no member named `standard_attributes'
> > shell.c:221: structure has no member named `length'
> > shell.c: In function `ShDumpFile':
> > shell.c:252: structure has no member named `length'
> > shell.c:254: structure has no member named `length'
> > shell.c:256: structure has no member named `length'
> > shell.c:262: structure has no member named `length'
> > shell.c:266: structure has no member named `length'
> > shell.c:281: structure has no member named `length'
> > shell.c:301: structure has no member named `length'
> > shell.c:307: structure has no member named `length'
> > shell.c: In function `ShCmdV86':
> > shell.c:610: structure has no member named `length'
> > shell.c:620: structure has no member named `length'
> > shell.c:626: structure has no member named `length'
> > make[1]: *** [shell.o] Error 1
>[...]
>
>Since I handed over shell development to Sam Rahman, I haven't been
>committing the latest shell sources.
>
> > mcopy.cmd -o menu.lst  c:\\
> > make[1]: mcopy.cmd: Command not found
> > make[1]: *** [all] Error 127
> > make[1]: Leaving directory `/mn/bin'
> > make: *** [all] Error 2
>
>I use mtools as part of my build process to ensure that the Bochs image is
>updated, although you can do this however you like.
>
>In summary:
>1) Someone (you or I -- my development machine doesn't have Internet access
>atm) needs to fix towupper.c.
>2) You need to install Nasm
>3) I need to make sure that the CVS version of the TTY driver is correct.
>4) Either I need to update the copy of the shell in the CVS, or Sam needs 
>to
>keep his version maintained. I suggest that I keep the original version
>up-to-date and that Sam forks it into a different directory and works on
>that one. Any shell development that I do will be orientated towards 
>testing
>rather than providing a nice command-line shell for users, so it would be
>best to keep a 'sanitised' copy which I don't hack on.
>
>
>
>-------------------------------------------------------
>This sf.net email is sponsored by:ThinkGeek
>Welcome to geek heaven.
>http://thinkgeek.com/sf
>_______________________________________________
>mobius-development mailing list
>mob...@li...
>https://lists.sourceforge.net/lists/listinfo/mobius-development





Luv
Prakash S

I care for those who care for me
                            - Prakash


_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com