search for: buildabl

https://bugzilla.mindrot.org/show_bug.cgi?id=2640 Bug ID: 2640 Summary: Make gnome-ssh-askpass2 buildable with GTK+ 3 Product: Portable OpenSSH Version: 7.3p1 Hardware: All OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: Miscellaneous Assignee: unassigned-bugs at mindrot.org...

I've noticed that some reviews, but not others, show up in Phab with a "buildable" indication in a "Diff Detail" box, just below the summary. Can somebody describe what that's about? Most interesting might be why it's there only sometimes, also what sort of "build" this indication is reporting. Thanks, --paulr

Author: wesolows Repository: /hg/zfs-crypto/gate Revision: f0ba1ee4d57611c825dcb431c1669a592147e7f9 Log message: 6242262 ON should be buildable with gcc (fix build noise) Files: update: usr/src/tools/scripts/nightly.sh

...uildbot hooks in Phabricator. But > that may just be wishful thinking :). > > On Wed, Nov 8, 2017 at 11:16 PM, Robinson, Paul via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> I've noticed that some reviews, but not others, show up in Phab >> with a "buildable" indication in a "Diff Detail" box, just below >> the summary. >> >> Can somebody describe what that's about? Most interesting might >> be why it's there only sometimes, also what sort of "build" this >> indication is reporting. >&...

Would Studio 10, or Studio 11 be preferable to build? This message posted from opensolaris.org

// hoping this is sufficiently on-topic // php-driven, markdown-aware, open source wiki/cms that has some degree of version control, a flexible system for privs/access control, is installable (or buildable) on OS X and has an easy installer for windows ?

> I may be missing something obvious, but what is `vector` defined as here? Can you provide a buildable example? Sorry, I should provide a cross-platform version using vector extension of frontend :) `vector int` is a vector extension on PowerPC, which is enabled if you set target to PowerPC platforms. Example below should be successfully compiled in any platform: typedef float v4sf __attribut...

...b/Support/Threading.cpp: In function 'unsigned int llvm::hardware_concurrency()': /home/dolphin/merge-from-upstream-area/ws/pristine/lib/Support/Threading.cpp:80:26: error: 'CPU_COUNT' was not declared in this scope return CPU_COUNT(&Set); ^ It is buildable with newest version of glibc. I tried to find a requirements for glibc version in LLVM documentation but failed. So I wonder whether there is such requirement or not. Could anyone point me to this documentation? I'm trying to understand whether patch is wrong which relies on availability of l...

Hello! I'm wondering whether compiler-rt is expected to be buildable with MSVC 2013. I am currently getting: Error 49 error LNK2005: _free already defined in asan_malloc_win.obj E:\llvm\crt_build\lib\asan\MSVCRT.lib(MSVCR120.dll) Which seems to be the only issue (aside from ~50 warnings, which I'll happily work on cleaning up). I get this when I build the ALL...

...ast x86 target as well as Fibonacci example > (to test if it really works). In order to do so, I may need some hints: > 1) How to generate X86GenRegisterNames.inc required by x86 (or any other > files, if there are any other) It's being built via tablegen > 2) Is bugpoint project buildable on windows? Yes. > 3) Which other tools can be compiled for windows? All, except lto. -- With best regards, Anton Korobeynikov. Faculty of Mathematics & Mechanics, Saint Petersburg State University.

On Sat, 4 Nov 2006, Reid Spencer wrote: > On Sun, 2006-11-05 at 00:27 +0300, Anton Korobeynikov wrote: > >>> 2) Is bugpoint project buildable on windows? >> Yes. > > Really? Yep. > When did that happen? Apparently Dec 22, 2005. Some rspencer guy did it: http://llvm.org/bugs/show_bug.cgi?id=351 > Are we now just execing the sub-processes > instead of forking them? yep, :) -Chris -- http://nondot.org/sabre/ h...

<paul.robinson at sony.com> writes: > Systems that I've seen will funnel all submitted PRs into a single queue > which *does* guarantee that the trial builds are against HEAD and there > are no "later commits" that can screw it up. If the trial build passes, > the PR goes in and becomes the new HEAD. The downside of a system like this is that when changes are

