search for: notify_msg

On Mon, 2018-06-18 at 10:35 -0400, pisymbol via samba wrote: > Small addendum, I did try: > > ./configure --nonshared-binary=ALL > > ERROR: source source3/smbd/notify_msg.c is in more than one subsystem of > target 'smbstatus': ['smbd_base.objlist', 'smbstatus.objlist'] > > This is CentOS 7.5. > > -aps Building more than smbd and smbtorture nonshared is simply not tested. The configure incantation for those is --nonshared-...

I have Googled around looking for the magic configure to waf incantation to get this accomplished but nothing seems to work. Does anyone know how to build rpcclient statically linked? Or all binaries statically linked? Thanks! -aps

Hi Team, While building smbd and smbstatus statically I am getting below error (using make). *ERROR: source source3/smbd/notify_msg.c is in more than one subsystem of target 'smbstatus': ['smbd_base.objlist', 'smbstatus.objlist']* *Environment Details:* Machine: Ubuntu 18.04 Samba Version: 4.11.6 *My Makefile excerpt:* ./configure --with-logfilebase=/var/log \ --disable-rpath --prefix=/opt/r1soft/r1sa...

On Mon, Jun 18, 2018 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > On Mon, 2018-06-18 at 10:35 -0400, pisymbol via samba wrote: > > Small addendum, I did try: > > > > ./configure --nonshared-binary=ALL > > > > ERROR: source source3/smbd/notify_msg.c is in more than one subsystem of > > target 'smbstatus': ['smbd_base.objlist', 'smbstatus.objlist'] > > > > This is CentOS 7.5. > > > > -aps > > Building more than smbd and smbtorture nonshared is simply not tested. > > The configu...

...:39 PM, Andrew Bartlett <abartlet at samba.org> > wrote: > >> On Mon, 2018-06-18 at 10:35 -0400, pisymbol via samba wrote: >> > Small addendum, I did try: >> > >> > ./configure --nonshared-binary=ALL >> > >> > ERROR: source source3/smbd/notify_msg.c is in more than one subsystem of >> > target 'smbstatus': ['smbd_base.objlist', 'smbstatus.objlist'] >> > >> > This is CentOS 7.5. >> > >> > -aps >> >> Building more than smbd and smbtorture nonshared is simply not t...

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with

* * * This series of VMCI linux upstreaming patches include latest udpate from VMware. -split guest, host and core driver code into different files -use EXPORT_SYMBOLS_GPL -remove vmci_device_get and vmci_device_release APIs -simplify the event deliver mechanism -driver ioctl code cleanup -sparse clean * * * In an effort to improve the out-of-the-box experience with