search for: buildability

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:

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

Hi All, I just posted a review with arcanist (which I'm fairly new to) and it included a build status. How it got there is totally opaque to me, but my workflow was: Using git+svn (following the setup in https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-git-svn) make a change, commit with 'git commit', create review with 'air diff'. It would be cool if

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

Hi All, The landed patch https://reviews.llvm.org/D38481 introduced the usage of CPU_COUNT defined in glibc sched.h header. I failed to find this symbol in sched.h of glibc version 2.5-24, so compilation just fails. /home/dolphin/merge-from-upstream-area/ws/pristine/lib/Support/Threading.cpp: In function 'unsigned int llvm::hardware_concurrency()':

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_BUILD project in the

Hello, Žiga > I would like to compile at least 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

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

...at PRs will build cleanly but it gets pretty complicated quickly. > But this would be a radical redesign of the LLVM bot system, and would > have to wait until we're done with the GitHub migration and can spend > a couple of years debating the use of PRs. :-) Heh. Fully guaranteeing buildability of a branch is not a trivial task and will take a LOT of thought and discussion. -David

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

I am wondering about updating the version of Spam Assassin on my CentOS 5 mail server. The current version, 3.3.1-4.el5 (stock RHEL version), 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

On Thu, Oct 23, 2014 at 1:13 PM, Timur Iskhodzhanov <timurrrr at google.com> wrote: > Yes it is. > Are you doing a Debug or Release build? > Using ninja? Release build, cmake + MSVC (not using ninja). Perhaps I have it configured stupidly; I have it as an out-of-tree folder, did: E:\llvm\crt_build>cmake -DLLVM_CONFIG_PATH=E:\llvm\2013\Debug\bin -G "Visual Studio 12"

Hi. As per[1], gcc-4.8 is the oldest supported *major* gcc version. But what about minor/patch versions? When https://reviews.llvm.org/D43779 was initially committed, a few[2][3] buildbots failed. As i have now looked into the issue: * but it is *REPRODUCIBLE* with gcc-4.8.4 and gcc-4.9.2 from debian oldstable (Jessie). * it is *NOT* reproducible with gcc-4.8.5 and gcc-4.9.3 from ubuntu 16.04,

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,

Canonicalizing to a masked store intrinsic is possible, but we might have to expand back to the load/shuffle/store sequence for targets that don't support masked store. And then you'd likely have to do the store splitting that I think is being requested for the original pattern anyway. But I'd like to step back to the premise - "LLVM seems to always generate vector instructions

Thank you very much for the feedback! What Chandler said about test-suite totally makes sense to me since it's also excluded from LLVM git monorepo. I will try to land benchmark library to LLVM core repo and update it to the latest version. I have not been doing much CMake/project structure before, but I'll start looking into that next week. I'll reach out to Dominic if anything goes