similar to: Error when cross configuring openssh 4.2p1

On Thursday 04 October 2007 04:27:47 you wrote: > Sir, you need to provide more information. What kind of errors? What > is not working? What exactly are you trying to do? What compiler are > you using? H IV0, we are using a lot of different cross-compiler (mainly based on GCC 3.4.x) When I tried to cross-compile FLAC for non-i386 platforms (such as ARM), I use use

I am very new to linux and openSSH ,, i am trying to compile openssh for jungo openrg IXP45. but while configuring i am getting following error,, hecking for libgen.h... yes checking for getspnam... yes checking for library containing basename... none required checking for deflate in -lz... no configure: error: *** zlib missing - please install first or check config.log *** if anybody will me

I am trying to cross compile openssh for arm5b-jungo-gnu-gcc,, and also using openssl and zlib from same compiler arm5b-jungo-gnu-gcc but i am getting following error,,, /usr/local/openrg/armv5b-jungo-linux-gnu/bin/armv5b-jungo-linux-gnu-ld: warning: cannot find entry symbol _start; defaulting to 0000b9c8 /usr/local/openrg/armv5b-jungo-linux-gnu/bin/../armv5b-jungo-linux-gnu/lib/libcrypto.so:

I was successful in compiling asterisk in raspbien except for the following error If I enable the gsm codec. It appears there is something in the Makefile n this directory that needs to be changed. Probably involving optimization. Not sure why it does not recognize the processor since it is one that is mentioned in the Makefile.? Any help would be appreciated. make[2]: Entering directory

hi, Dale Johannesen wrote: > On Oct 19, 2007, at 7:23 AM, Dietmar Ebner wrote: >> i'm trying to make some experiments with the ARM backend (llvm 2.1) >> and >> therefore built an arm-softfloat-linux-gnu toolchain on x86_64 linux. >> >> however, the llvm-gcc frontend seems to cause troubles with single >> precision floating point values, i.e., they are

Hi anyone. When I run make trying to compile Dovecot for a network attached storage box and it fails. I have used two variants of configuration: The first ./configure i_cv_epoll_works=no i_cv_inotify_works=no i_cv_posix_fallocate_works=no i_cv_signed_size_t=no i_cv_gmtime_max_time_t=32 i_cv_signed_time_t=yes i_cv_mmap_plays_with_write=yes i_cv_fd_passing=yes i_cv_c99_vsnprintf=yes

Hi Rafael, As you mentioned in the bug, we should only apply this change when hard-float is set, which it is by default on armv7a, I presume. >From that part of the code, I can infer that by the time "MaxAtomicPromoteWidth = 64;", the variable SoftFloat is not properly set, so a simple "if (!SoftFloat)" won't cut in there. It seems SoftFloat is being set on

Hi. I'm trying to cross compile dovecot. My desktop machine is an AMD64 box with bells and whistles. The ARM based machine is a network attached storage box. When I run "make" always get x86_64 binaries. My OS is Gentoo, so I have been able to build using emerge a variety of other programs from source. What am I doing wrong here. (Gentoo doesn't have Dovecot for the arm) I

Hello, I am using OpenSSH-3.8p1 on HP-UX machine with USE_POSIX_THREADS option. This is for making the kerberos credentials file to be created in the system with PAM. In OpenSSH versions 3.5 when authentication is done with pam kerberos, a /tmp/krb5cc_X_Y file is created on the server side. But the KRB5CCNAME variable is not set by default. So, after we manually set this environment variable, the

On Mar 21, 2011, at 3:44 AM, Anton Lokhmotov wrote: >> Adding half float to LLVM IR is *only* reasonable if you have hardware >> that supports half float, or if you want to add softfloat operations >> for these. > Yes, our graphics hardware natively supports some fp16 arithmetic > operations. Ok. >> Just like C compilers need to know sizeof(long), sizeof(void*) and

Hi, below is a patch which simply removes a Cygwin-specific piece of code from OpenSSH. Input from a system admin educated me how useful this option could be on Cygwin as well. However, way back when the call to read_etc_default_login got disabled on Cygwin hardcoded in session.c, rather than just setting --disable-etc-default-login when building the Cygwin version of OpenSSH. So, here's

Hello, Does Samba server have a grace period that allows a client to reopen its files and reacquire locks on them before the locks are given to other clients? If there is no grace period, is there a way for the client to avoid the lock ownerships files if the connection goes away for a short period (say few seconds). Thanks and Regards Sudheer

On Oct 19, 2007, at 7:23 AM, Dietmar Ebner wrote: > hi, > > i'm trying to make some experiments with the ARM backend (llvm 2.1) > and > therefore built an arm-softfloat-linux-gnu toolchain on x86_64 linux. > > however, the llvm-gcc frontend seems to cause troubles with single > precision floating point values, i.e., they are not converted > correctly > to the

hi, i've got some more things to note. first, the issue is not related to x86_64 being the host machine - it also happens on i686/linux. next, i think (one of) the problem(s) is the use of [HOST_]WORDS_BIG_ENDIAN instead of [HOST_]FLOAT_WORDS_BIG_ENDIAN in llvm-convert.cpp (see patch below). this fixes single precision floating point but breaks double precision. for

Dale Johannesen wrote: > On Oct 22, 2007, at 2:08 AM, Dietmar Ebner wrote: >> next, i think (one of) the problem(s) is the use of >> [HOST_]WORDS_BIG_ENDIAN instead of [HOST_]FLOAT_WORDS_BIG_ENDIAN in >> llvm-convert.cpp (see patch below). >> >> this fixes single precision floating point but breaks double >> precision. >> for arm-softfloat-linux-gnu,

hi, i'm trying to make some experiments with the ARM backend (llvm 2.1) and therefore built an arm-softfloat-linux-gnu toolchain on x86_64 linux. however, the llvm-gcc frontend seems to cause troubles with single precision floating point values, i.e., they are not converted correctly to the particular target format (double precision works as expected). it seems the problem is related to

Hi Chris, It is important for embedded/mobile computation to have efficient fp16 support, otherwise those users will suffer from the merging problem with their local LLVM with native fp16 type they add (locally). So we should either add full fp16 support as a basic floating point type or enhance the LLVM infrastructure to make floating point type as scalable as int type. -Chihong -----Original

Hi, I've got a box with CentOS 4.2 x86_64 which had no DHCP access for a few hours, now I can't ping it (I'm pretty sure the box is still up). I expect the DHCP lease has timed out and the box has lost it's IP, I was expecting it to reacquire it once the DHCP came back up (configuration problem) - but no luck. Is this a known problem? Any solution/workaround? (for now or for

When a mips16 wants to return a floating point value, it's at a quandary in mixed mode programs (having both mips16 and mips32 code). float foo() { return 1.0; } Mips16 code is compiled in soft float, with there being an options to have the emulation library be written in mips32 and use floating point instructions in those mips32 support functions (if the machine supports floating

On Mar 21, 2011, at 1:59 PM, Zhang, Chihong wrote: > Hi Chris, > > It is important for embedded/mobile computation to have efficient fp16 support, otherwise those users will suffer from the merging problem with their local LLVM with native fp16 type they add (locally). So we should either add full fp16 support as a basic floating point type or enhance the LLVM infrastructure to make