On 18 Sep 2002, Miles Lane wrote:
> Since I am building on a PowerPC machine, yes, I don't have
> vm86.h in my path, if that is what you are asking. I only
> see vm86 files in the /usr/src/linux/arch/[i386|mips] trees.
>
> It does seem odd that some x86 driver would be getting
> compiled on my
Well, according for Linux:
DESCRIPTION
The system call vm86 was introduced in Linux 0.97p2. In
Linux 2.1.15 and 2.0.28 it was renamed to vm86old, and a
new vm86 was introduced. The definition of `struct
vm86_struct' was changed in 1.1.8 and 1.1.9.
It's de
Since I am building on a PowerPC machine, yes, I don't have
vm86.h in my path, if that is what you are asking. I only
see vm86 files in the /usr/src/linux/arch/[i386|mips] trees.
It does seem odd that some x86 driver would be getting
compiled on my PPC build.
Miles
On Tue, 2002-09-17
Were you also missing vm86 too? =)
On September 17, 2002 07:21 pm, Miles Lane wrote:
> Any idea how I can fix this?
>
> make[5]: *** No rule to make target `xf86noBus.o', needed by
> `libxf86.a'. Stop.make[5]: Leaving directory
> `/usr/src/xc/programs/Xserver/hw/xfree86/common'
>
> Linux firehos
On Tue, 17 Sep 2002, Miles Lane wrote:
> Any idea how I can fix this?
> make[5]: *** No rule to make target `xf86noBus.o', needed by
> `libxf86.a'. Stop.make[5]: Leaving directory
> `/usr/src/xc/programs/Xserver/hw/xfree86/common'
The HEAD branch is currently unstable, and likely will be so fo
Any idea how I can fix this?
make[5]: *** No rule to make target `xf86noBus.o', needed by
`libxf86.a'. Stop.make[5]: Leaving directory
`/usr/src/xc/programs/Xserver/hw/xfree86/common'
Linux firehose 2.4.20-pre5-ben0 #12 Tue Sep 10 05:25:08 PDT 2002 ppc unknown
Gnu C 2.95.3
G
