|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Joseph W. Shaw II (mrman
darkside.org)Date: Mon Jun 03 2002 - 19:29:09 CDT
On Mon, 3 Jun 2002, Marc Espie wrote:
> > Cleaning of includes might explain why I had so much trouble yesterday
> > with mount_cd9660.c and others when trying to compile the ramdisk_cd
> > image. I noticved in CVSweb that export had been expanded to export_info
> > in the various chunks of mount code, but had not been changed in
> > /usr/include/sys/mount.h which caused this:
> >
> > cc -O2 -I/usr/src/sbin/mount_ext2fs/../mount -c mount_ext2fs.c
> > mount_ext2fs.c: In function `main':
> > mount_ext2fs.c:101: structure has no member named `export_info'
> > mount_ext2fs.c:103: structure has no member named `export_info'
> > mount_ext2fs.c:105: structure has no member named `export_info'
> > *** Error code 1
>
> Bzzzt ! learn how to rebuild your system. mount.h lives in
> /usr/src/sys/sys, is installed by make include, and is just fine.
I guess I was at a loss to understand how an include file dated from March
and a chunk of source dated from April, both from 3.1-Release, would have
problems. I can only assume it is attributable to the source being frozen
for the 3.1 release. Either way, I have a better understanding now than I
did yesterday.
Regards,
-- Joseph
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]