search for: svr4

...'s what I've gathered > > so > > far alongside with some questions. > > Sorry for the confusion, this all should probably be cleaned up a > bit. > In general, LLVM today supports the following ABIs: > - The Darwin ABI (32-bit and 64-bit flavors) > - The 32-bit SVR4 ABI > - Two variants of the 64-bit SVR4 ABI: ELFv1 and ELFv2 > > The ELFv1 ABI is used on 64-bit big-endian Linux and AIX. > The ELFv2 ABI is used on 64-bit little-endian Linux. > > Unfortunately, the term "SVR4" is quite overloaded, and applies > both to the 32-bit...

Hi all, I'm trying to understand which ABIs are supported in the PowerPC backend and I'm getting a bit confused. Here's what I've gathered so far alongside with some questions. - In PPCSubtarget.h there's DarwinABI, SVR4ABI and ELFv2ABI. - The CodeGenerator documentation claims that the AIX PowerPC ABI is followed (with some deviations). Is this refering to the DarwinABI? - In a recent commit a TargetABI value and enumeration was added to PPCSubtarget which contains PPC_ABI_UNKNOWN, PPC_ABI_ELFv1 and PPC_ABI_ELFv2....

hello everybody, Anybody ever compile rsync under "ncr mp ras svr4" unix system? I'm having some problem to run it. I compiled everything as in README file. when i tried run the rsync binary i received this error: ksh: rsync: not found unexpected EOF in read_timeout i even use full path to rsync and yer still get the same error. Anybody could help me, p...

...-c checking for mawk... no checking for gawk... no checking for nawk... nawk checking whether cc understands -c and -o together... no checking that the C compiler understands volatile... yes checking host system type... configure: error: can not guess host type; you must specify one # # configure svr4 loading cache ./config.cache checking for gcc... no checking for cc... cc checking whether the C compiler (cc -O ) works... yes checking whether the C compiler (cc -O ) is a cross-compiler... no checking whether we are using GNU C... no checking for a BSD compatible install... ./install-sh -c check...

...it confused. Here's what I've gathered so >> far alongside with some questions. > > Sorry for the confusion, this all should probably be cleaned up a bit. > In general, LLVM today supports the following ABIs: > - The Darwin ABI (32-bit and 64-bit flavors) > - The 32-bit SVR4 ABI > - Two variants of the 64-bit SVR4 ABI: ELFv1 and ELFv2 > > The ELFv1 ABI is used on 64-bit big-endian Linux and AIX. > The ELFv2 ABI is used on 64-bit little-endian Linux. > > Unfortunately, the term "SVR4" is quite overloaded, and applies > both to the 32-bit a...

...that sh seemed to be more capable than > I remembered. If you like to check what the Bourne Shell did support in the late 1980s, I recommend you to fetch recent Schily tools from: https://sourceforge.net/projects/schilytools/files/ compile and install and test "osh". This is the SVr4 Bourne Shell, so you need to take into account what has been added with Svr4: - multibyte character support. In the 1980s, the Bourne Shell was just 8-bit clean. - job-control. If you do not call "jsh", or if you switch off jobcontrol via "set +m" in a job shell, you have t...

