[OpenAFS] Still Compiling on FC6T2 (try again)
chas williams - CONTRACTOR
Fri, 18 Aug 2006 11:44:32 -0400
apply this. i was thinking about making the whole mutex api generic
which would tend to solve this problem. something like osi_mutex_t,
osi_mutex_lock(), osi_mutex_unlock() which each arch would need to
define (this is already done in rx so it would just get moved to the
the afs side).
RCS file: /cvs/openafs/src/afs/LINUX/osi_pag_module.c,v
retrieving revision 18.104.22.168
diff -u -u -r22.214.171.124 osi_pag_module.c
--- src/afs/LINUX/osi_pag_module.c 13 Aug 2006 04:53:27 -0000 126.96.36.199
+++ src/afs/LINUX/osi_pag_module.c 18 Aug 2006 15:42:50 -0000
@@ -55,8 +55,12 @@
MODULE_PARM_DESC(this_cell, "Local cell name");
struct proc_dir_entry *openafs_procfs;
+#if LINUX_VERSION_CODE >= KERNEL_VERSION(2,6,16)
+#elif LINUX_VERSION_CODE >= KERNEL_VERSION(2,4,0)
struct semaphore afs_global_lock = MUTEX;
In message <1155915200.3004.19.camel@BillMurray>,William Murray writes:
> OK, 1.5.7 does get further.
>odule.c:58: error: conflicting types for 'afs_global_lock'
>previous declaration of 'afs_global_lock' was here
>Does anyone know which is a better bet?
>On Fri, 2006-08-18 at 16:00 +0200, Stephan Wiesand wrote:
>> On Fri, 18 Aug 2006, Derrick J Brashear wrote:
>> > The CVS head probably still isn't what you want. 1.5.7 is a few hours old.
>> > Try it.
>> Maybe more people would if someone released the volume ;-)
>> > Derrick
>> > On Fri, 18 Aug 2006, William John Murray wrote:
>> >> Hi guys,
>> >> I watched all the discussion about FC6T2 at the weekend,
>> >> but it did not seem to apply to me yet. I am stuck (with the latest CVS)
>> >> at:
>> >> /usr/local/src/openafs-snap-2006-08-14/src/libafs/MODLOAD-2.6.17-1.2564.f
>> >> error: implicit declaration of function IN6_IS_ADDR_V4COMPAT
>> >> I don't understand where the in3t6 definitions are supposed to come from:
>> >> there
>> >> arer no results for
>> >> find /usr -name inet\*
>> >> or
>> >> find /usr -name netinet\*
>> >> on my system.
>> >> Does anyone know what happened here?
>> >> Thanks,
>> >> Bill
>> >> _______________________________________________
>> >> OpenAFS-info mailing list
>> >> OpenAFSemail@example.com
>> >> https://lists.openafs.org/mailman/listinfo/openafs-info
>> > _______________________________________________
>> > OpenAFS-info mailing list
>> > OpenAFSfirstname.lastname@example.org
>> > https://lists.openafs.org/mailman/listinfo/openafs-info
>OpenAFS-info mailing list