similar to: [LLVMdev] Changing Where Man Pages Live

Displaying 20 results from an estimated 90000 matches similar to: "[LLVMdev] Changing Where Man Pages Live"

2012 Jan 25
1
man pages conflicting?
Just got this message after an autoupdate on my 5.x system.. should I be worried? Hi, This is the automatic update system on mail.<xxx>.com. There was a problem updating the system. The following error message was reported: ["[('file /usr/share/man/man1/ca.1ssl.gz from install of openssl-0.9.8e-20.el5_7.1.x86_64 conflicts with file from package openssl-0.9.8e-20.el5.i686',
2012 Oct 12
3
[PATCH] explicitly use escaped minus in man pages
--- man/man1/unicorn.1 | 32 ++++++++++++++++---------------- man/man1/unicorn_rails.1 | 34 +++++++++++++++++----------------- 2 files changed, 33 insertions(+), 33 deletions(-) diff --git a/man/man1/unicorn.1 b/man/man1/unicorn.1 index 0b496af..749272a 100644 --- a/man/man1/unicorn.1 +++ b/man/man1/unicorn.1 @@ -4,7 +4,7 @@ unicorn - a rackup-like command to launch the Unicorn HTTP
2013 Dec 07
2
[PATCH 1/2] Fix installing man-pages from out-of-tree build
--- po-docs/ja/Makefile.am | 6 +++--- po-docs/uk/Makefile.am | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/po-docs/ja/Makefile.am b/po-docs/ja/Makefile.am index da1bcc3..820f91a 100644 --- a/po-docs/ja/Makefile.am +++ b/po-docs/ja/Makefile.am @@ -160,8 +160,8 @@ $(podfiles): # XXX Can automake do this properly? install-data-hook: $(MKDIR_P)
2007 Oct 09
0
Bug#391606: xen-utils-common: doesn't ship referenced man pages
Hi, the package currently contains /usr/share/man/man1/xm.pod.1.gz /usr/share/man/man5/xmdomain.cfg.pod.5.gz which isn't exactly what we want. bye, Roland
2013 Oct 12
0
[LLVMdev] "target-features" and "target-cpu" attributes
FYI: http://lists.cs.uiuc.edu/pipermail/llvmdev/2013-October/066389.html Please read and let me know you comments. -bw On Oct 11, 2013, at 2:47 PM, Dmitry Babokin <babokin at gmail.com> wrote: > Looking forward to these changes! Thanks for working on it. > > > On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I
2013 Oct 11
2
[LLVMdev] "target-features" and "target-cpu" attributes
Looking forward to these changes! Thanks for working on it. On Fri, Oct 11, 2013 at 10:32 PM, Bill Wendling <isanbard at gmail.com> wrote: > Hi Dmitry, > > I can try my best, but it would be a bit tricky to get it all finished by > then... > > -bw > > On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > > Bill, > > Are there
2011 Jan 13
0
Formatting bug in rsync man page? (man -k, whatis, catman -w)
Hi guys, I'm new to this mailing list as I just came across a small problem after installing the rsync package on one of our Solaris 10 machines. I installed rsync package SMCrsync v3.0.7 SPARC and although command man rsync worked, man -k rsync and whatis rsync did not despite the fact that I had run a catman -w to rebuild the windex databases. After reading the catman man page, I suspected
2011 Jan 31
1
DO NOT REPLY [Bug 7941] New: Formatting bug in rsync man page? (man -k, whatis, catman -w)
https://bugzilla.samba.org/show_bug.cgi?id=7941 Summary: Formatting bug in rsync man page? (man -k, whatis, catman -w) Product: rsync Version: 3.0.7 Platform: Sparc OS/Version: Solaris Status: NEW Severity: minor Priority: P3 Component: core AssignedTo: wayned at samba.org
2014 Aug 21
6
[LLVMdev] [3.5 Release] Release Candidate 3 Now Available
The third 3.5 release candidate is now available. Please pick up sources and binaries here: https://llvm.org/pre-release/3.5 Run it through its phases and report any bugs you find! Share and enjoy! -bw
2007 Sep 24
4
[LLVMdev] Compilation Failure
On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > On Sep 24, 2007, at 3:07 PM, Bill Wendling wrote: > >> A debug or release build? >> >> -bw > > Both, actually. Weird. I see a potential problem, though. The code is like this: void dumpToDOUT(SparseBitVector<> *bitmap) { dump(*bitmap, DOUT); } where dump expects an llvm::OStream& for the
2008 Jan 31
0
[LLVMdev] Some questions about live intervals
Hi Roman, > I already started work on the implementation of this algorithm and have > a few hopefully rather simple questions: > > 1) What is the easiest way to understand which MBB a given instruction > index belongs to? All the required information is available in the > MBB2IdxMap of the LiveIntervalAnalysis class. Would it be useful to add > a small function
2005 Feb 27
3
Cygwin-bug#20050227T2233: liboggz: Missing manual pages - oggzinfo, oggzed, oggzdiff
Package: liboggz Version: 0.9.0 Status: Severity: normal [Keep CC if you reply, I'm nt in this list] After porting the package to Cygwin, some binaries do not have accompnying manual pages. ... .inst/usr/share/man/man1/oggzdump.1.gz .inst/usr/share/man/man1/oggzdiff.1.gz .inst/usr/share/man/man1/oggzmerge.1.gz .inst/usr/share/man/man1/oggzrip.1.gz .inst/usr/include .inst/usr/include/oggz
2013 Oct 11
0
[LLVMdev] "target-features" and "target-cpu" attributes
Hi Dmitry, I can try my best, but it would be a bit tricky to get it all finished by then... -bw On Oct 11, 2013, at 4:10 AM, Dmitry Babokin <babokin at gmail.com> wrote: > Bill, > > Are there any chances that you complete it before 3.4 is branched? > > > On Thu, Oct 10, 2013 at 10:16 PM, Bill Wendling <isanbard at gmail.com> wrote: > On Oct 10, 2013, at
2007 Sep 25
2
[LLVMdev] Compilation Failure
On 9/25/07, Daniel Berlin <dberlin at dberlin.org> wrote: > On 9/24/07, Bill Wendling <isanbard at gmail.com> wrote: > > On Sep 24, 2007, at 3:15 PM, Dale Johannesen wrote: > > > > Weird. I see a potential problem, though. The code is like this: > > > > void dumpToDOUT(SparseBitVector<> *bitmap) { > > dump(*bitmap, DOUT); > > } >
2009 Jul 15
3
[LLVMdev] please stabilize the trunk
On Wed, Jul 15, 2009 at 3:43 PM, Eli Friedman<eli.friedman at gmail.com> wrote: > On Wed, Jul 15, 2009 at 3:01 PM, Bill Wendling<isanbard at gmail.com> wrote: >> The core problem, in my opinion, is that people *don't* pay attention >> to the build bot failure messages that come along. > > That's largely because of the number of false positives. > There
2009 Jan 27
2
[LLVMdev] RFC: -fwritable-strings Change
On Tue, Jan 27, 2009 at 1:15 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > On Tue, Jan 27, 2009 at 1:00 PM, Bill Wendling <isanbard at gmail.com> wrote: >> Even with C code, we place a null string in a writable >> section, which isn't correct. > > You could say that, but it's not really wrong... say you had a 10 > kilobyte struct that was all
2008 Oct 26
1
[LLVMdev] Error while creating ExecutionEngine
Thanks Bill! But it does not work. I get the error given below when I try to load LLVMExecutionEngine.o in the opt command. Error opening '../../../build/Release/lib/LLVMExecutionEngine.o': ../../../build/Release/lib/LLVMExecutionEngine.o: only ET_DYN and ET_EXEC can be loaded -load request ignored. Any ideas?? Please help me out here. Thanks, Bhavani --- On Sun, 10/26/08, Bill
2008 Dec 09
1
[LLVMdev] [PATH] Add sub.ovf/mul.ovf intrinsics
Hi, The add.with.overflow instrinsics don't seem to work with constant arguments, i.e. changing the call in add-with-overflow.ll to: %t = call {i32, i1} @llvm.sadd.with.overflow.i32(i32 0, i32 0) causes the following exception when running the codegen tests: llc: DAGCombiner.cpp:646: void<unnamed>::DAGCombiner::Run(llvm::CombineLevel): Assertion `N->getValueType(0) ==
2008 Dec 09
0
[LLVMdev] [PATH] Add sub.ovf/mul.ovf intrinsics
Applied. Thanks, Zoltan! -bw On Tue, Dec 9, 2008 at 1:12 PM, Zoltan Varga <vargaz at gmail.com> wrote: > Hi, > > Attached is the final version of the patch, adding the requested > FIXME. If this is ok, can > somebody check it in ? > > thanks > > Zoltan > > On Tue, Dec 9, 2008 at 9:58 PM,
2014 Aug 25
2
[LLVMdev] [cfe-dev] [3.5 Release] Release Candidate 3 Now Available
The ARM binaries seem to be corrupt. Although correctly signed, the xz file seems to be truncated arm7% unxz < clang+llvm-3.5.0-rc3-armv7a-linux-gnueabihf.tar.xz | wc -c unxz: (stdin): Unexpected end of input 133214381 M.E.O. On Aug 21, 2014, at 10:56 AM, Bill Wendling <isanbard at gmail.com> wrote: > Ahem. And now for the correct URL: > >