Subject: Re: to 2.4 tree or not to 2.4 tree
From: Patrick Callahan (pac1@tiac.net)
Date: Mon Jul 30 2001 - 21:03:43 MDT
On Monday 30 July 2001 10:11, you wrote:
> Anyone got an easy answer to not compiling S3triofb.c?
Found it.
As I read over my message after sending it. It occurred to me that all I had
to do was navigate down the menuconfig tree looking for S3trio video driver.
There it was. I turned it off and a few other drivers I don't need and
proceeded to the next step: $ make modules
No need to touch the Makefile. (What a silly idea!)
The next questions:
I've turned off a few things I am pretty sure I don't need, such as drivers
for chips on other machines.
What happens if I'm wrong about something I've turned off in menuconfig?
How do I determine easily what I can or can't turn off in menuconfig?
Oh bother! make modules just failed with the error: Now I suppose I'll have
to run make menuconfig again and find ntfs and shut if off. (I probably
don't need a Windows NT file system.) this is exactly what I'm asking. How
do I figure this out up front? Or do we keep trying stuff till it breaks and
then fix it?
make[2]: Entering directory `/usr/src/linux-2.4/fs/ntfs'
gcc -D__KERNEL__ -I/usr/src/linux-2.4/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-D__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2 -Wno-uninitialized
-mmultiple -mstring -DMODULE -DNTFS_VERSION=\"1.1.15\" -c -o fs.o fs.c
In file included from fs.c:17:
util.h:22: `$' in identifier
<snip>
fs.c: In function `ntfs_read_inode':
fs.c:650: `$' in identifier
<snip>
fs.c: In function `_ntfs_clear_inode':
fs.c:796: `$' in identifier
<snip>
fs.c: In function `ntfs_statfs':
fs.c:886: `$' in identifier
fs.c: In function `ntfs_read_super':
fs.c:1077: `$' in identifier
make[2]: *** [fs.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.4/fs/ntfs'
make[1]: *** [_modsubdir_ntfs] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4/fs'
make: *** [_mod_fs] Error 2
-pat
>
> -Pat
>
>
> gcc -D__KERNEL__ -I/usr/src/linux-2.4/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
> -D__powerpc__ -fsigned-char -msoft-float -pipe -ffixed-r2
> -Wno-uninitialized -mmultiple -mstring -c -o S3triofb.o S3triofb.c
> S3triofb.c:524: warning: #warning FIXME: always obey fb_var.accel_flags
> In file included from S3triofb.c:42:
> /usr/src/linux-2.4/include/asm/pci-bridge.h:24: warning: `struct pci_dev'
> declared inside parameter list
> /usr/src/linux-2.4/include/asm/pci-bridge.h:24: warning: its scope is only
> this
> definition or declaration, which is probably not what you want.
> /usr/src/linux-2.4/include/asm/pci-bridge.h:65: field `io_resource' has
> incomplete type
> /usr/src/linux-2.4/include/asm/pci-bridge.h:66: field `mem_resources' has
> incomplete type
> S3triofb.c: In function `s3trio_init':
> S3triofb.c:322: warning: implicit declaration of function `pci_device_loc'
> S3triofb.c: At top level:
> S3triofb.c:783: warning: `Trio_MoveCursor' defined but not used
> make[3]: *** [S3triofb.o] Error 1
> make[3]: Leaving directory `/usr/src/linux-2.4/drivers/video'
> make[2]: *** [first_rule] Error 2
> make[2]: Leaving directory `/usr/src/linux-2.4/drivers/video'
> make[1]: *** [_subdir_video] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.4/drivers'
> make: *** [_dir_drivers] Error 2
>
> On Tuesday 24 July 2001 04:13, you wrote:
> > on 24/7/01 1:55 am, Patrick Callahan at pac1@tiac.net wrote:
> > > Now what does one do first after downloading 22mb via 28,800 again?
> > >
> > > -pat on a Blue G3 rev1 no special hardware...
> >
> > You need to configure the kernel ...
> >
> > - cd to the kernel directory
> > - make menuconfig
> >
> > ... set configuration options. I don't know whether the kernel source
> > that ships with YDL is shipped preconfigured. If it is, you could:
> >
> > - start from the old kernel directory
> > - make menuconfig
> > - use the menuconfig option to save the kernel configuration to a file
> > - cd to the new kernel directory
> > - make menuconfig
> > - use the menuconfig option to load the kernel options you just saved
> >
> > There are some options that will be specific to your hardware, you just
> > need to work through them removing things that clearly aren't relevant
> > (eg SCSI support on a Mac with no SCSI etc.). Then:
> >
> > - make dep
> > - make
> > - make modules
> > - make modules_install (as root)
> >
> > ... and that should be your new kernel (vmlinux) and System.map
> >
> > Iain
This archive was generated by hypermail 2a24 : Mon Jul 30 2001 - 20:11:14 MDT