search for: unbuild

Greetings, A fresh install of 7 followed by a cvsup to 7.2-PRE on the 26th results in an inability to build Xorg on the system. A cvsup only an hour ago provides no solution. An attempt at the following: cd /usr/ports/x11/xorg-minimal make produces the following error: ... checking pkg-config files for X11 are available... yes checking for LIBDRM... yes checking for DRI2PROTO... yes checking

Just a "heads up". I tried to search mailinglist archives and wiki, but found no similar configurations. Dovecot is unbuildable with the following configuration: SunOS mail 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Fire-V210 cc: Forte Developer 7 C 5.4 2002/03/09 config.log output from ./configure is at: http://iso.ego.fi/misc/dovecot_1.0-test50.log I guess I'll have to bend over for GCC :) -- Toni Viemer? |...

...e no idea what CR is .. ask and people can help you on the list. Here is the info in the wiki: https://wiki.centos.org/AdditionalResources/Repositories/CR Any if you are wondering why not earlier (though, 2 days is pretty fast if you ask me) ...this timebomb bug rendered both the openssl updates unbuildable: https://bugzilla.redhat.com/show_bug.cgi?id=1335097 There where also a bugs where glutserfs, xmlgraphics-commons, and certmonger would not build. The full release of the entire 6.8 tree and isos is still some time (10-20 days) away, but we should have CR packages soon. Thanks, Johnny Hugh...

...goal of incubation is to eventually become part of the > llvm-project monorepo, I feel that being inside the monorepo should be > a goal early on. Actually that would be a big problem in practice, because it means that either: 1. random changes in the monorepo can put the incubator into an unbuildable state 2. people changing the monorepo need to somehow build and test and fix incubator projects Currently, in npcomp, we have a monorepo hash that we bump periodically. That means that people can follow our README and build our project at any point by checking out the right monorepo revision....

...= $wx_libs[/\S+libwx\S+_stc\S+/] +stc_lib = $wx_libs[/\S+lwx\S+_stc\S+/] since wx_libs has strings of the form -lwx_gtk2_*. There is no "lib" in there. The build is now proceeding. Stay tuned. Is the rakefile system unmaintained or something? Adoption will be a problem if wxruby is unbuildable out of the box in the "stable" release. _______________________________________________ wxruby-users mailing list wxruby-users@rubyforge.org http://rubyforge.org/mailman/listinfo/wxruby-users

...use it actually marks the merge as being a merge. That's the main reason why I think we ought to use a merge commit here. Additionally (and less importantly), I'm going to presume that many/most of the 2700 commits cannot actually be built. So, having a single merge commit within which the unbuildable sub-commits are contained will also make things better for autobuilders. > It's of course technically straightforward to push either "follow-on > commits" or a merge commit. > > I think there could be a benefit to having it as a "follow-on commits", > i...

...but they responded without it' is ambiguous and wrong in some cases (Reported by Rusty Newton) * ASTERISK-15434 - [patch] When ast_pbx_start failed, both an error response and BYE are sent to the caller (Reported by Makoto Dei) * ASTERISK-18105 - most of asterisk modules are unbuildable in cygwin environment (Reported by feyfre) * ASTERISK-24828 - Fix Frame Leaks (Reported by Kevin Harwell) * ASTERISK-24838 - chan_sip: Locking inversion occurs when building a peer causes a peer poke during request handling (Reported by Richard Mudgett) * ASTERISK-24825 - C...

...ple can help you on the > list. Here is the info in the wiki: > > https://wiki.centos.org/AdditionalResources/Repositories/CR > > Any if you are wondering why not earlier (though, 2 days is pretty fast > if you ask me) ...this timebomb bug rendered both the openssl updates > unbuildable: > > https://bugzilla.redhat.com/show_bug.cgi?id=1335097 > > There where also a bugs where glutserfs, xmlgraphics-commons, and > certmonger would not build. > > The full release of the entire 6.8 tree and isos is still some time > (10-20 days) away, but we should hav...

...and solution files for Visual Studio are all under the win32 directory. It uses the native Win32 API (see lib/System/Win32). The entire backend, except for a (very) few tools, builds natively. The front end cannot build this way because it's a hacked-up GCC, which is well known for being unbuildable with VC++. But that isn't really LLVM's problem; we can just distribute a pre-built llvm-gcc binary compiled with cygwin or mingw. Anyway, the usefulness of LLVM is not limited to compiling C/C++ code. > In fact, with regards to the specific "cannot unlink while open"...

