On Fri, 15 Oct 1999, Dave Borja wrote:
> I agree, the intel site is wrong on how to set the prefix
> when making glibc. I had the same problem with the compiler
> but it went away when I set --prefix=/usr/local/arm/arm-linux
> (/usr/ocal/arm is where I put all the arm cross development
> stuff)....
Thanks Dave! That did the trick! It compiled my hello world program.
I'll inform Intel of the mistake in the documentation (unless it's
already been done?).
Now how does one add framebuffer support to Brutus? (do I do this when
compiling the 2.2.2 kernel with the patches or do I need to obtain another
patch/file?)
Thanks for the help!
Vasant.
>
>
> >>The only real difference between what I've done and what's on the Intel
> >>site as far as GNU packages is that I'm using EGCS 1.1.2 and the
> >>apropriate ARM patch from Phil. B as opposed to EGCS 1.1.1 and a patch.
> >
> >You should probably consider using gcc 2.95.1 now.
> >
> >>I followed Intel's directoy conventions to the letter (I changed nothing).
> >
> >I think Intel's instructions are wrong; this has been discussed here
> recently.
> >See the mailing list archives.
> >
> >>If I wanted the output "console" (Linux login, etc) to appear on the LCD
> >>would I have to write the LCD driver or is there something I can use to
> >>get basic text on the screen? Anything for the keyboard IC (USAR
> >>SPICoder)?
> >
> >I think there is a Brutus framebuffer driver now. Nico can probably give a
> >more definite answer.
> >
> >p.
> >
> >
> >unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
> >
>
> unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
>
unsubscribe: body of `unsubscribe linux-arm' to [EMAIL PROTECTED]
