similar to: SAMBA 2.0 Packaging request

Hello, rsync.h is always including the syslog.h file, even though it is only used when the LOG_DAEMON macro is defined. Could someone change it to be as follows: #ifdef LOG_DAEMON #include <syslog.h> #endif OpenVMS currently does not have a syslog facility, so it does not have a syslog.h. Thank you, -John wb8tyw@qsl.net Personal Opinion Only

Compaq C 6.5 OpenVMS Alpha 7.3 The config.h.in template file is missing the line: #undef HAVE_INET_NTOP This caused the resulting CONFIG.H on OpenVMS to not test for the existance of the inet_ntop() routine in it's system tables. This configure bug exposed that the prototype in inet_ntop() in RSYNC.H does not match the one in the Compaq C header files. This stopped the build. I am

Hi @ all, I have two samba-servers running perfectly! Now I configured a third machine which provides some backups. Since I brought it up in the network the windows client won't execute the netlogon-scripts... When I turn off samba-services on the backup-machine it works again. Did I miss something??? Maybe you can open my eyes... Best regards Sascha Here my conf-files: PDC

I am trying to debug the RSYNC client and server by single stepping through them. The server seems to ok up to the point where it is waiting for the client connection. On the client side, I am having trouble finding the right options so that it will connect up to the local server with out fork() a copy of itself or trying to exec the rsh command. This is on RSYNC 2.5.5 on OpenVMS Alpha. If

Refer to this: https://legacyos.org/vsi-introduces-new-samba-release/ I noticed that VSI, the new owners of VMS, have created a package for Samba4 under OpenVMS. I also notice the samba-vms list appears to be abandoned (for years). So, I apologize for posting here on the general list, but it seemed fruitless trying the dedicated list. I am under the impression that the GPL v3 compels all

I just installed Samba for VMS (1.9.17p4) on a DecServer 1000A running VMS 7.1 The University Network is primarily NT Server 4.0 SP5. My experience is with Netware and NT, not with VMS, but I have the luck of supporting the system..... My main question is about Encrypted Passwords.....Does this release of Samba support them, or do I have to modify the clients who want access to our Alpha to

> Qualities > > 1. Be reasonably portable: at least in principle, it should be > possible to port to Windows, OS X, and various Unixes without major > changes. In general, I would like to see OpenVMS in that list. > Principles > > 1. Clean design rather than micro-optimization. A clean design allows optimization to be done by the compiler, and tight optimization

I am still chasing this down, but in doing the build for OpenVMS, I have discovered that one of the popt modules is using HAVE_ALLOCA_H to determine if the alloca function is on a platform. That is not a good assumption. Compaq C does have an alloca() built in (slightly different symbol name, I assume because of symbol naming rules in the C standard.) Because alloca is a non-standard

The following popt files need patches in order to compile using Compaq C on OpenVMS. These patches should also be needed on a Tru64 or LINUX on ALPHA using Compaq C. Except for the alloca issue, these should work on any ANSI compliant compiler. Operating System: OpenVMS ALPHA V7.3 Compiler: Compaq C T6.5 Compiler switches: /WARN=ENABLE=(LEVEL4, QUESTCODE) SYSTEM.H is doing tests on

On Fri, 12 Jun 2020, Andrew Bartlett via samba wrote: > I can't find any evidence in the source code for new patches to have > Samba build on VMS Okay, well, at least I didn't just overlook something. > it certainly wasn't something we actively targeted when we moved from > autoconf to WAF with Samba 4.1. I'd be shocked if you did. Python 3.x isn't available on

Greetings, Beginning today, I started to receive the following when ftp'ing to my CentOS 6 machine: ncftp /home/pyz2 > dir connect failed: No route to host. connect failed: No route to host. connect failed: No route to host. Falling back to PORT instead of PASV mode. I can make a connection, but I can't get a directory listing or transfer data/files. I'm flummoxed. What I had

Hello, I'd like to introduce myself, my company, and our upcoming use of LLVM. My name is John Reagan. I've been working on compilers and assemblers since 1983 (yes, 31 years). Most of that time was spent on compilers for VAX/VMS (later renamed to OpenVMS), then OpenVMS on Alpha, and OpenVMS on Itanium. I've also worked with the HP NonStop platform and was directly involved

Hi all, I have two queries regarding WINE. 1) Is there support for VMS(OpenVMS) and MAC OS in WINE. I mean that can I install/build WINE over OpenVMS OS and MAC OS. 2) I have heard that WINE doesnot have support for WIN64 bit API's. Is this true that I cannot port WIN64 applications via WINE on Linux 64 bit. If this is possible for anyone among you then plz list the name of all the OS where

I've gone through the CVS commit log and tried to get every user-visible change since 2.4.6, so that we can make a proper announcement for 2.4.7. Please let me know if anything is missing/inaccurate. At this stage I'm planning to release two 2.4.7pre tarballs, one with the "large nohang patch" and one without. Some people inside VA will be stress-testing both, and so we can

As one of the OS' without current CMake support, I'm closely watching this discussion. We currently have LLVM 3.4.2 hosted on OpenVMS Itanium (as a host only, x86 target) using configure/make with little hassle. We plan to port CMake to OpenVMS, but that has been trickier than you'd think (others have tried, I haven't found anybody who has done it). Looks like I'll want to

Dear community, My company is interested in porting LLVM to OpenVMS. To do so, we need to look at extending the AMD64 calling convention to suit the existing calling conventions available on OpenVMS. We realize LLVM is a big and complex project and for some people who has not worked on it before, it's going to be a big and tough job that is going to take a lot of time. Still, the job has to

On Wed, May 18, 2016 at 01:10:50PM +0000, Daniel Sanders via llvm-dev wrote: > It's my understanding that llvm-mc is intended to be a testing tool > for LLVM developers rather than an assembler for end users. Users > should be assembling with clang. Not all LLVM users are clang users. For example, we're using LLVM to build OpenVMS cross-compilers to x86 for our porting effort.

As part of our port of OpenVMS to x86-64, we are using LLVM with our own frontends on OpenVMS Itanium. We are writing a converter between our old backend's IR and the LLVM IR. We can cross-compile (hosted on OpenVMS Itanium) and link/execute on x86-64 CentOS. At present, we pass over 88% of our C test suite. Porting starts with being able to compile the code. Since we are stuck with a

Yes. We currently build LLVM 3.4.2 on our OpenVMS Itanium box with an older EDG/Intel C++03 compiler to create legacy cross-compilers to our OpenVMS x86 box (well, VirtualBox). We do have a few tweaks to the relocations to access static data always through the GOT (including CodeGen's static data). Our linker sees references to code (which might be in 64-bit space) and creates trampolines

Hi all, We're at the point in our port of OpenVMS to x86-64 that we're working on the unwind code.  The current ABI and the current codebase doesn't have enough support for true asynchronous unwinding from any point (most notably in the prologue/epilogue) in the code that OpenVMS needs.  We're working on a set of changes to the compact unwind information to handle the additional