I wish to transcode an AVI from 29fps to 15fps theora. I have tried many combinations. The nearest I have so far is to: 1) ffmpeg -i input.avi -f avi -vcodec rawvideo -acodec pcm_s16le -r 15 -ar 22050 -ac 1 intermediate.avi then 2) ./ffmpeg2theora-0.15.linux.bin -f avi -c1 -H 22050 -o out.ogg intermediate.avi This gives me an output I want, however, the intermediate uncompressed stage

On Nov 23, 2005, at 22:49, Jeff Cohen wrote: > News to me. I do it all the time. Notice the "win32" directory under > the root :) Okay, so I spoke about something that I don't really know about, since I don't use Windows. But what was the whole "Still can't compile backend of frontend on Windows" discussion about? My impression is that LLVM only builds

...but they responded without it' is ambiguous and wrong in some cases (Reported by Rusty Newton) * ASTERISK-15434 - [patch] When ast_pbx_start failed, both an error response and BYE are sent to the caller (Reported by Makoto Dei) * ASTERISK-18105 - most of asterisk modules are unbuildable in cygwin environment (Reported by feyfre) * ASTERISK-24828 - Fix Frame Leaks (Reported by Kevin Harwell) * ASTERISK-24838 - chan_sip: Locking inversion occurs when building a peer causes a peer poke during request handling (Reported by Richard Mudgett) * ASTERISK-24825 - C...

Evan Jones wrote: > On Nov 23, 2005, at 18:17, Reid Spencer wrote: > >>> So this comment means that I should attempt to theoretically support >>> Windows, and close the current archive file before updating it? >> >> If you use sys::Path, it is not "theoretically" supported, it is >> supported. > > > Well, except of course that it

For those that like to assist in the testing of rsync, the CVS version now defaults to doing an incremental file-list scan when it is recursing through the directories. This avoids keeping the whole file list in memory, and allows the transfer to start working on changed files before it has completed the recursive scan of the sending side. The code appears to be working well so far, but there

...but they responded without it' is ambiguous and wrong in some cases (Reported by Rusty Newton) * ASTERISK-15434 - [patch] When ast_pbx_start failed, both an error response and BYE are sent to the caller (Reported by Makoto Dei) * ASTERISK-18105 - most of asterisk modules are unbuildable in cygwin environment (Reported by feyfre) * ASTERISK-24828 - Fix Frame Leaks (Reported by Kevin Harwell) * ASTERISK-24751 - Integer values in json payload to ARI cause asterisk to crash (Reported by jeffrey putnam) * ASTERISK-24838 - chan_sip: Locking inversion occurs when...

...but they responded without it' is ambiguous and wrong in some cases (Reported by Rusty Newton) * ASTERISK-15434 - [patch] When ast_pbx_start failed, both an error response and BYE are sent to the caller (Reported by Makoto Dei) * ASTERISK-18105 - most of asterisk modules are unbuildable in cygwin environment (Reported by feyfre) * ASTERISK-24828 - Fix Frame Leaks (Reported by Kevin Harwell) * ASTERISK-24751 - Integer values in json payload to ARI cause asterisk to crash (Reported by jeffrey putnam) * ASTERISK-24838 - chan_sip: Locking inversion occurs when...

https://bugs.freedesktop.org/show_bug.cgi?id=50280 Bug #: 50280 Summary: Mesa 8.0.3 fails to build dri/nouveau against libdrm 2.4.34 Classification: Unclassified Product: Mesa Version: 8.0 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority:

I think it would probably make the most sense to land this as a single merge-commit (from the 2700-commit rewritten history you've created) onto llvm-project master, rather than as 2700 individual toplevel commits to master. (Which means: disable the merge-commit prohibition in the github configuration, temporarily, push this commit, and then enable it again). On Tue, Dec 17, 2019 at 5:10 PM

Hi, Since I''ve installed ruby and ruby-gems from source, then installed facter and puppet as gems, I don''t get the usual startup scripts shipped with RPMs. Rebuilding the ruby RPM is painful, mostly because Red Hat (and pretty much every vendor) have this tendency to include random files and patch the living daylights out of a perfectly good source package so that converting

Per the recent (seeming) consensus regarding incubating new projects under the LLVM organization, I would like to trial the process by requesting to incubate mlir-npcomp <https://github.com/google/mlir-npcomp>. The project is still quite young and has been primarily developed part time by myself and Sean Silva over the last ~2 months. We set it up following discussion of a Numpy/Scipy op set