From: Takashi Iwai <tiwai@suse.de>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Re: 1.0.7 build errors
Date: Mon, 22 Nov 2004 12:28:46 +0100 [thread overview]
Message-ID: <s5hmzxadswh.wl@alsa2.suse.de> (raw)
In-Reply-To: <20041120134559.GG9815@neu.nirvana>
At Sat, 20 Nov 2004 14:45:59 +0100,
Axel Thimm wrote:
>
> [1 <text/plain; us-ascii (quoted-printable)>]
> 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
I can't reproduce this.
Did you update both alsa-driver and alsa-kernel trees?
Takashi
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
prev parent reply other threads:[~2004-11-22 11:28 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
2004-11-22 11:28 ` Takashi Iwai [this message]
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=s5hmzxadswh.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
/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