similar to: configure.ac

Displaying 20 results from an estimated 2000 matches similar to: "configure.ac"

2017 Aug 01
0
configure.ac
If you check developer.r-project.org, you'll find links to the scripts that we use for building releases and pre-releases of R. These are usually run on a Mac, but shouldn't require much change for Linux. In particular, notice this lead-in in the prerelease script: rm -rf BUILD-dist mkdir BUILD-dist cd R aclocal -I m4 autoconf cd ../BUILD-dist ....etc.... -pd > On 1 Aug 2017, at
2002 Sep 26
2
Compiling CVS? (automake/autoconf problem with autogen.sh?)
I've eagerly grabbed the current CVS as of a few minutes ago, and attempted to build and play with theora, but am running into a snag with the autogen.sh script: ------------------------------------------------------------------------ bash-2.05# ./autogen.sh I am going to run ./configure with no arguments - if you wish to pass any to it, please specify them on the ./autogen.sh command line.
2004 Aug 06
3
autogen.sh trouble with latest CVS checkout
Hello All: I just checked out the whole icecast but cannot build anything because autogen wouldn't cooperate. I have automake-1.7.6 just installed from ftp.gnu.org. Below is an example output in trying to build "icecast"; it's not very short... Thanks in advance for any help. --- $~/icecast/icecast> ./autogen.sh Checking for automake version found automake found
2004 Aug 06
3
Some questions and problems about setting up Icecast2
On Mon, Jul 29, 2002 at 02:45:50PM +1000, Michael Smith wrote: > > > When you say "icecast2", do you mean the module 'ice2'? The reason I ask is because I don't see a 'icecast2' module in CVS. I also don't see the HACKING file in ice2. Could you please provide a little more information about the CVS modules that I need? > > icecast2 is in the
2004 Aug 06
8
Some questions and problems about setting up Icecast2
I've finally decided to take the plunge and set up an Icecast 2 server on my Linux 2.4.18 machine. After asking in #vorbis, I was told that I need ice2 and ices. From what I understand, ice2 is the Icecast2 server, while ices is a program that sends it data to push to its clients. Am I right? After downloading both modules, the first problem I've ran into is executing the
2012 Dec 12
8
[PATCH 0/5] update build system
This patch series modernizes various aspects of the autotools based build system. There is a lot more that could and should be done, but I tried to stay conservative for now and just resolve some of the most obvious issues. Max Horn (5): configure: replace XIPH_C_FIND_ENDIAN by AC_C_BIGENDIAN autogen.sh: replace this by a simple call to autoreconf configure: always print
2012 Jun 14
5
Opus and WebM support have landed
Hi, quick info. Yesterday Rillian landed Oneman's patches adding ogg/opus and WebM support on Icecast trunk. Big thanks for all the work that has gone into this! Please use trunk for your testing and development in this area from now. If you run into problems please send mails/patches/bitch'n'moan-on-IRC/... It's important to find any problems by testing it in every possible
2004 Aug 06
3
Some questions and problems about setting up Icecast2
On Sun, Jul 28, 2002 at 11:31:59PM +1000, Michael Smith wrote: > At 09:48 PM 7/27/02 -0500, you wrote: > > I've finally decided to take the plunge and set up an Icecast 2 server on my Linux 2.4.18 machine. After asking in #vorbis, I was told that I need ice2 and ices. From what I understand, ice2 is the Icecast2 server, while ices is a program that sends it data to push to its
2002 Oct 14
1
timeline
good question. I would think beta means the bitstream is more or less stable. Monty? >If June is the goal for public release, is the second milestone the first beta/rc1? Guess what I'm asking is, whats a good estimate for when the codec will be frozen as far as backwards compatability.. -----Original Message----- From: Arc [mailto:arc@indymedia.org] Sent:
2004 Sep 10
4
beta 10 candidate checked in
> > I have checked in all the latest into CVS and am going to start the > > test suite again. if all goes well I will probably release this as > > beta 10. > > > > anyway, try it out and let me know if anything bad happens! it > > should be a short jump from beta 10 to 1.0. > > I've just checked out the latest from scratch. There is no configure
2015 Feb 23
3
Call for testing: OpenSSH 6.8
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",
2019 Jan 21
18
[PATCH xf86-video-nouveau 00/17] autotools configuration cleanups
Series of cleanups to autotools build config files to utilize the available xorg-server macros, defaults and more closely match other modern Xorg drivers. Notable improvements: - gitignore fully covers potential build artifacts - Simplify logic given stated minimum required version of xorg-server 1.8 - Remove use of deprecated, outdated or no longer required macros - Utilize xorg macros where
2012 Jun 11
1
[hivex][PATCH] OS X, bootstrap: Locate pkg.m4
OS X does not include pkg-config by default. When installed, pkg.m4 tends to end up in some place that is not the autotool-expected /usr/share/aclocal/. Add to bootstrap a path check so pkg.m4 can be found, so ./configure does not fail invoking PKG_CHECK_MODULES. Signed-off-by: Alex Nelson <ajnelson at cs.ucsc.edu> --- bootstrap | 7 ++++++- 1 files changed, 6 insertions(+), 1
2012 Jun 11
1
[hivex][PATCH v2] OS X, bootstrap: Locate pkg.m4
OS X does not include pkg-config by default. This causes ./configure to fail when invoking PKG_CHECK_MODULES for libxml2. This change autodetects the path for aclocal, c/o RWMJ noting the real problem is a deficiency in aclocal on OS X. Signed-off-by: Alex Nelson <ajnelson at cs.ucsc.edu> --- bootstrap | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/bootstrap
2004 Aug 06
3
libshout compile problems
No, it's not his version of autoconf or automake. I had the same errors even with the latest versions available for my debian distribution. I only could help myself by using one of my precompiled binaries from a previous cvs snapshot. I haven't tried it with the current snapshot but I also don't know if there had been any update lately. Michael Smith wrote: >>all ok until
2009 Aug 10
1
[PATCH libguestfs] build: daemon/do_debug: parameters aren't always unused
Thanks to the reminder from Dan Berrange, here's a patch to make build output less verbose, by default. E.g., instead of the redundant multi-line compilation/linking commands, you'll see something like this by default: CC guestfsd-fsck.o CC guestfsd-grep.o CC guestfsd-grub.o CC guestfsd-glob.o CC guestfsd-guestfsd.o CC guestfsd-headtail.o CC
2004 Sep 15
1
building from svn
After downloading libogg-1.1.tar.gz, libvorbis-1.0.1.tar.gz, and libtheora-1.0alpha3.tar.gz; building and installing them in that order, and trying the alpha3 theora encoder, I decided to try to build theora from svn. Using svn to checkout theoratrunk worked ok. The first time I tried to execute ./autogen.sh, it complained that I didn't have automake. Mandrake 10.0 comes with automake
2006 Jul 13
4
Compiling the latest SVN checkout
Hello, I just checked out the latest version of speex and I want to compile it. The INSTALL file says that's easy: bjoern@deimos:~/studium/beleg/resources/svn/speex$ cat INSTALL Installing Speex is as easy as: % ./configure [--prefix=<install-path>] % make % make install Note that if you are using the code from SVN, you will need to run "autogen.sh" instead of
2011 Sep 06
1
[PATCH 3/3] Mac OS X: Run glibtoolize in absence of libtoolize
Signed-off-by: Alex Nelson <ajnelson at cs.ucsc.edu> --- bootstrap | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/bootstrap b/bootstrap index 79b6717..b2960c1 100755 --- a/bootstrap +++ b/bootstrap @@ -36,7 +36,7 @@ autopoint --force # Autoreconf runs aclocal before libtoolize, which causes spurious # warnings if the initial aclocal is confused by the
2004 Sep 10
6
beta 10 candidate checked in
I have checked in all the latest into CVS and am going to start the test suite again. if all goes well I will probably release this as beta 10. this one should have all the configure stuff working with the new assembly infrastructure. I have tried to make it as easy as possible to port routines to assembly. all that's really needed now is to write the corresponding routine for a specific