Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: James Courtier-Dutton <James@superbug.demon.co.uk>
To: James Courtier-Dutton <James@superbug.demon.co.uk>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [PATCH] fixes Re: problem compiling alsa-lib CVS.
Date: Wed, 31 Mar 2004 21:09:47 +0100	[thread overview]
Message-ID: <406B258B.4080106@superbug.demon.co.uk> (raw)
In-Reply-To: <405F1C2A.1070000@superbug.demon.co.uk>

Is there any reason why this patch was not added to the alsa-lib cvs ?


James Courtier-Dutton wrote:
> James Courtier-Dutton wrote:
> 
>> I attach the output I see on the screen when running ./cvscompile.
>>
>> Cheers
>> James
>>
> 
> I attach a patch to fix the problem for me.
> 
> 
> ------------------------------------------------------------------------
> 
> --- cvscompile	2002-10-24 13:09:30.000000000 +0100
> +++ cvscompile.new	2004-03-22 16:58:07.072241360 +0000
> @@ -1,4 +1,9 @@
>  #!/bin/bash
> +# Minimum value required to build
> +WANT_AUTOMAKE_1_6=1 export WANT_AUTOMAKE_1_6
> +AUTOMAKE_MIN=1.6.0
> +AUTOCONF_MIN=2.53
> +LIBTOOL_MIN=1.4.0
>  
>  touch ltconfig
>  libtoolize --force --copy --automake



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click

  reply	other threads:[~2004-03-31 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22 16:53 problem compiling alsa-lib CVS James Courtier-Dutton
2004-03-22 17:02 ` [PATCH] fixes " James Courtier-Dutton
2004-03-31 20:09   ` James Courtier-Dutton [this message]
2004-04-01  8:42     ` Jaroslav Kysela
2004-04-01 11:57       ` James Courtier-Dutton
2004-04-01 21:50         ` Glenn Maynard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=406B258B.4080106@superbug.demon.co.uk \
    --to=james@superbug.demon.co.uk \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox