search for: dot1

On 29 December 2015 at 08:08, Erik de Castro Lopo <mle+la at mega-nerd.com> wrote: > I would suggest: > > #if SIZEOF_VOIDP == 8 I believe this is not portable. At least on my machine ("4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)") it's not defined. Probably this one comes closest: #define __SIZEOF_POINTER__ 8 Riggs

Hello, I am trying to get a time derivative on a plot title. I prefer to have it in the form \dot{s_i}, but \partial s_i/\partial t would be O.K. In the graphics demo I cannot find either a dot or a partial equivalent. Thanks, John. -- ========================================== John Janmaat Department of Economics Acadia University, Wolfville, NS, B0P 1X0 (902)585-1461 All opinions stated

...312:14: error: request for member ‘getValue’ in ‘fe’, > >which is of non-class type ‘int’ > >if (fe.getValue() == StaleFileEntry) { > >^ Are you sure this is the 3.4.1 source? This doesn't seem to match what is in SVN: https://llvm.org/viewvc/llvm-project/cfe/tags/RELEASE_34/dot1-final/lib/Basic/FileManager.cpp?revision=208032&view=markup -Tom > > solved by adding -std=c++11 to Makefile.config > > > Second one: > > Compilation of "SmallPtrSet.cpp" seems to be broken ... > Solved by removing the conditional compile by > > #i...

Hi I am new to this mailing list.we encounter a problem in our network,we have a samba 4 as an domain controller . for deploying dot1.x(IEE802.1x) in our network our firewall team run a windows CA Server 2012 R2 to work with EAP-ttls protocol. It generate a CA for domain controllers that should be imported in trusted certification authorities that i imported with rsat console in this directory . After that the dc (that here is...

...and, so that release testers can do that seamlessly. Currently, we have "rcN" and "final", we should move to "rcN.M" and "dotN" or something similar, to account for the dot releases... So: rc0.1 -> rc0.2 -> rc0.3 -> dot0 -> rc1.1 -> ... -> dot1 -> ... So that, in the script, we chose: "-release 3.4 {-rc2.1 or -final}| and the script will checkout the correct tag of the correct branch. Of course, to not disrupt the current release process, "-rc1" would have to alias to "-rc0.1" and "-final" aliasing...

I've just read about the 3.4.1 point release, but there seems to be no way to track these in the Git archives, no tags, no branches. Am I missing something? Bas -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140512/295256a1/attachment.html>

Hi, A few months ago, I mentioned I was interested in helping to make dot releases for LLVM 3.3. Now that 3.3 has been released, I would like to kick off the process of collecting bug fixes and merging them into the 3.3 branch. I reviewed the previous discussion about dot releases: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-April/060821.html and I've come up with the following dot

FreeBSD 9.3 Dovecot 2.25 (7be1766) I'm trying to install Dovecot2-pigeonhole-0.4.14_2 from ports. Get an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" With options MAKE_JOBS_UNSAFE=yes: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" *** [edit-mail.lo] Error code 1 Stop in

In stream_encoder.c there's the following code: #if defined FLAC__CPU_X86_64 /* and other 64-bit arch, too */ if(mean <= 0x80000000/512) { /* 512: more or less optimal for both 16- and 24-bit input */ #else if(mean <= 0x80000000/8) { /* 32-bit arch: use 32-bit math if possible */ #endif A) How to properly check for 64-bit architectures? I can check for "defined

...ATED -fno-strict-aliasing' 'LDFLAGS= -L/usr/local/lib -Wl,-rpath,/usr/local/lib/heimdal:/usr/lib -fstack-protector' 'LIBS=' 'CPPFLAGS=-isystem /usr/local/include -DLIBICONV_PLUG' 'CPP=cpp' compiled by CLANG 4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032) compiled with OpenSSL version: OpenSSL 1.0.1p-freebsd 9 Jul 2015 linked to OpenSSL version: OpenSSL 1.0.1p-freebsd 9 Jul 2015 compiled with libxml2 version: 2.9.3 linked to libxml2 version: 20903 When setting up my environment, I mostly followed the tutorial found here: https://for...

...47 AM, Alvin Starr wrote: > I addressed the fix to Jim but I should have addressed it to you. > > > Try systemctl disable xendomains.service > > It is conflicting with libvirtd.service. > I found it by using > "systemd-analyze dot libvirtd.service | dot -Tgif > /tmp/dot1.gif" > > > It looks like libvirt-daemon-driver-xen or > libvirt-daemon-driver-libxl should disable the xendomains.service > > > On 07/26/2017 06:46 AM, G Crowe wrote: >> Jim, >> Thanks for that, I had manually installed >> libvirt-daemon-driver-xe...

Hello! I was trying to optimize our automatically generated backend for Open RISC and for this purpose I went through the gcc torture testsuite. There are many programs that are better optimized by LLVM, but some are much better optimized by gcc 4.9. The main limitations were is loop unrolling and structures handling. Differences can be best seen e.g. when compiling for an

Jim, Thanks for that, I had manually installed libvirt-daemon-driver-xen, but also needed to install libvirt-daemon-driver-libxl. I can now create VMs and convert config formats. However the daemon still fails to start on bootup. It starts fine when I manually start it with "systemctl start libvirtd" but setting it to autostart with "systemctl enable libvirtd" seems

...m but I should have addressed it to you. >>> >>> >>> Try systemctl disable xendomains.service >>> >>> It is conflicting with libvirtd.service. >>> I found it by using >>> "systemd-analyze dot libvirtd.service | dot -Tgif > /tmp/dot1.gif" >>> >>> >>> It looks like libvirt-daemon-driver-xen or >>> libvirt-daemon-driver-libxl should disable the xendomains.service >>> >>> >>> On 07/26/2017 06:46 AM, G Crowe wrote: >>>> Jim, >>>> Than...

Hi, I am trying to upgrade my Xen host (Dom0) and are having troubles getting it to work. I think that it has booted into a kernel that supports Xen (running 'xl info' does list some Xen capabilities), but I have three problems (that I have found so far). Firstly, the "libvirtd" daemon doesn't start on bootup (and as a result all 'virsh' commands fail). It

...rk of The FreeBSD Foundation. Sep 17 11:25:39 romulus kernel: FreeBSD 10.2-RELEASE #0 r286666: Wed Aug 12 15:26:37 UTC 2015 Sep 17 11:25:39 romulus kernel: root at releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 Sep 17 11:25:39 romulus kernel: FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Sep 17 11:25:39 romulus kernel: CPU: Intel(R) Xeon(R) CPU?????????? E5462? @ 2.80GHz (2800.15-MHz K8-class CPU) Sep 17 11:25:39 romulus kernel: Origin="GenuineIntel"? Id=0x1067a? Family=0x6? Model=0x17? Stepping=10 Sep 17 11:25:39 romulus kernel: Features=0xbfebfbff...

Ok, So this is really more of an observation than anything else.? I had a FreeBSD 10.1 server that was running great. Some SSL issue came up, or I upgrade Dovecot in ports - something occurred and the machine started rebooting randomly.? It would run for 2 weeks, then reboot.? It might run for 5 days and then reboot. So I started doing more FreeBSD upgrades, thinking it was a kernel issue. The