similar to: Problems Compiling 2.2.8 on Tru64 5.1

Displaying 20 results from an estimated 10000 matches similar to: "Problems Compiling 2.2.8 on Tru64 5.1"

2003 Mar 17
2
2.2.8 doesn't compile on Tru64-5.1
HI, I've successfully compile 2.2.8 on Solaris (6,7,8) and Linux. However on Tru64-5.1 I get the following during the make: Compiling smbd/dfree.c Compiling smbd/dir.c smbd/dir.c:649:70: macro "stat" passed 3 arguments, but takes just 2 smbd/dir.c:716:13: macro "stat" passed 3 arguments, but takes just 2 make: *** [smbd/dir.o] Error 1 Any ideas? Ramon Kagan York
2002 May 12
0
make error in 2.2.4; Tru64 Unix
I get the following error when trying to compile samba 2.2.4 on Tru64 Unix (v5.1). # make . smbd/dir.c:625: macro `stat' used with too many (3) args smbd/dir.c:693: macro `stat' used with too many (3) args I did make the change which has been discussed several times, to source/include/config.h .. changing #define HAVE_IMMEDIATE_STRUCTURES 1 to /* #undef
2003 Sep 25
4
[Bug 716] OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64 UNIX)
http://bugzilla.mindrot.org/show_bug.cgi?id=716 Summary: OpenSSH 3.7.1p2: sshd doesn't start at reboot (Tru64 UNIX) Product: Portable OpenSSH Version: -current Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: openssh-bugs
2004 Feb 10
1
FW: problems with samba 2.2.7 installed on Tru64 with OS 5.1
Hi Is there anyone who can answer to my question below? I've received an autoreply from Tan Feng with a message that he'll be on vacation until the 6th of Feb.. I've tried to go on the site mentioned by him without success... Please help. Regards, Dona Mihut HP, Managed Services, Asia Pacific > -----Original Message----- > From: Mihut, Donna > Sent: Tuesday, January
2002 Jul 12
5
rsync 2.5.5 Tru64 5.1
Hi, I am trying to compile rsync 2.5.5 on a Tru64 box. I downloaded configure.in revision 1.148, which I believe is the correct fix for the getaddrinfo problem; however I still have errors compiling rsync. Also I had to change line 22 in options.c from #include "popt.h" to #include "popt/popt.h". Any suggestions or ideas? Tan Dang
2004 Oct 15
3
Compiling on Tru64
So, before I waste another couple of hours at this, is it possible to compile Samba 3.0.x on Tru64 at all? If so, can you tell me what the ./configure switches are? Thanks, Nate
2001 Jun 06
1
configure patch for Alpha/Tru64 Unix 5.1
I had to apply this patch to configure.in to get configure to run on Tru64 Unix on Alpha. The RSA test forgot to reset $LIBS. (The compile stopped with missing "zlib.h". I'll send more patches if required. :-) diff -ur src-2.9p1/configure.in src-2.9p1-local/configure.in --- src-2.9p1/configure.in Wed Jun 6 17:15:09 2001 +++ src-2.9p1-local/configure.in Wed Jun 6
2002 Aug 28
2
Tru64 patch won't make it into 3.5 due to lack of interest.
Tru64 patch will not make it into 3.5 (this is final) due to lack of willing people to test. I have given the Tru64/osf1 community almost a month to test it. And *ONE* person came forward to give me verification. And don't give me shit about "I don't have time." The person who tested it was LEAVING his employer with Tru64. He found time. IT IS YOUR GAWD DAMN PLATFORM. IF
2004 Sep 20
3
[Bug 933] compile problem on tru64 5.1A code outside of a #ifdef that should not be included on tru64
http://bugzilla.mindrot.org/show_bug.cgi?id=933 Summary: compile problem on tru64 5.1A code outside of a #ifdef that should not be included on tru64 Product: Portable OpenSSH Version: 3.8p1 Platform: Alpha OS/Version: OSF/1 Status: NEW Severity: normal Priority: P2 Component: Build
2002 Jun 27
1
No TTY prealloc; Tru64 can't do post-auth privsep
Well, after digging around and thinking some more, I'm giving up on the idea of preallocating a TTY to get post-auth privsep working on Tru64. I don't think it will work, because just allocating a TTY doesn't fix the problem - there's no valid way to tie that TTY back to the client process (because it hasn't requested a TTY yet and may not ever do so). The problem is that the
2001 Feb 23
1
Problem with mput * on Tru64 ?
Samba 2.0.7 running on Compaq Tru64 UNIX V5.0A with latest tru64 patches. "mget *" works OK, "mput *" or something like "mput *.bat" fails with the error message "find: bad option -maxdepth". Several questions - Anyone else come across this one? Would dropping back to 2.0.6 fix the problem? Could it be an issue with 2.0.7 on Tru64 V5? Regards, Brian
2001 Feb 25
1
Problem with sftp-server on Tru64 (long long type and %ll)
The ls_file function in sftp-server.c calls snprintf with "%8llu" as part of the format string and a "unsigned long long" type argument. The "%ll" format is not a valid format on Tru64 (at least 4.0F). Apparently it can confuse snprintf as well - sftp-server will segfault and core dump if the user types "ls". This isn't really a needed format string on
2003 May 17
1
Tru64 Unix patch for rsync 2.5.6.
Version 2.5.6 of rsync fail to compile on Tru64 Unix v5.1 with this error message: cc-wrapper -I. -I. -g -DHAVE_CONFIG_H -c socket.c -o socket.o cc: Error: socket.c, line 619: In this statement, "sin_len" is not a member of "sock2". (needmember) sock2.sin_len = sizeof(sock2); --------^ make: *** [socket.o] Error 1 error: compile failed. The problem
2006 Sep 20
2
Tru64 Unix and SIA
I have recently written a (minimal) Tru64 Unix SIA password module for Dovecot as part of testing a Dovecot installation. Has anyone else written a Tru64 Unix SIA module? Is anyone else interested in such a module? If so, how might I/we go about getting this/such a module into the main Dovecot source? Thanks -- Simon L Jackson Carringbush.Net +- Carringbush.Net Hosting * Development *
2003 May 02
1
rsync+ssh2 from Tru64 unix to linux has intermittent hangs.
This is odd: We're using rsync to mirror multiple directories from a server to two clients. The server is running Tru64 v5.1a, client A is running Redhat Linux 8.0, and client B is running Tru64 v4.0g. The mirrors for both clients are running at the same time interval (10 minutes, offset by 5 minutes). All machines are running rsync v2.5.6, and using ssh2 v3.2.3 as the
2000 May 03
2
SIA support patches for Tru64 UNIX
I think I'm ready with the SIA (Security Integration Architecture) patches for Tru64 UNIX. All of the code was written by Tom Woodburn, an engineer at Compaq. I've only performed integration and testing of the patches with more help from Tom. Tom's original patches were included in the "other" ssh. We'd both like to see SIA support get into OpenSSH. SIA provides PAM-like
2002 Aug 28
1
ERROR: out of memory in flist_expand on Tru64 UNIX
I am running rsync version 2.5.5 on Tru64 UNIX on two AlphaServers running version 4.0F and version 5.1. Rsync fails with the error message: ERROR: out of memory in flist_expand A log of the command I am using is: # rsync --dry-run --recursive --delete foo:/foo1 /bar1/foo1copy receiving file list ... done ERROR: out of memory in flist_expand rsync error: error allocating core memory buffers
2003 Sep 16
1
OpenSSH 3.7p1, PrivSep, and Tru64 broken (sorry)
Well, I had just finally gotten around to downloading a snapshot to test the latest on Tru64 a couple of days ago but hadn't had a chance to build it yet, and 3.7p1 has now been released. Sigh. The problem is that Tru64 setreuid() and setregid() are broken, so privsep doesn't work. This could also be a security problem for SIA authentication in general (any version of OpenSSH on Tru64,
2001 Jun 26
1
compiling R-1.3.0 under Tru64 Unix
Dear all- I get the same problem in compiling R-1.3.0 on Tru64 Unix (OSF 5.0). Here is the final output of the ./configure R is now configured for alphaev67-dec-osf5.0 Source directory: . Installation directory: /usr/local C compiler: gcc -mieee -g -O2 C++ compiler: c++ -g -O2 FORTRAN compiler: f77 -fpe3 -g X11 support:
2003 Sep 19
1
configure fixes for Tru64 UNIX V4.0x
1) Testing of uidswap.c on a Tru64 UNIX V4.0G PK4 (BL22) machine shows the following defines to be required for correct uid changing semantics: #define BROKEN_SETREGID 1 #define BROKEN_SETREUID 1 #define SETEUID_BREAKS_SETUID 1 Failure to fix these contributes to breaking privilege separation (in a safe way: connections will fail while UsePrivilegeSeparation=yes, thanks to