On Wednesday 27 September 2006 16:20, Hugo Vanwoerkom wrote:
> David Baron wrote:
> > Manually putting in the symlink worked. 2.6.18 is up and running.
> > Easily build the kqemu and, using m-a all the other added kernel models.
> > And yes, Nvidia's installer CAN be easily used with multiple kerne
David Baron wrote:
Manually putting in the symlink worked. 2.6.18 is up and running.
Easily build the kqemu and, using m-a all the other added kernel models.
And yes, Nvidia's installer CAN be easily used with multiple kernels and even
cross-compile (read their "advanced" options).
I'll keep 2
Manually putting in the symlink worked. 2.6.18 is up and running.
Easily build the kqemu and, using m-a all the other added kernel models.
And yes, Nvidia's installer CAN be easily used with multiple kernels and even
cross-compile (read their "advanced" options).
I'll keep 2.6.17 around for a few
David Baron wrote, On 2006-09-26 23:42:
On Tuesday 26 September 2006 02:54, Arthur Marsh wrote:
Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
David Baron wrote:
I recall others have had a problem with this as well. Looks for the
asm/socket.h file.
This is very often a problem on a clean(ed) bui
On Tuesday 26 September 2006 17:47, Arthur Marsh wrote:
> David Baron wrote, On 2006-09-26 23:42:
> > On Tuesday 26 September 2006 02:54, Arthur Marsh wrote:
> >> Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
> >>> David Baron wrote:
> I recall others have had a problem with this as well. Looks
On Tuesday 26 September 2006 02:54, Arthur Marsh wrote:
> Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
> > David Baron wrote:
> >> I recall others have had a problem with this as well. Looks for the
> >> asm/socket.h file.
> >>
> >> This is very often a problem on a clean(ed) build, usually solved b
Hugo Vanwoerkom wrote, On 2006-09-26 03:49:
David Baron wrote:
I recall others have had a problem with this as well. Looks for the
asm/socket.h file.
This is very often a problem on a clean(ed) build, usually solved by
running a make until c files are actually being compiled and then
stoppin
David Baron wrote:
I recall others have had a problem with this as well. Looks for the
asm/socket.h file.
This is very often a problem on a clean(ed) build, usually solved by running a
make until c files are actually being compiled and then stopping it. Then one
could go on with whatever make
I recall others have had a problem with this as well. Looks for the
asm/socket.h file.
This is very often a problem on a clean(ed) build, usually solved by running a
make until c files are actually being compiled and then stopping it. Then one
could go on with whatever makekpkg one was doing.
9 matches
Mail list logo