similar to: [Patch] Make OpenSSH work with FreeBSD's utmpx implementation

Hello OpenSSH hackers, The last couple of weeks I've been figuring out how hard it is to replace FreeBSD's <utmp.h> with <utmpx.h>. I don't think utmpx is perfect, but at least it's better than what we have now and at least it has gone through some form of standardisation. I noticed POSIX says the following [1]: | The <utmpx.h> header shall define the utmpx

https://bugzilla.mindrot.org/show_bug.cgi?id=1732 Summary: Proper utmpx support for FreeBSD HEAD Product: Portable OpenSSH Version: 5.4p1 Platform: Other OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy: ed

http://bugzilla.mindrot.org/show_bug.cgi?id=378 Summary: sshd does not update utmp/utmpx records correctly when "UseLogin" feature on Product: Portable OpenSSH Version: -current Platform: MIPS OS/Version: IRIX Status: NEW Severity: normal Priority: P2

Hello all, I've happily been using Dovecot for a couple of years now, but only a couple of days ago I configured it to speak both TLS and SSL for both POP3 and IMAP. Ideally I want users to use TLS, but I've enabled SSL, because some mailers (at least Apple Mail on OS X Tiger) don't support TLS. Right now I'm in sort of a transitional phase, where I'm asking users to enable

On 10 Jan 2015, at 17:35, Dimitry Andric <dimitry at andric.com> wrote: > > It looks like the interpretation of what "__STDC_MB_MIGHT_NEQ_WC__" means differs between the llvm developers and the FreeBSD developers. I'm not sure what a good solution is. I've just read the relevant parts of the C11 spec, and it's not really clear to me what the 'basic

On 12 Jan 2015, at 08:07, Dimitry Andric <dimitry at andric.com> wrote: > > > On 15 Oct 2014, at 19:42, Richard Smith <richard at metafoo.co.uk> wrote: >> On 15 Oct 2014 05:12, "Ed Schouten" <ed at 80386.nl> wrote: > ... >> The test case in the LLVM tree is invalid and should be discarded. It >> erroneously assumes that the encoding of

2015-03-29 3:33 GMT-05:00 Ed Schouten <ed at 80386.nl>: > I am cross-compiling compiler-rt for my specific use-case. That said, > I'm cross-compiling from x86-64 to x86-64, but for a different ABI. > This is what I use: > > > https://github.com/NuxiNL/cloudlibc/wiki/Building-runtime-libraries#user-content-compiler-rt > > -DCMAKE_CROSSCOMPILING=True > > As

* 罗勇刚(Yonggang Luo) <luoyonggang at gmail.com> wrote: > The patch is for version 77784 > And it's fixed the cmake for eclipse win32 mingw makefile output:) > Also a warning in VS 2008 on stub.c > Hope someone apply this patch. > And those files that place the > <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> > Before

The patch is for version 77784 And it's fixed the cmake for eclipse win32 mingw makefile output:) Also a warning in VS 2008 on stub.c Hope someone apply this patch. And those files that place the <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> Before <title> is just because of in tag title may contains strange characters such as Chinese

Hi, I've cross-compiled musl-libc to arm binaries with clang. It needs functions from static runtime library "libcompiler_rt.a". I tried to build compile_rt outside the llvm source tree. Using command like "make clang_linux", I can easily build "libcompiler_rt.a" for my host machine, which is X86_64. But how can I *cross-compile* the compiler_rt runtime

Dear all, When I tried to compile LLVM, I found these annoying warnings. I actually found several other, but this patch deals with the trivial ones Regards, Rizky Herucakra -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100612/d2171b49/attachment.html> -------------- next part -------------- A

Hello everyone, Since yesterday I've been toying around with LLVM on my FreeBSD box at the office. As an ideal test I tried to compile a FreeBSD kernel. I've just sent the following message to the FreeBSD Hackers list, which contains some stats on compile time, binary size, etc. Links: http://lists.freebsd.org/pipermail/freebsd-hackers/2008-May/024600.html

Hi folks, I just tried to build LLVM on FreeBSD/arm. It looks like libSystem doesn't build and requires the following hack: --- lib/System/Memory.cpp +++ lib/System/Memory.cpp @@ -61,7 +61,7 @@ for (intptr_t Line = StartLine; Line < EndLine; Line += LineSize) asm volatile("icbi 0, %0" : : "r"(Line)); asm volatile("isync"); -# elif defined(__arm__)

Hi all, Speaking about warnings, we're seeing the following warnings when building LLVM/Clang on FreeBSD/amd64. When using GCC: http://amd64-clang-bot.qat.freebsd.org:8010/builders/freebsd-clang-amd64/builds/20/steps/compile-llvm.1/logs/warnings When using Clang: http://amd64-clang-bot.qat.freebsd.org:8010/builders/freebsd-clang-amd64/builds/20/steps/compile-llvm.2/logs/warnings -- Ed

I am having trouble figuring out how to build openssh-5.8p1 for QNX 6.5. I am trying to build on linux, cross-compiling for armv7. If I configure like this: configure CC=ntoarmv7-gcc --host=i686-pc-linux-gnu --target=arm-unknown-nto-qnx6.5.0 then I get these errors: sshconnect.o: In function `timeout_connect': sshconnect.c:(.text+0x778): undefined reference to

Hi there, I'm experiencing some problems accessing some of the services on llvm.org: $ svn co https://llvm.org/svn/llvm-project/llvm/trunk svn: E200029: Couldn't perform atomic initialization https://llvm.org/bugs/show_bug.cgi?id=24734: "undef error - DBD::mysql::st execute failed: Got error 28 from storage engine" On Linux, errno 28 corresponds with ENOSPC, so my suspicion

Hi, I've installed openssh-2.1.0p2 on a Solaris 8 host (SPARC). The sshd corrupts utmpx/wtmpx when a client connects to this machine. Observable error: $ who who: Error --- entry has ut_type of 28265 when maximum is 9 It can be repeated and is attributable to the login done by sshd. Now, Solaris has only utmpx/wtmpx and not the old utmp/wtmp. It get's worse as more logins take place

it seems that --enable-utmpx and friends have the effect of disabling the corresponding feature (i.e., #define-ing DISABLE_UTMPX etc.), which leads to the (perhaps not so) obvious breakage of UseLogin on Solaris etc. For the less anal (or reformed anal) configure-r who leaves these unspecified, everything is OK i'd suggest changes to configure.in, but i'm blissfully ignorant of autoconf.

We're trying to build OpenSSH 3.0.2p1 for Solaris 8 (among others) and are running into a problem with UseLogin and utmpx. If we set "UseLogin no" then we can login okay. finger or who won't find us, even with a TTY allocated altough "who /etc/wtmpx" will find us. But the real problem is if we set "UseLogin true" which we must do for BSM support on some

http://bugzilla.mindrot.org/show_bug.cgi?id=960 Summary: Support needed for NetBSD utmpx field ut_ss Product: Portable OpenSSH Version: 3.9p1 Platform: All OS/Version: NetBSD Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org ReportedBy: eravin