similar to: Looking for SElinux help

thanks for the reply. On 08/23/2015 01:26 PM, Rowland Penny wrote: > On 23/08/15 17:10, Robert Moskowitz wrote: >> After years of delays and side trips, I really am going to dive in >> and build my own Samba server. And I have a few questions. >> >> All of my servers will be ARM. The main hardware will be Cubieboards >> (2 and truck). They will be running

After years of delays and side trips, I really am going to dive in and build my own Samba server. And I have a few questions. All of my servers will be ARM. The main hardware will be Cubieboards (2 and truck). They will be running Centos-7 once the development is finished. For now I am using Fedora 22 arm. My backup file server will be a pogoplug (armv5) with Redsleeve 7.1. My current

On 23/08/15 17:10, Robert Moskowitz wrote: > After years of delays and side trips, I really am going to dive in and > build my own Samba server. And I have a few questions. > > All of my servers will be ARM. The main hardware will be Cubieboards > (2 and truck). They will be running Centos-7 once the development is > finished. For now I am using Fedora 22 arm. My backup

I am trying to override the mac addr. Now this is on an armv7 actually running the F19 kernel and Redsleeve 6, but it SHOULD be standard Centos6 ifcfg-eth0 content. Of course RSEL does not start with a ifcfg-eth0 file, letting network services do all the work, so I am starting from scratch, using the file from one of my C6 boxes with static addressing. My file has in it:

On 26 February 2013 16:14, David Blaikie <dblaikie at gmail.com> wrote: > I'm not sure I understand your question. Fail tests continue to run so we > find out if they start passing as seems to be the case here. If llvm is now > free of whatever bugs caused these things to fail (ie: it's not just that > these stopped failing on this hardware but in all environments the

The RSEL Project has working builds of EL6 and 7 out for embedded ARM devices like the raspberry pi. http://www.redsleeve.org You need to dig through their wiki four instructions your several devices. Am 14.05.2015 23:46 schrieb "Johnny Hughes" <johnny at centos.org>: > On 05/14/2015 04:19 PM, Always Learning wrote: > > > > On Thu, 2015-05-14 at 13:51 -0700, John R

No change after running this and trying both: system network restart ifdown eth0; ifup eth0 Still having an IPv6 addr. The box has been up for 140 days. Would like to keep it running... This box is really Redsleeve 6, which is the port of Centos 6 to arm. The kernel I am using is the F19 kernel. All of this MIGHT be contributing to things not working as they would on a 'normal'

On Jun 22, 2011, at 3:16 PM, Renato Golin wrote: > On 22 June 2011 11:49, Damjan Marion <damjan.marion at gmail.com> wrote: >> # /opt/llvm/bin/clang -S -ccc-host-triple arm-unknown-freebsd -mcpu=arm926ej-s -mfloat-abi=soft -v -o rrx.S rrx.c > > Even though you specified cpu as arm9, it's probably generating > generic ARM IR (use -emit-llvm -S and see), which defaults

How about, in your /etc/sysconfig/network file adding or editing the line for IPV6 to be: NETWORKING_IPV6=no and then try a 'service network restart' and see what you get. Chris On Mon, Mar 9, 2015 at 11:52 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: > No change after running this and trying both: > > system network restart > > ifdown eth0; ifup eth0

Moreover,  ../llvm-gcc4.2-2.6.source/configure --prefix=`pwd`/../install --program-prefix=llvm- --enable-llvm=/home/LLVM/llvm-2.6/ --enable-languages=c,c++  --with-gnu-ld=/home/arm/bin/arm-elf-ld --with-gnu-as=/home/arm/bin/arm-elf-as  --with-arch=armv7  --target=arm-elf and then make target=arm-elf gives the following error: Unknown arch used in --with-arch=armv7 Thanks. --- On Sun,

