Displaying 20 results from an estimated 3000 matches similar to: "openbsd-compat"
2002 May 28
1
Build problem on IRIX 6.5.16m
I had a problem building OpenSSH 3.2.3p1 on IRIX 6.5.16m.
The configure command I used was:
env CC=cc ./configure --prefix=/usr --sysconfdir=/etc/ssh
--libexecdir=/usr/lib \
--mandir=/usr/share/man/u_man --with-catman=man --without-rsh \
--with-xauth=/usr/bin/X11/xauth --with-ssl-
dir=../openssl-0.9.6d \
--with-prngd-socket=/dev/egd-pool
The errors during make are:
2014 Sep 29
2
[LLVMdev] Windows Installer
Your install dir has a whitespace. Have you tried quoting? e.g.
<LLVMInstallDir>"C:\Program
Files (x86)\LLVM"</LLVMInstallDir>
Best regards,
Rafael Auler
On Mon, Sep 29, 2014 at 7:38 PM, Eric Mader <emader at gmx.us> wrote:
> I changed tooset-vs2013.props to this:
>
> <Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003"
>
2014 Sep 30
2
[LLVMdev] Windows Installer
I replaced all instances of "$(Platform)" with "x64" for the x64 .props
file and it still fails, so it looks like that guess was wrong as well.
Regards,
Eric
On 9/29/14, 2:11 PM, Eric Mader wrote:
> Quoting doesn't seem to make a difference. Strangely, the Win32
> toolset seems to work. (Where "work" means that clang runs and
> produces a bunch of
2014 Sep 29
2
[LLVMdev] Windows Installer
Open the file toolset-vs2013.props and you'll understand what's happening
and where the path is set. It tries to fetch the LLVM installation path
from the Windows registry. Just fix this (maybe editing your registry or
editing the .props file, whatever suits you best).
On Mon, Sep 29, 2014 at 5:33 PM, Eric Mader <emader at gmx.us> wrote:
> I copied the x64 toolsets by hand and
2001 Sep 27
4
ssh2 key passphrase problems in 2.9.9 on Linux
I've just compiled and installed openssh-2.9.9p2 (compiled against
openssl-0.9.6b using gcc-3.0.0) on a Slackware 7-based Linux machine
(kernel 2.4.6ac2). The previously installed version was 2.9p2, compiled
against openssl-0.9.6a, also with gcc-3.0.0, but with a different build of
gcc-3.0.0.
Everything seems to work fine except for one problem: passphrase matching
for ssh2 keys
1999 Nov 17
3
file permissions and smbmount
I'm using Samba 2.0.6 on a Linux server.
When using smbmount or mount to mount a share from an NT server, how do I
set file permissions. An older smbmount allowed a -d and -f switch to set
the file permissions. The newest one does not support these. The man pages
for smbmount and smbmnt mention using syntax that does not work.
I finally have gotten the mount command to work, but now I
2014 Oct 01
2
[LLVMdev] size_t?
I believe that we provide a definition of size_t inside the compiler itself
when clang is in MSVC compatibility mode.
On Tue, Sep 30, 2014 at 5:51 PM, Eric Mader <emader at gmx.us> wrote:
> I did some more investigation of the size_t size error. I misunderstood
> what was happening. It turns out that size_t is already defined before my
> prefix header is included. I added the
2014 Oct 01
2
[LLVMdev] size_t?
We inject a typedef for size_t here:
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Sema/Sema.cpp?revision=218230&view=markup#l206
The typedef type is determined by calling getSizeType().
SizeType is (relevantly) calculated in two places:
X86_64
http://llvm.org/viewvc/llvm-project/cfe/trunk/lib/Basic/Targets.cpp?revision=218666&view=markup#l3512
X86_32
2014 Sep 29
4
[LLVMdev] Windows Installer
I was hoping to not have to build LLVM myself, especially on Windows.
Can anybody help me with the Windows installer?
Failing that, I find the directions for how to compile on Windows hard
to follow? Can I build using Cygwin?
Regards,
Eric
On 9/29/14, 8:11 AM, Rafael Auler wrote:
> I'm not sure about the Windows installer, but if you build and install
> LLVM for Windows from the
2014 Sep 30
2
[LLVMdev] Windows Installer
Hi Hans,
Answers inline below.
Regards,
Eric
On 9/30/14, 8:05 AM, Hans Wennborg wrote:
> On Mon, Sep 29, 2014 at 7:56 PM, Eric Mader <emader at gmx.us> wrote:
>> Hi Hans,
>>
>> I think installer.bat found my visual Studio installation because it
>> installed the Win32 toolsets but not the x64 ones. (It took me a while to
>> work this out ;-) I installed
2014 Oct 01
2
[LLVMdev] -fblocks?
I'm trying to compile some C++ code on Windows that contains blocks. The
compiler gives me the error that the blocks language feature is not
enabled and that I should enable it with "-fblocks". When I add that
compiler flag, the compile fails immediately saying "unknown argument:
'-fblocks'"
Is this perhaps an incomplete feature?
Regards,
Eric Mader
2014 Sep 30
2
[LLVMdev] size_t?
Hi Reid,
I copied the x64 toolsets by hand; they got installed to C:\Program
Files (x86)\LLVM\tools\msbuild\x64; they just didn't get moved correctly
by install.bat.
I just verified that the LLVM-vs2013 toolset.props is correct.
If it is a bitness problem, perhaps I'm failing to define something
correctly?
Regards,
Eric
On 9/30/14, 11:29 AM, Reid Kleckner wrote:
> This looks
2014 Sep 29
4
[LLVMdev] Windows Installer
I’m trying to install LLVM-3.6.0-r218288-win32.exe on Windows 7 Ultimate
x64. The install doesn’t complain, but the toolset doesn’t show up in
either Visual Studio 2013 or Visual Studio 2010. Also I selected the
choices to add LLVM to the path for every user and put an LLVM icon on
the desktop. Neither of this happened. Can anyone tell me how to get
this to work?
Regards,
Eric Mader
1999 Nov 12
1
smbmount problem after kernel recompile
Hi all,
I am running SuSE 6.2 on a machine with 2 processors, so I just recompiled
the kernel to pick up the second cpu.
I now have problems using smbmount (2.0.5a that came with distrubution) or
using the newer mount syntax (I just installed 2.0.6) to mount a share from
an NT 4.0 server. After issuing the smbmount/mount command, and then going
to the mount point, I get i/o errors on the
2014 Oct 01
2
[LLVMdev] Compiling As Obj-C or Obj-C++ On Windows
I have some C++ source files that mix in small bits of Obj-C. On the
Mac, these files are marked to be compiled as Obj-C++. Looking at the
clang help, it seems that the option for that is "-ObjC++". However,
when I add that in Additional Options I get an error message:
CL> : error : invalid integral value 'bjC++' in '-ObjC++'
I see this same message if I put
2001 Sep 27
1
AIX lastlog change?
Somewhere between 2.9p1 and 2.9.9p2 there was a change to auth2.c that
removed the userauth_reply() function. There were a few lines of code
in that function, #ifdef'd with WITH_AIXAUTHENTICATE, that handled the
AIX method of lastlog type stuff (specifically, a loginsuccess() call).
There is a similar call in auth1.c, down in do_authentication(), which
is still there in 2.9.9p2.
So with
2014 Sep 30
2
[LLVMdev] Windows Installer
Hi Hans,
I think installer.bat found my visual Studio installation because it
installed the Win32 toolsets but not the x64 ones. (It took me a while
to work this out ;-) I installed the x64 toolsets by hand and they seem
to work.
I think the installer ran as administrator. I explicitly ran it that way
again (asking it to uninstall first) just to be sure. It didn't seem to
make any
2006 Mar 24
4
SAMBA install on IRIX 6.5
I am having problems with Samba on IRIX 6.5 authenticating via Active
Directory. Installing the tardist of 3.0.21c did not give me
kerberos/ldap/adc capabilities even though Kerberos and LDAP were
prereq's. With OpenLDAP and Kerberos5 installed, my configure fails. I
am trying this:
./configure --libdir=/usr/lib --includedir=/usr/include
--prefix=/usr/samba --with-ldap --with-ads
2014 Oct 02
2
[LLVMdev] Header File Not Found?
I'm having a strange problem compiling with VS 2013. It's not finding a
header file that's there in one of the header file search dirs.
Here's the compile command (with the names changed to protect the
innocent ;-)
1> C:\Program Files (x86)\LLVM\msbuild-bin\CL.exe /c
/IC:\[top-level-dir]\[source-dir]\
/IC:\[top-level-dir]\[source-dir]\[sub-dir-1]
2014 Sep 30
2
[LLVMdev] Barking Up The Wrong Tree?
I'm trying to port a bunch of code from MacOS X to Windows. The code is
a mixture of C, C++11 and Objective-C. (Some of the C++ code has bits of
Objective-C mixed in, just for spice ;-) Since it builds on the Mac with
clang, I thought that building on Windows with clang would mean that I
wouldn't have to make a bunch of changes just related to a different
compiler. For example, if I