similar to: solaris 2.5.1 still no good

Displaying 20 results from an estimated 6000 matches similar to: "solaris 2.5.1 still no good"

1999 Dec 09
1
solaris 2.5.1 still no good
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, Here's what I get under solaris 2.5.1 (sparc) with gcc-2.95.2 and gnumake 3.78-something : bsd-snprintf.c: In function `msetup': bsd-snprintf.c:67: warning: implicit declaration of function `getpagesize' bsd-snprintf.c:72: `x' undeclared (first use in this function) bsd-snprintf.c:72: (Each undeclared identifier is reported
1997 Jul 08
3
so-called snprintf() in db-1.85.4
Hi, There is a severe problem with the db-1.85.4 library''s Linux port that can be found on sunsite.unc.edu under /pub/Linux/libs/db-1.85.4-src.tar.gz (sp?): This library contains a "snprintf" function which breaks down to a common sprintf, ignoring the size parameter. Obviously, this was thought to be a terribly bad work-around for C libraries which don''t contain an
2000 Jan 06
1
bsd-snprintf.c and NeXT.
I'm wonder if anyone happens to have a simplier (slower) version of bsd-snprintf.c. It seems NeXT 3.3 (unsure about 4.2) is missing mprotect(). If I could get something to replace that for a while and fix some of theses utmp in login.c issues I may have a rough port NeXT to black hardware.=) Thanks
2001 Oct 18
2
Incorrect return types for snprintf() and vsnprintf()
Both of these functions are using strlen() to create return value. Cheers, Scott Rankin *** /openbsd-compat/bsd-snprintf.c.orig Thu Oct 18 13:57:51 2001 --- /openbsd-compat/bsd-snprintf.c Thu Oct 18 13:58:26 2001 *************** *** 632,638 **** #endif /* !defined(HAVE_SNPRINTF) || !defined(HAVE_VSNPRINTF) */ #ifndef HAVE_VSNPRINTF ! int vsnprintf(char *str, size_t count, const char *fmt,
2000 Feb 21
1
OpenSSH doesn't compile under Solaris 2.3 Sparc
Hi, We are trying to get OpenSSH-1.2.2 stable release to compile under Solaris 2.3 Sparc. It worked perfect for Solaris 2.5, Solaris 2.5.1, Solaris 7 (All on Sparc) and Linux 2.2.13 Intel x86 OpenSSL installs fine without problem, zlib is installed fine without problems and egd.pl installs fine without problems. These are all the current releases, I can get the version numbers if you need
2014 Sep 18
3
patch for win_utf8_io.c: vsnprintf_s vs. MinGW
lvqcl wrote: > Oops. It seems that vsnprintf_s isn't always available on MinGW platform: > MinGW declares this function only if MINGW_HAS_SECURE_API macro is defined. > That's because WinXP version of msvcrt.dll doesn't contain secure functions > like vsnprintf_s. > > Maybe it's better to revert vsnprintf_s to vsprintf or to use vnsprintf? Ok, we need to drop
2002 Oct 23
2
vsnprintf()
I think I stumbled upon a bug in the i_snprintf() function. In the case of vnsprintf() being available, it depends on vnsprintf() returning -1 when the string was longer than the passed-in limit (or it won't terminate the string.). But this isn't the C99-standardized behaviour, and newer glibc's don't do that anymore either, so you can end up with a non-terminated string. This
2010 Apr 26
3
openbsd-compat regression tests
The snprintftest.c regression test in openbsd-compat/regress has a buffer overflow error, and an argument error in the calls to snprintf(), and vsnprintf(). On line 49 of snprintftest.c, the character buffer, b, is allocated at 5 bytes. However, in the calls to snprintf and vsnprintf, on lines 68 and 77 respectively, it is expected to place 11 bytes of data into the buffer. Which will result
2001 Feb 12
5
SCO OS3 build broken (CVS 01/12/01)
It looks like something got broken in openbsd-compat/bsd-snprintf.c ... gcc -g -O2 -Wall -Dftruncate=chsize -I/usr/local/include -I/usr/local/ssl/includ e -I. -I.. -I../src/openbsd-compat -I../src/openbsd-compat/.. -DHAVE_CONFIG_H -c ../src/openbsd-compat/bsd-snprintf.c In file included from ../src/openbsd-compat/bsd-snprintf.c:72:
2015 Jan 08
1
New version of Rtools for Windows
Oh, I forgot to mention that besides setting AR, RANLIB and the stack probing fix, you also need a very up to date binutils. 2.25 was out in december. Even with that , if you linker's default is not what you are compiling for (i.e. a multiarch toolchain), you need to set GNUTARGET also, i.e. -m32/-m64 is not enough. Some fix to autodetect non-default targets went in after christmas before the
2005 Mar 17
2
Snom190 intercom
Hi All... I'm trying to get the intercom feature working on some snom 190 phones but having no luck... As you can see from the SIP trace below (from the called phone), intercom=true is being appended to the To: header as per requirements. I've email'd snom a few days ago but have yet to get a response. On my 190s, im running snom190-SIP 3.57v. I am pulling the config for the
2000 Jan 17
5
AANOUNCE: openssh-1.2.1pre27
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.
2000 Jan 17
5
AANOUNCE: openssh-1.2.1pre27
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A couple of silly errors, and one dangerous bug were in the pre26 release. This release corrects them. http://violet.ibs.com.au/openssh/files/openssh-1.2.1pre27.tar.gz If you want RPMs or any of the other files, please use a mirror: http://violet.ibs.com.au/openssh/files/MIRRORS.html Changes: - Using __snprintf is *NOT SAFE* on old Solaris.
2013 Feb 27
2
ocfs2 bug reports, any advices? thanks
Hi, I setup two nodes, 192.168.20.20, and 192.168.20.21, The os is Ubuntu1204 with Kernel version 3.0: root at Server21:~# uname -a Linux Server21 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Server20 reboot for the disconnection with iSCSI SAN, so Server20 recovery resource locks for Server21. Server20: Feb 27 09:29:31 Server20 kernel:
2013 Feb 27
2
ocfs2 bug reports, any advices? thanks
Hi, I setup two nodes, 192.168.20.20, and 192.168.20.21, The os is Ubuntu1204 with Kernel version 3.0: root at Server21:~# uname -a Linux Server21 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux Server20 reboot for the disconnection with iSCSI SAN, so Server20 recovery resource locks for Server21. Server20: Feb 27 09:29:31 Server20 kernel:
2000 Jun 27
1
openssh-2.1.1p1 on Irix6.2 report
I've had fairly good sucecss with the portable OpenSSH 2.1.1p1 on Irix 6.2. There's one major nit, and a few things that configure got wrong. I'm kinda deep in real work at the moment, so I don't have time to delve heavily, but since configure specifically asked for feedback on this port, I'm obliging. The biggest problem I've run into so far is in the builtin PRNG
2007 Apr 12
2
[PATCH] Make com32 printf obey width-restriction on %s
Hi, The following patch is against 3.36. It lets the width-modifier to the %s conversion specifier restrict the length of the formatted string as well as expand it. In addition, it adds the strnlen function, which only exists as a prototype today. -- Arne. --- syslinux-3.36/com32/lib/Makefile.orig 2007-02-10 21:47:07.000000000 +0100 +++ syslinux-3.36/com32/lib/Makefile 2007-04-12
2003 Jun 25
2
snprintf, vsnprintf
I'm tracking a compiling issue with 2.2.8a on AIX 5.2-ML01 with IBM C for AIX 6.0 and i'm having an issue with lib/snprintf.c The first thing i noticed is that "includes.h" is not included which is in many other places, but I'm sure there are reaasons. The other thing is there is a check at the beginning for HAVE_SNPRINTF, HAVE_VSNPRINTF and HAVE_C99_VSNPRINTF to include
1999 Nov 24
2
snprintf on solaris
Hello, I've managed to get around the undefined paths in openssh-1.2pre14 on solaris, but now I'm stuck without an implementation of snprintf and vsnprintf. Is there a library I can download or a way to #define the functions into compatibility? Thanks, --Henry
2014 Sep 12
2
win_utf8_io.c: Use fputws instead of fwprintf
Hi On MSVCRT, wprintf expects that %s is wide char string, but for not MSVCRT, this is not true. When using -D__USE_MINGW_ANSI_STDIO=1 on MINGW, mingw doesn't use MSVCRT. Therefore, compiling on mingw with -D__USE_MINGW_ANSI_STDIO=1 and redirecting stderr to a file, the printing result is corrupt. We should use fputws simply. A patch is attached. -------------- next part