On Wed, Jul 19, 2017 at 9:26 AM, Christopher Li <sparse@xxxxxxxxxxx> wrote: > I have revert the change cause this problem on sparse-next. > > Wine compile should be able to complete now. Yes, I have single CPU build the wine package to a complete. The test sparse is on the sparse-next branch. cgcc -o wineserver async.o atom.o change.o class.o clipboard.o completion.o console.o debugger.o device.o \ directory.o event.o fd.o file.o handle.o hook.o mach.o mailslot.o main.o mapping.o mutex.o \ named_pipe.o object.o process.o procfs.o ptrace.o queue.o region.o registry.o request.o \ semaphore.o serial.o signal.o snapshot.o sock.o symlink.o thread.o timer.o token.o trace.o \ unicode.o user.o window.o winstation.o -Wl,--rpath,\$ORIGIN/../libs/wine \ ../libs/port/libwine_port.a -lwine -L../libs/wine make[1]: Leaving directory '/home/xxx/git/oss/wine/server' Wine build complete. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
