Kernel 2.6.0 - build using O= gives permissions error during compile - Questions
This is a discussion on Kernel 2.6.0 - build using O= gives permissions error during compile - Questions ; I am building a kernel 2.6.0.
The kernel source is in a read only directory
/u1/dev01/kernel/linux-2.6.0
The build directory is /u1/build/kernel
Using:
make O=/u1/build/kernel bzImage
The compile runs for about 20 minutes, then stops during build of the
AGP drivers:
...
-
Kernel 2.6.0 - build using O= gives permissions error during compile
I am building a kernel 2.6.0.
The kernel source is in a read only directory
/u1/dev01/kernel/linux-2.6.0
The build directory is /u1/build/kernel
Using:
make O=/u1/build/kernel bzImage
The compile runs for about 20 minutes, then stops during build of the
AGP drivers:
CC drivers/char/agp/isoch.o
gcc: /u1/dev01/kernel/linux-2.6.0/drivers/char/agp/isoch.c: Permission
denied
gcc: No input files
make[4]: *** [drivers/char/agp/isoch.o] Error 1
make[3]: *** [drivers/char/agp] Error 2
make[2]: *** [drivers/char] Error 2
make[1]: *** [drivers] Error 2
make: *** [bzImage] Error 2
Is there a fix for this ?
Thanks in advance to anyone who can help.
-
Re: Kernel 2.6.0 - build using O= gives permissions error during compile
Mark Hobley wrote:
> I am building a kernel 2.6.0.
>
> The kernel source is in a read only directory
>
> /u1/dev01/kernel/linux-2.6.0
>
> The build directory is /u1/build/kernel
>
> Using:
>
> make O=/u1/build/kernel bzImage
>
> The compile runs for about 20 minutes, then stops during build of the
> AGP drivers:
>
> CC drivers/char/agp/isoch.o
> gcc: /u1/dev01/kernel/linux-2.6.0/drivers/char/agp/isoch.c: Permission
> denied
try chmod'ing the file isoch.c so that you have Read access to it, and
ensuring that you have eXecute access to all the directories above it
(/u1/dev01/kernel/linux-2.6.0/drivers/char/agp).
-
Re: Kernel 2.6.0 - build using O= gives permissions error during compile
On Sun, 04 Jan 2004 12:26:52 GMT, Robert Newson
wrote:
Duhh !!! What a donkey ! I should have looked !
The file in question actually did not have read permission.
All the other files do.
This one must have the incorrect attribute in the source tarball.
I've used chmod and I'm recompiling.
Cheers.
