From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000743]: msleep is now defined in linux/include/linux/delay.h causing conflict with macro defined in alsa-driver/include/adriver.h
Date: Thu, 23 Dec 2004 22:10:46 +0100 [thread overview]
Message-ID: <19d9f89080b79fbd3ffdcb041efc282b@bugtrack.alsa-project.org> (raw)
The following issue has been SUBMITTED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=743>
======================================================================
Reported By: jdthood
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 743
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: major
Priority: normal
Status: assigned
Distribution:
Kernel Version:
======================================================================
Date Submitted: 12-23-2004 22:10 CET
Last Modified: 12-23-2004 22:10 CET
======================================================================
Summary: msleep is now defined in linux/include/linux/delay.h
causing conflict with macro defined in alsa-driver/include/adriver.h
Description:
Recent 2.4.29-pre3 patch moves msleep() from include/linux/libata-compat.h
to include/linux/delay.h. As a result, alsa-driver 1.0.7 does not
compile
on 2.4.29-pre3 because it defines its own msleep macro in
include/adriver.h.
Currently the macro is defined inside
#if LINUX_VERSION_CODE < KERNEL_VERSION(2, 6, 6) ... #endif.
The code seems to be the same in CVS. I guess this version dependency
needs to be updated.
gcc -D__KERNEL__ -DMODULE=1 -I/usr/src/modules/alsa-driver/include
-I/usr/src/linux-2.4.29/include -I/usr/src/linux-2.4.29/include2
-I/usr/src/linux-2.4.29/include -O2 -mpreferred-stack-boundary=2
-march=i686 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer
-Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -DALSA_BUILD
-nostdinc -iwithprefix include -DEXPORT_SYMTAB -c timer.c
In file included from timer.c:23:
/usr/src/linux-2.4.29/include/linux/delay.h:57: error: parse error before
"do"
/usr/src/linux-2.4.29/include/linux/delay.h:57: error: parse error before
'(' token
/usr/src/linux-2.4.29/include/linux/delay.h:60: error: parse error before
'(' token
make[4]: *** [timer.o] Error 1
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
12-23-04 22:10 jdthood New Issue
======================================================================
-------------------------------------------------------
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/
next reply other threads:[~2004-12-23 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-23 21:10 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-27 14:10 [ALSA - driver 0000743]: msleep is now defined in linux/include/linux/delay.h causing conflict with macro defined in alsa-driver/include/adriver.h bugtrack
2005-01-31 18:04 bugtrack
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=19d9f89080b79fbd3ffdcb041efc282b@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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