On 2011-06-12 21:27, Kirk McKusick wrote:
Author: mckusick
Date: Sun Jun 12 19:27:05 2011
New Revision: 223020
URL: http://svn.freebsd.org/changeset/base/223020
...
Modified: head/sys/ufs/ffs/ffs_extern.h
==============================================================================
--- head/sys/ufs/ffs/ffs_extern.h       Sun Jun 12 18:52:39 2011        
(r223019)
+++ head/sys/ufs/ffs/ffs_extern.h       Sun Jun 12 19:27:05 2011        
(r223020)
...
@@ -161,4 +166,14 @@ void       softdep_journal_fsync(struct inode

  int   ffs_rdonly(struct inode *);

+TAILQ_HEAD(snaphead, inode);
+
+struct snapdata {
+       LIST_ENTRY(snapdata) sn_link;
+       struct snaphead sn_head;
+       daddr_t sn_listsize;
+       daddr_t *sn_blklist;
+       struct lock sn_lock;
+};
+
  #endif /* !_UFS_FFS_EXTERN_H */

This addition breaks world compilation in usr.sbin/makefs, apparently
because the TAILQ_HEAD macro isn't defined at that point:

...
cc -O2 -pipe  -I/usr/src/usr.sbin/makefs 
-I/usr/src/usr.sbin/makefs/../../sys/fs/cd9660/ 
-I/usr/src/usr.sbin/makefs/../../sys/ufs/ffs -I/usr/src/usr.sbin/makefs/compat 
-DHAVE_STRUCT_STAT_ST_FLAGS=1 -DHAVE_STRUCT_STAT_ST_GEN=1 
-I/usr/src/usr.sbin/makefs/../mtree -std=gnu99 -fstack-protector 
-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized 
-Wno-pointer-sign -c /usr/src/usr.sbin/makefs/ffs/ffs_bswap.c
cc1: warnings being treated as errors
In file included from /usr/src/usr.sbin/makefs/ffs/ffs_bswap.c:51:
/usr/obj/usr/src/tmp/usr/include/ufs/ffs/ffs_extern.h:169: warning: data 
definition has no type or storage class
/usr/obj/usr/src/tmp/usr/include/ufs/ffs/ffs_extern.h:169: warning: parameter 
names (without types) in function declaration
/usr/obj/usr/src/tmp/usr/include/ufs/ffs/ffs_extern.h:172: error: expected 
specifier-qualifier-list before 'LIST_ENTRY'
*** Error code 1

Stop in /usr/src/usr.sbin/makefs.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "[email protected]"

Reply via email to