Hi, > Two patches modifies a single file. > When aufs changes fileA and loop-aes changes fileB, there is no > conflict. Both of aufs and loop-aes change fileC, there is conflict in > fileC. In our case, fileC is loop.h, which defines "struct loop". > > If aufs3-loopback.patch is unnecessary for you, then you can stop > applying it and the confliction will be gone.
Ok thanks, that's what I did in the previous step (not applying aufs3-loopback.patch), but it still BUGs. However I compile loop-aes AFTER aufs, so maybe aufs is compiled against a wrong header (because it's modified later on by loop-aes!). Is it a possibility? Regards, François. ------------------------------------------------------------------------------ WatchGuard Dimension instantly turns raw network data into actionable security intelligence. It gives you real-time visual feedback on key security issues and trends. Skip the complicated setup - simply import a virtual appliance and go from zero to informed in seconds. http://pubads.g.doubleclick.net/gampad/clk?id=123612991&iu=/4140/ostg.clktrk
