search for: sysv4

Hello, would it be possible to update config.sub and config.guess to the latest versions (or at least version from automake-1.13.1) in order to support new architectures based on the ARM 64 bit CPU? Patch: http://plautrba.fedorapeople.org/openssh/openssh-latest-config.sub-config.guess.patch Related Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=926284 Thanks, Petr

The following is special to sshd 3.9p1 under ReliantUnix 5.45. It does not occur under ReliantUnix 5.43 nor under Solaris 5.8: `pwd`/sshd-3.9 -e -D -d -d -d Now connecting from outside [...] debug1: inetd sockets after dupping: 3, 3 debug1: get_port() calls get_sock_port(3) debug1: getpeername failed: Operation not supported on transport endpoint lsof proves FD 3 is an established TCP

...iffs (obtained with 'diff -c' on the Dynix box) of the two files I had to change: *** configure Sat Jun 16 17:09:50 2001 --- configure.new Mon Oct 8 11:33:09 2001 *************** *** 1960,1965 **** --- 1960,1985 ---- LIBS="$LIBS -lgen -lnsl -lucb" ;; + *-sequent-sysv4*) + CPPFLAGS="$CPPFLAGS -I/usr/local/include" + LDFLAGS="$LDFLAGS -L/usr/local/lib" + LIBS="$LIBS -lnsl -lsec" + rsh_path="/usr/bin/resh" + conf_utmpx_location="/var/adm/utmpx" + cat >> confdefs.h <<\E...

...' - ;; - ccc) - wl='-Wl,' - ;; - esac - ;; - osf3* | osf4* | osf5*) - wl='-Wl,' - ;; - sco3.2v5*) - ;; - solaris*) - wl='-Wl,' - ;; - sunos4*) - wl='-Qoption ld ' - ;; - sysv4 | sysv4.2uw2* | sysv4.3* | sysv5*) - wl='-Wl,' - ;; - sysv4*MP*) - ;; - uts4*) - ;; - esac -fi - -# Code taken from libtool.m4's AC_LIBTOOL_PROG_LD_SHLIBS. - -hardcode_libdir_flag_spec= -hardcode_libdir_separator= -hardcode_direct=no -hardcode_minus_L=no - -ca...

...make it the default for Reliant > Unix. It does not fix the problem really but it is a reasonable work-around which is sufficient for the standard X11-applications like xterm, xeyes, etc. So I think it is a good idea to turn that on for Reliant UNIX. The host has been detected as "mips-sni-sysv4" It still can't work with the System Management tool TransView. This application tries hard to figure out whether it is running on the local host and opens the communication to the local name piped /tmp/.X11-unix/Xn (n being the DISPLAY number) instead of the TCP-port 6000+n. I am still...

...pe_queue is defined in dbxout.c > > If your platform is not using stabs debugging format (nowadays most of > the platforms use DWARF format) then it won't define DBX_DEBUGGING_INFO. > > Based on your response I've removed the #undef DBX_DEBUGGING_INFO in gcc/config/ia64/sysv4.h. I don't need stabs debugging so if it is broken in my final build, I won't care. After doing so, my llvm-gcc build runs for a much longer time before finally dying while running xgcc. Here is the final output: /liberty/llvm.ia64/obj/./gcc/xgcc -B/liberty/llvm.ia64/obj/./gcc/ -B/libe...

I would be surprised if someone hasn''t encountered this already, but I haven''t found any discussion of the nature of this problem. I run RehHat 5.0. If a user makes a mistake in the login process such as the following: login: mistake password: xxx Login incorrect! login: username password xxxx bash$ a ps will show, among other things, 2333 /bin/login --mistake. Since

On Jan 10, 2008, at 10:29 AM, Thomas Jablin wrote: > Hi, > > I've figured out a little more. #if defined DBX_DEBUGGING_INFO || > XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however, > neither is defined on Intanium. In gt-dbxout.h type_queue's uses are > unguarded and thus are undefined on Itanium. When I compared llvm- > gcc's > gt-dbxout.h

On Jan 10, 2008, at 12:52 PM, Thomas Jablin wrote: >> > Based on your response I've removed the #undef DBX_DEBUGGING_INFO in > gcc/config/ia64/sysv4.h. I don't need stabs debugging so if it is > broken > in my final build, I won't care. After doing so, my llvm-gcc build > runs > for a much longer time before finally dying while running xgcc. Here > is > the final output: > > /liberty/llvm.ia64/obj/./gcc/xgc...