trying to compile 2.2.3a on solaris 8 and getting the following: Is it supported on sol 8? after typing configure and after many lines i get: -----much deleted------ ecking how to get filesystem space usage checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs.fsize member (...

To whomever is interested, I have compiled and am running OpenSSH under NCR UNIX using the following procedure: 1. Compile and install zlib to the default location. gunzip zlib*.gz tar -xvfo zlib*tar cd zlib-* ./configure make make install 2. Compile and install openssl to the default location. gunzip openssl*.gz tar -xvfo openssl*tar cd openssl-*

Hi! I am trying to install samba 2.2 on a Sun and I'm getting this error: ./configure --prefix=/local --with-ssl checking how to get filesystem space usage checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs.fsize member (...

Hi, still got the problem of NT slow logon, what am I doing wrong? This is the situation: Samba running on Unixware 2.1.1, SVR4 and RedHad. Win95 and smbclient in any unix works fine. A win NT machine sees the workgroup, but browsing to it takes a LONG time ( 3 or 4 minutes or so..) and when the machines appear ( redhat, unixware and SVR4 ) it again takes a lot of time to log on, after that everything is fine. I got mail...

Hello all. I'm trying to create the rpm for Samba 2.2.5. I haven't uninstalled the other version as we are using it. I got the tar.gz from the Samba web site. I type # sh makerpms.sh and this is what I get this @ the end: checking statvfs64 function (SVR4)... no checking statvfs function (SVR4)... no checking for 3-argument statfs function (DEC OSF/1)... no checking for two-argument statfs with statfs.bsize member (AIX, 4.3BSD)... no checking for four-argument statfs (AIX-3.2.5, SVR3)... no checking for two-argument statfs with statfs.fsize member (...

...:45AM -0400, Scott Robbins wrote: > Wasn't Solaris, which for awhile at least, was probably the most popular > Unix, using ksh by default? Solaris /bin/sh was a real real dumb version of the bourne shell. Solaris included /bin/ksh as part of the core distribution (ksh88 was a part of the SVr4 specification) and so many scripts were written with #!/bin/ksh at the start (including tools like "patchadd"). Note Solaris had bugs in those tools because they didn't start "#!/bin/ksh -p" so if you had a $ENVFILE that included lines like "set -o noclobber" or h...

...d processes) to all orphaned process groups with a given tty/pty association when the session leader exits (TDI44BSDOS states that POSIX and 4.4BSD do this) - and any open file descriptors referring to the tty/pty in any processes that choose to continue running are revoked. - Whereas SVR4 doesn't do any of this and relies on the session leader to do its part and HUP/CONT its process groups. This part is not too clear because Uresh Vahalia mentions this very much in passing on page 108 of "Unix Internals." It is unclear whether closing a pty master causes t...

...t/Archive.h to print the archive symbol table for standard Unix .a files by slightly extending a code in llvm-nm, and the code crashed with wild segfault. It looks like the implementation in lib/Object/Archive.cpp assumes completely different symbol table format from what I have (which I believe is SVR4/GNU variant). Which archive formats does libObject support, and are there any plans to extend it? -- Alexey Samsonov, MSK -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120803/059a6a5d/attachment.html>

On 30 Jul 2014, at 21:29, Ulrich Weigand wrote: > The ELFv1 ABI is used on 64-bit big-endian Linux and AIX. There's one small difference between the two: with the 64 bit ELFv1/ SVR4 ABI, tail padding for structs passed by value is only performed in case the struct is larger than 8 bytes, while for AIX 64 bit it's always done. As an aside, on Darwin/ppc64 it's done if the aggregate's size is not in [1,2,4]. For an example, look at the assembly code for the pr...

...tting used a lot for constant loads; we can (and in fact must) use it as a scratch register, but we cannot rely on it surviving past the prologue of the target function. > AFAIK, the OS X dynamic linker does not "own" any registers. Here are > some links to the Darwin ABI... In SVR4 ABI, R11 and R12 can be used. In Darwin, these are reserved for uses associated with dynamic code generation and/or indirect call using dynamic code generation, which is conceptually related. The part that is not clear to me is whether a call made by a C function in Darwin is required to avoid R11...

The PowerPC backend on PPC64 for non-Darwin (SVR4 ABI) systems currently has a problem handling integer types smaller than 64 bits. This is because the ABI specifies that these types are zero-extended to 64 bits on the stack and the default logic provided in LegalizeDAG does not use that convention. Specifically, for these targets we have: s...

On Fri, 23 Mar 2012 09:50:12 +0100 Ivan Llopard <ivanllopard at gmail.com> wrote: > Hi Finkel, > > Le 23/03/2012 05:50, Hal Finkel a écrit : > > The PowerPC backend on PPC64 for non-Darwin (SVR4 ABI) systems > > currently has a problem handling integer types smaller than 64 bits. > > This is because the ABI specifies that these types are > > zero-extended to 64 bits on the stack and the default logic > > provided in LegalizeDAG does not use that convention. Specific...

> > according to the documentation the option ucode=scan should tell XEN to > > look for a microcode update in an uncompressed initrd. > > > > While I don?t use the Debian kernel the tools to generate the initrd are > > part of Debian. The command ?cpio -i < /boot/initrd.img-4.0.2-Dom0? > > creates the directory structure

> Message: 5 > Date: Mon, 26 Jan 2009 21:47:12 -0500 > From: "Jonathan S. Shapiro" <shap at eros-os.com> > Subject: [LLVMdev] PPC calling convention -- how to provide an > environment pointer? > To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu> > Message-ID: <1233024432.24380.11.camel at vmx> > Content-Type: text/plain > > This is