similar to: Building IceS 0.4

Displaying 20 results from an estimated 2000 matches similar to: "Building IceS 0.4"

2014 Nov 25
1
Building IceS 0.4
I wound up finding and using an IceS augmentation called Centova Cast, which built, made and installed without a single error on my 64-bit system. It's IceS 0.4 with a couple additions. It's running now and behaving as it should, so this might be a solution for you as well. The install script is intense. It downloads everything you need, resolves dependencies, installs them, logs
2014 Nov 24
0
Building IceS 0.4
Somehow I had the impressions that IceS 0.4 Either would not compile under a 64 bit OS Or was not compatible with a 64 bit OS In General I would Love to hear I Was Wrong.... That Ices 2 Sends ogg streams I can handle But that it Won't Read mp3 makes it Non-viable for me I can't afford to replace the extensive mp3 Library ----- Original Message ----- From: "Steve Matzura"
2004 Aug 06
1
problem installing Icecast
I'm trying to install Icecast in my home directory using the method described in the following doc under the heading "Customized compilation." http://melmoth.dyndns.org/stream/doc/x145.html However, when I run the autogen.sh script for ices, I get the following messages: checking for pkg-config... /usr/bin/pkg-config configure: /usr/bin/pkg-config couldn't find libshout. Try
2020 Feb 19
2
test post1
Hi Everyone, Just a quick test. Been trying to get back on the list for years and finally looks like there's a proverbial light at the end of the samba list tunnel! Phil
2008 Aug 26
2
Error while compiling Ices 0.4
Dear All, I am sorry if this mail has already been posted to the mailing list. I am trying to cross compile Ices 0.4 for my ARM target board in ubuntu 8.04 but the configure script is terminating with the error of not being able to find an usable libshout. ..... checking for pkg-config... /usr/bin/pkg-config checking shout/shout.h usability... yes checking shout/shout.h presence... yes
2012 Apr 30
4
[LLVMdev] [RFC] Encoding Compile Flags into the IR
On Apr 30, 2012, at 1:00 PM, dag at cray.com wrote: > Bill Wendling <wendling at apple.com> writes: > >> Link-Time Optimization has a problem. We need to preserve some of the >> flags with which the modules were compiled so that the semantics of >> the resulting program are correct. For example, a module compiled with >> `-msoft-float' should use library
2020 Feb 19
2
test post1
funny guy!!! A BIG thank you to Bjorn and Rowland for his relentless patience and support. Regards, Phil This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents
2012 May 01
0
[LLVMdev] [RFC] Encoding Compile Flags into the IR
On Apr 30, 2012, at 4:12 PM, Bill Wendling wrote: > On Apr 30, 2012, at 1:00 PM, dag at cray.com wrote: > >> Bill Wendling <wendling at apple.com> writes: >> >>> Link-Time Optimization has a problem. We need to preserve some of the >>> flags with which the modules were compiled so that the semantics of >>> the resulting program are correct. For
2015 Sep 18
2
GlobalOPT and sections
Hello everyone, This is a rather ancient code with Chris's name all over it, so I naturally feel humbled :) I see a conceptual issue in lib/Transforms/IPO/GlobalOpt.cpp with several optimizations that create a copy of GlobalVariable without copying attributes from the original one. Consider this one: http://llvm.org/doxygen/GlobalOpt_8cpp_source.html static bool
2020 Feb 19
2
test post1
On 19/02/2020 18:55, Philippe LeCavalier wrote: > Just another test. Could I get a few replies please? > > Regards, Phil > This email and any files transmitted with it are confidential and > intended solely for the use of the individual or entity to whom they > are addressed. If you are not the intended recipient, you are notified > that disclosing, copying, distributing or
2018 May 07
2
I am leaving llvm
> However, the main point here is why we have it and who is doing it. I > know Chandler and Tanya for a while and, while I do not speak for > them, I trust them to *want* to do the right thing (tm). > > If they miss the mark, or make mistakes, I'd first point out to them, > not assume ill intent. This has been my personal experience and I have > no reason to change
2005 Jan 10
0
[LLVMdev] Version Control Upgrade?
On Sun, Jan 09, 2005 at 08:02:38PM -0800, Jeff Cohen wrote: > I have used Perforce also and fully agree it's wonderful. The only > concern I have is with their license for open source projects. The > only gotcha is that it must be renewed annually, and they reserve the > right to not renew it (though they say they won't unreasonably deny > renewals). Not sure how much
2012 Apr 30
0
[LLVMdev] [RFC] Encoding Compile Flags into the IR
Bill Wendling <wendling at apple.com> writes: > Link-Time Optimization has a problem. We need to preserve some of the > flags with which the modules were compiled so that the semantics of > the resulting program are correct. For example, a module compiled with > `-msoft-float' should use library calls for floating point. And that's > only the tip of the proverbial
2007 Mar 25
1
the age old telephone tree... why re-invent the wheel?
I have an interesting task for my son's lacrosse team... it is the time-old telephone tree... I am pretty sure someone has already done this w/*, why re-invent the wheel?... a) coach calls in leaves a msg, others call in retrieve the msg b) coach calls in leaves a msg, kicks of a call to every parent plays msg c) coach calls in leaves a msg, kicks off a call to every parent, checks for
2010 Dec 20
1
howto? howto switch domain controllers in an ldap directory?
I've got an ldap directory, but no PDC yet. I want to set up a test PDC, and once things work, I want to be able to set a more appropriate system to be teh PDC using teh same login informations (replica of existing authzn databases). where's the documentation of how to do this? what do I need to know about this process (I'm not sure what it's even called >,.,< in
2020 Nov 10
2
Recovering expunged but not purged e-mails from mdbox with zlib compression
Yesterday I had to recover an e-mail which a user had deleted. If I understand this correctly the message was expunged but not purged (doveadm purge had not been run). This e-mail was clearly still in the mdbox stored with zlib compression as I could tell using the doveadm dump command (doveadm dump -t dbox filename). I could however not reveal the e-mail with the normal doveadm fetch -u
2020 Apr 23
1
Re: [PATCH nbdkit v3 2/2] golang: Compile against the local nbdkit build, not installed.
On 4/23/20 2:13 PM, Richard W.M. Jones wrote: > Compiling nbdkit from source when an older nbdkit is installed would > fail because certain symbols such as .get_ready are not defined in the > (installed) <nbdkit-plugin.h>: > > ../../src/libguestfs.org/nbdkit/nbdkit.go:541:8: plugin.get_ready undefined (type _Ctype_struct_nbdkit_plugin has no field or method get_ready) >
2015 Sep 21
2
GlobalOPT and sections
Chris, Thanks for the clarification... at least no bug report is due... and I am glad that I've asked. In my case these transformations are rather useful and forcing them to copy original global variable section is making them compatible with our (rather important) use case, so I guess I will have to fix it locally. Nevertheless if someone else would have a similar issue - I would be
2012 Apr 29
8
[LLVMdev] [RFC] Encoding Compile Flags into the IR
Hi, Link-Time Optimization has a problem. We need to preserve some of the flags with which the modules were compiled so that the semantics of the resulting program are correct. For example, a module compiled with `-msoft-float' should use library calls for floating point. And that's only the tip of the proverbial iceberg. Goals ===== My goals for whichever solution we come up with are
2020 Apr 23
4
[PATCH nbdkit v3 0/2] golang: Compile against the local nbdkit build.
Version 2: https://www.redhat.com/archives/libguestfs/2020-April/thread.html#00166 Version 3 contains all changes discussed in the previous review. Rich.