All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Thimm <Axel.Thimm@ATrpms.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: ATrpms development list <atrpms-devel@ATrpms.net>,
	alsa-devel@lists.sourceforge.net, psantoro@att.net
Subject: Re: 1.0.7 build errors
Date: Sat, 20 Nov 2004 14:45:59 +0100	[thread overview]
Message-ID: <20041120134559.GG9815@neu.nirvana> (raw)
In-Reply-To: <s5hd5ybcba8.wl@alsa2.suse.de>


[-- Attachment #1.1: Type: text/plain, Size: 981 bytes --]

On Thu, Nov 18, 2004 at 06:33:19PM +0100, Takashi Iwai wrote:
> At Thu, 18 Nov 2004 11:33:52 -0500,
> Peter Santoro wrote:
> > I've been using 1.05a and recently tried upgrading to 1.0.7.
> > Unfortunately, I get build errors (patching fails).  I tried
> > 1.0.6a and it works fine.  I'm using slackware 9.1/10.0 and kernel
> > 2.4.28.  Let me know if you would like more information.
> 
> This should have been fixed on the CVS version.
> Could you try CVS?

I had similar errors with FC1 and RH9,8.0 and 7.3. I just upgraded to
today's CVS and the errors are still there for Red Hat's 2.4.22:

copying file alsa-kernel/core/sound.c
patching file sound.c
Hunk #5 succeeded at 502 (offset -1 lines).
copying file alsa-kernel/core/init.c
patching file init.c
Hunk #4 FAILED at 823.
Hunk #5 succeeded at 836 (offset -3 lines).
1 out of 5 hunks FAILED -- saving rejects to file init.c.rej
make[2]: *** [init.c] Error 1

Thanks!
-- 
Axel.Thimm at ATrpms.net

[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2004-11-20 13:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-18 16:33 1.0.7 build errors Peter Santoro
2004-11-18 17:33 ` Takashi Iwai
2004-11-20 13:45   ` Axel Thimm [this message]
2004-11-22 11:28     ` Takashi Iwai

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=20041120134559.GG9815@neu.nirvana \
    --to=axel.thimm@atrpms.net \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=atrpms-devel@ATrpms.net \
    --cc=psantoro@att.net \
    --cc=tiwai@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.