From: Don M. <dlm...@us...> - 2001-06-22 13:14:59
|
Darn!!!!! I knew it. I knew it couldn't be that easy. No ... I did not. -Don Kevin M Corry/Austin/IBM@IB...@li... on 06/22/2001 01:22:59 PM Sent by: evm...@li... To: evm...@li... cc: Subject: Re: [Evms-devel] Changes to DLIST plugin IDs Have you checked out and installed the new version of dlist? Steve made a change to the definition of DLIST which might make debugging a bit easier. However, that new definition is causing lots of new warnings. -Kevin To: evm...@li... cc: Subject: [Evms-devel] Changes to DLIST plugin IDs FYI ... I just did a cvs checkout (linux,engine), rebuilt my 2.4.5 kernel and then rebuilt the engine code. I honestly didn't pay too much attention to the kernel build messages so I can only say that it runs. I did watch the engine code build and it went pretty clean ... a few warnings here and there. I kinda expected lotsa trouble after reading your note. Don Mulvey IBM Austin Linux Technology Center (512) 838-1787 To: evm...@li... cc: Subject: [Evms-devel] Changes to DLIST plugin IDs All, I have just moved a bunch of definitions from PluginIDs.h to evms_common.h As part of this many of the IDs changed in order to sync up the kernel code with the engine code. You will need to extract both files from CVS and rebuild both your kernel and engine. I have also changed the typedef of DLIST to be a MasterListRecord * . The effect of this change is 2 fold: 1st, debugging will be easier since gdb will recognize DLSTS, and second (and more importantly) the compiler will do better type checking on passing of DLISTS. Many of you will find LOTS of warning about passing *DLIST instead of just DLIST. This means your code is wrong and has been, please fix immediately. Steve _______________________________________________ Evms-devel mailing list Evm...@li... http://lists.sourceforge.net/lists/listinfo/evms-devel |