similar to: Cross-compiling 4.3.2 for Intel/PowerPC causes Python errors

What is the status of cross compiling samba 4.1.0 with the new waf configure. We don't have a native compiler or emulator to use. We used autoconf in 3.6.5 and earlier, which worked successfully. We are in need of smbclient, which supports SMB2 (and maybe SMB3?) right away, so we need to resolve this issue. Thanks, Mike Tompkins

(This is the Team's agreed statement explaining the role of the two build systems in Samba 4.0. Please, if you have can't use the waf build system, and so need the autoconf system for 4.0, reply and let us know your reasons and needs here or in the specific threads I'm raising on samba-technical). Thanks, Andrew Bartlett BUILDING SAMBA 4.0 (which build system to use and why)

Hi all, I'm just curios and would like some input from the community on this one. We're busy budgeting for a couple of new servers and I thought it would be good to try out the Core i7 CPU's, but see the majority of them don't offer VT-d, but just VT-x. Looking at the LGA1366 range, only the "Intel lga1366 i7 980XE" (from the list of what our suppliers stock) have VT-d,

Hi All, Are there any good, up-to-date hints out there for cross compiling Samba4 for Arm? I've looked at http://wiki.samba.org/index.php/Waf#cross-compiling but the info is a little dated it appears. I'm looking to build for the dreamplug and based on the info on the wiki I've installed qemu and an arm toolchain but 'cross-execute' appears to be ignored. At least

Sorry about the lack of info. So in the wireshark trace, our printer smbclient 4.0.7 sends a Unicode value in Russian of ???? with a password of ????123. The server rejects the login attempt with STATUS_LOGON_FAILURE. The second attempt is with the linux version smbclient 4.0.7, and the same credentials to the same server work. The only thing I see different in the requests are the flags sent:

I am unable to compile Samba 4.4.7, 4.5.1 or 4.5.3 on Solaris 11. I had been able in the past so maybe an update to GCC broke something. GCC 4.8 is the default. I then installed GCC 4.9. /usr/bin/gcc is a symlink to /usr/gcc/4.9/bin/gcc. I compiled the latest openldap (client only) to the samba target directory. Set environmental variables so the krb5.h and openldap would be found.

I'm checking back in to see if samba is FIPS compliant, as in using FIPS compliant algorithms ? Can it be built with openssl, which is FIPS compliant ? We're currently running 4.7.5. Please let me know. Regards, Mike

This issue is reproducible for this customer and a couple of others. We execute the smbclient command the same way for each instance. The null user name is valid syntax sent from the smbclient. When we send the command " smbclient -c 'cd <dir>; ls' ", samba code executes starting with Negotiate Protocol Request, and onward. I'm guessing this could be a DFS issue, but

"Tompkins, Michael via samba" <samba at lists.samba.org> writes: > I'm wondering if anyone else has any feedback on this or needs anymore info ? Can you provide the output of the failing command with full debug messages (-d10)? -- Aurélien Aptel / SUSE Labs Samba Team GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3 SUSE Linux GmbH, Maxfeldstraße 5, 90409 Nürnberg,

We are running Samba-4.6.6 and are running into an issue where it negotiates to a NetApp server but then the client stops the connection. 8262 2017-10-12 09:32:16.198917 10.136.78.14 10.128.101.128 TCP 66 45848 → 445 [FIN, ACK] Seq=403 Ack=581 Win=16768 Len=0 TSval=11546007 TSecr=3316317046 This is at a customer site, and we cannot recreate it here due to

Hi, I'm trying to build Samba from source on a RHEL version 8 server. I installed all the necessary packages and untarred the source for Samba version 4.6.10. In the past I have been able to successfully build and install Samba version 4.13.17 on a RHEL version 7 server with Python2. Here I believe I am using Python3, but I cannot seem to get past the configure command: [root at v2ecsqapp09

I would like to gain some idea of the XCP impact of these two CPU versions: Intel Core i7-2600, 3.4 GHz Core i7-2600K, 3.5 GHz Both have VT-x Differences 2600K does not include: Embedded Opions Available vPro Technology Virtualization Technology for Directed I/O Trusted Execution Technology Is the difference critical? Thanks, ray

On Tue, 31 Oct 2017 16:06:13 +0000 "Tompkins, Michael via samba" <samba at lists.samba.org> wrote: > Re-sending ... We tend to see a lot of issues with NetApp servers and > SMB 311. Not sure what might be wrong with their response packet, > that 4.6.6 doesn't like. > > ~ Mike > > > -----Original Message----- > From: samba [mailto:samba-bounces at

Thanks for the quick reply Jeremy. We have other FIPS compliant libraries, which check for, and ensure the proper FIPS compliant algorithms are used. Is there a link option to specify this kind of library ? ~ Mike -----Original Message----- From: Jeremy Allison <jra at samba.org> Sent: Tuesday, October 2, 2018 2:08 PM To: Tompkins, Michael <Michael.Tompkins at xerox.com> Cc:

I don't think you are going to have much luck getting 4.17 working on CentOS 7. We recently moved from CentOS 7 (4.13) to Rocky Linux 8 (4.16) and the install process was much easier. On Wed, Jan 18, 2023 at 12:03 PM Greg Dickie via samba < samba at lists.samba.org> wrote: > Ok now, but did 4.10.16? I was just trying to rebuild their source RPM. > > Trying 4.17 on the command

Ok now, but did 4.10.16? I was just trying to rebuild their source RPM. Trying 4.17 on the command line (with python3) gives me: > [root at srvlxfs2 samba-4.17.4]# ./configure > Setting top to : > /root/rpmbuild/BUILD/samba-4.17.4 > Setting out to : > /root/rpmbuild/BUILD/samba-4.17.4/bin > Checking for 'gcc' (C

> Am 11.05.2017 um 16:29 schrieb Leon Fauster <leonfauster at googlemail.com>: > >> Am 11.05.2017 um 14:48 schrieb Leon Fauster <leonfauster at googlemail.com>: >> >> https://access.redhat.com/support/policy/intel >> >> shows mainly Xeon CPUs. What about >> >> Intel Core i7-6700 Quad-Core Skylake >> >> has the current EL6

​No, sorry, it's actually failing on "configure" which this script calls. I should have been more clear. ./configured is failing at step: ​*Checking uname sysname type* It's obviously missing some app/header/library, but reading through all the breakpoints listed in the error (re-pasted below) I can't make out from the code what it's looking for, and the config.log

I am trying to build Samba 4.6.4 on an ARM 7 Cortex based router (Netgear R8000), running *DD-WRT v3.0-r31980M kongac (05/11/17)* I'm working with some folks via the DDWRT, but we're running into an issue trying to build from source. I have python 2.7 already installed on the router, and I'm executing the install_with_python.sh script. ./install_with_python.sh /opt/test/samba-4.6.4

https://access.redhat.com/support/policy/intel shows mainly Xeon CPUs. What about Intel Core i7-6700 Quad-Core Skylake has the current EL6 variant support for it? Any experience? Feedback would be greatly appreciated. Thanks, LF