From: Dmitry Astapov <adept@umc.com.ua>
To: andi@rhlx01.fht-esslingen.de
Cc: "Andrea Venturi (personale)" <andrea.venturi@tin.it>,
alsa-devel@lists.sourceforge.net
Subject: Re: gcc 3.x build issue?
Date: Tue, 18 Feb 2003 10:34:21 +0200 [thread overview]
Message-ID: <877kbyrnqq.fsf@dimail.umc.com.ua> (raw)
In-Reply-To: <20030217191113.GA1853@rhlx01.fht-esslingen.de> (Andreas Mohr's message of "Mon, 17 Feb 2003 20:11:13 +0100")
Evening, Andreas.
Andreas Mohr <andi@rhlx01.fht-esslingen.de> 20:11 17/2/2003 wrote:
>> >After having installed the 0.9rc7 Debian package (or around that time
>> >at least) and having rebuilt ALSA, I didn't manage to start ALSA properly
>> >any more:
>> i incurred in the same problem since two days, when i decided to upgrade
>> my alsa driver from 0.9rc6 to 0.9rc7
AM> Ah, finally! It's quite reassuring to know that I'm not alone in suffering
AM> this severe problem :-)
I'd like to second that - "oops" with alsa-drivers built with gcc-3.0 and
gcc-3.2, no problems with 2.95.
--
Dmitry Astapov //ADEpt E-mail: adept@umc.com.ua
GPG KeyID/fprint: F5D7639D/CA36 E6C4 815D 434D 0498 2B08 7867 4860 F5D7 639D
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-02-18 8:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-14 11:14 cat /proc/asound/version: "No such device": HELP!! Andreas Mohr
2003-02-17 18:43 ` Andrea Venturi (personale)
2003-02-17 19:11 ` gcc 3.x build issue? (was: cat /proc/asound/version: "No such device": HELP!!) Andreas Mohr
2003-02-18 8:34 ` Dmitry Astapov [this message]
2003-02-18 8:52 ` Takashi Iwai
2003-02-18 9:04 ` Duncan Sands
2003-02-18 13:09 ` Duncan Sands
[not found] ` <20030218155623.GA11912@nubol.int.oskuro.net>
2003-02-18 18:49 ` Andreas Mohr
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=877kbyrnqq.fsf@dimail.umc.com.ua \
--to=adept@umc.com.ua \
--cc=alsa-devel@lists.sourceforge.net \
--cc=andi@rhlx01.fht-esslingen.de \
--cc=andrea.venturi@tin.it \
/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