On Mon, 23 Feb 2015, Kevin Brott wrote: > Stock - Debian GNU/Linux 7.8 (wheezy) - all tests passed > > > build failure on: > * AIX 6.1 (6100-09-03-1415) IBM XL C/C++ Compiler (11.1.0.16) > * AIX 7.1 (7100-03-04-1441) IBM XL C/C++ Compiler (12.1.0.6) > > ./configure && make tests > > -DHAVE_CONFIG_H -c ssh_api.c -o ssh_api.o > "ssh_api.c",

Apparently this didn't/doesn't build on FreeBSD by default...or is it "doesn't build at all". If it is buildable, what should I do to build it, as without it...see wiki: http://wiki.samba.org/index.php/Samba4/Winbind Cheers, TMS III

...ersion), has been 'leaking' recently. I suspect I need some newer match rules to detect some of the newer flavors of spam. I see that in rpmforge's extras repo is version 3.3.2-4.el5.rfx -- is this version worth installing? Are there even newer versions either available for CentOS 5 (or buildable under CentOS 5)? Or is there a collection of match rules available for the newer flavors of spam than can just be dropped into /etc/mail/spamassassin/local.cf? I am not ready just yet to migrate my server to CentOS 6 (but that is something I'll probably do at some point). -- Robert Heller...

...make -DLLVM_CONFIG_PATH=E:\llvm\2013\Debug\bin -G "Visual Studio 12" ..\compiler-rt Opened up the solution, hit Build All. ~Aaron > > 2014-10-23 9:51 GMT-07:00 Aaron Ballman <aaron at aaronballman.com>: >> Hello! I'm wondering whether compiler-rt is expected to be buildable >> with MSVC 2013. I am currently getting: >> >> Error 49 error LNK2005: _free already defined in asan_malloc_win.obj >> E:\llvm\crt_build\lib\asan\MSVCRT.lib(MSVCR120.dll) >> >> Which seems to be the only issue (aside from ~50 warnings, which I'll >>...

...2 from debian oldstable (Jessie). * it is *NOT* reproducible with gcc-4.8.5 and gcc-4.9.3 from ubuntu 16.04, So it looks like it was a gcc problem, and it is resolved in latest minor/patch versions. So is there some more specific guideline on minor/patch version requirements? Do we want LLVM to be buildable with all gcc 4.8/4.9 versions? Or is it okay to only build with the latest point versions, that contain the fix? (Regardless, it would be good to have the answer in [1]) Roman. [1] http://llvm.org/docs/GettingStarted.html#host-c-toolchain-both-compiler-and-standard-library [2] http://lab.llvm.o...

Hi there, I notice that LLVM seems to always generate vector instructions for vector operations in C, even it's just simple stores: void foo(vector int* c) { (*c)[0] = 1; (*c)[1] = 2; } %0 = load <4 x i32>, <4 x i32>* %c, align 16 %vecins1 = shufflevector <4 x i32> <i32 1, i32 2, i32 undef, i32 undef>, <4 x i32> %0, <4 x i32> <i32 0, i32 1, i32 6,

...sense to canonicalize this to a masked store? > > Nemanja > > On Thu, Sep 26, 2019 at 10:59 PM Qiu Chaofan via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> > I may be missing something obvious, but what is `vector` defined as >> here? Can you provide a buildable example? >> >> Sorry, I should provide a cross-platform version using vector >> extension of frontend :) `vector int` is a vector extension on >> PowerPC, which is enabled if you set target to PowerPC platforms. >> Example below should be successfully compiled in any...

...> > On Sun, 29 Jul 2018, 00:34 Chandler Carruth via cfe-dev, < > cfe-dev at lists.llvm.org> wrote: > >> I'm happy to have this in the main LLVM repositiory. >> >> The version in the test suite should likely stay there because the test >> suite should be buildable w/o LLVM itself -- it is largely a distinct >> thing. We re-use lit, but not much else from LLVM, and we wouldn't want to >> install the benchmark library the way we do lit. >> >> One interesting point: we should have some way of running the in-tree >> benchmarks,...