nanogui: Trouble building Microwindows for MIPS target
Subject:
Re: Trouble building Microwindows for MIPS target
From:
"John Waldron" ####@####.####
Date:
9 Feb 2001 22:39:55 -0000
Message-Id: <003301c092e9$987df240$6401a8c0@fletchii>
I can't imagine that floating point would have anything to do with it (but I
may be wrong). Are you building on the osprey board? There could be some
other enhancements in the new tools that would fix this, but it sounds like
a config issue. Are you sure all your enviroment vars point to the correct
places? Are you sure you are using the correct .config file in the uWin
make? I have had that cause some of the strangest, most difficult problems
to find )-:
John Waldron
----- Original Message -----
From: "Scott A McConnell" ####@####.####
To: "Greg Haerr" ####@####.####
Cc: ####@####.####
Sent: Friday, February 09, 2001 4:34 PM
Subject: Re: Trouble building Microwindows for MIPS target
> Greg Haerr wrote:
>
> > : scr_fb.c:14: warning: No include path in which to find linux/fb.h
> > : scr_fb.c:15: warning: No include path in which to find linux/kd.h
> > : scr_fb.c:16: warning: No include path in which to find linux/vt.h
> >
> > You're building for VxWorks, right? fb.h is the linux framebuffer
> > kernel interface file, VxWorks 'dont do dat'.
>
> No I am building with Monta Vista cross tools for 1.2. I have not
> upgraded to their latest tool chain that has floating point support.
> Maybe I should ?
>
> ftp://ftp.mvista.com/pub/CDK/1.2/cdimages/mips_fp_le_001214.cdimage
>
> $ find . -name fb.h
> ./hardhat/devkit/mips/5000_le/target/microwin/src/drivers/fb.h
> ./hardhat/devkit/lsp/mymips/linux/include/linux/fb.h
> ./hardhat/devkit/lsp/mymips/linux/include/config/fb.h
> ./hardhat/devkit/kernel/linux-2.4.0-test2/include/linux/fb.h
>
> So I have all the files...
>
> I just can't seem to find them or at least the right ones.
>
> Scott
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>