On 8 December 2012 19:10, Amir Yazdanbakhsh <amir.yazdanbakhsh at gmail.com> wrote: > Hi, > > I've installed clang version 3.3 on ubuntu. > I want to cross-compile a C code into ARM (preferably) ARMv7. I want to get > both assembly code and binary. Can anyone help me what are the steps which > should I take? clang -triple arm-none-eabi (or many other variations

Evan, > I'm the code owner of LLVM codegen and targets. I'm also the one of main developers on the original ARM target. That means, I would make the decisions on major development on ARM target if there are decisions to be made. > > But my role is very different from what people are looking for in this thread. To properly qualify a target like ARM which are supported on many

Hello, Nathan >   I may need to clarify, sparcv9-* is used for the SPARCV9 ABI (ie 64-bit ABI), rather than the SPARCV9 CPU per se. It serves the same purpose as x86_64-* and powerpc64-*, which is to say it's associated with -m64, not -mcpu=v9 (although unsurprisingly -m64 does require a V9 or later CPU). I may be wrong, but I think the only distinction in ARM is between arm and thumb

Hello, I wanted to know about the reasons Apple dropped the support for "arm" target in its ld64. After searching in the sourcecode I found out that ld64 supports armv4 armv5 armv6 armv7 and its subtypes. The code shows that -force_cpusubtype_ALL for ARM targets is no more supported in "src/ld/options.cpp") and static const ARMSubType ARMSubTypes[] doesn't include

Thanks for your tips. But I'm still getting errors. .../llvm-gcc4.2-2.6.source/configure --prefix=`pwd`/../install --program-prefix=llvm- --enable-llvm=/home/LLVM/llvm-2.6/ --enable-languages=c,c++  --with-gnu-ld=/home/arm/bin/arm-elf-ld --with-gnu-as=/home/arm/bin/arm-elf-as  --with-cpu=cortex-a8  --target=arm-elf Errors: >> checking for g++ that supports -ffunction-sections

Hi Renato, On 06/25/12 12:13 AM, Renato Golin wrote: > Hi Karel, > > I understand this patch has already been merged (to 3.0), so don't > take my question as stopping the merge to head, I'm just making sure I > got it right... The rest looks correct. > > + CCIfType<[v2f64], CCAssignToReg<[Q4, Q5]>>, > + CCIfType<[f64], CCAssignToReg<[D8, D9,

On 12/08/2014 09:11 PM, Robert Moskowitz wrote: > I have a Samba server here with 4 users and 4 XP systems. Kind of > small, but it does the job. It is running as a PDC with roaming > profiles. I should note that I left professionally supporting Windows > networking around the time XP came out, so I have maintained an > NTDomain through a number of incarnations (NT, Win2000,

I recompiled the LLVM-gcc with these options: .../llvm-gcc4.2-2.6.source/configure --prefix=`pwd`/../install --program-prefix=llvm- --enable-llvm=/home/LLVM/llvm-2.6/ --enable-languages=c  --disable-libssp  --with-gnu-ld --with-gnu-as  --with-arch=armv7-a  --target=arm-elf It compiles successfuly. make install. But when compiling a file : llvm-gcc a.c Assembler messages: Fatal error: Invalid

Hi, Although Im dutch too, Ill write this in english. I got a similar problem then the one on the helpforum. Ill paste my setup first server tincd.conf ---- ListenPort = 8089 MyOwnVPNIP = 192.168.100.1/24 #VpnMask = 255.255.255.0 TapDevice = /dev/tap0 Passphrases=/usr/local/etc/tinc/passphrases server tapdev ---- tap0 Link encap:Ethernet HWaddr FE:FD:C0:A8:6F:01 inet

On 29 June 2012 17:46, Karel Gardas <karel.gardas at centrum.cz> wrote: > Yes and no. Shortly: original GHC/ARM/LLVM port was done by Stephen on > ARMv5/Qemu IIRC. I've later added whole VFP support and ARMv7 support. The > code in GHC is properly #ifdefed, so if there is no VFP available on pre > ARMv6, then it's not used. ie. GHC STG floating points regs are then >