From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001444]: sb16: unable to compile driver and wrong build order
Date: Mon, 2 Jan 2006 20:39:06 +0100 [thread overview]
Message-ID: <eb7dd26ec71a3175e598de2075df9ec2@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1444>
======================================================================
Reported By: slashlos
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 1444
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: block
Priority: normal
Status: closed
Distribution:
Kernel Version: 2.4.20-31smp
Resolution: open
Fixed in Version:
======================================================================
Date Submitted: 09-23-2005 13:31 CEST
Last Modified: 01-02-2006 20:39 CET
======================================================================
Summary: sb16: unable to compile driver and wrong build order
Description:
this this might be a noob issue, but the order suggested for build should
be lib, util then driver; it seems driver needs some utils?
Anyhow, when trying to build driver, I get this:
gcc -D__KERNEL__ -DMODULE=1 -I/usr/src/alsa/alsa-driver-1.0.10rc1/include
-I/lib/modules/2.4.20-31.9smp/build/include -O2
-mpreferred-stack-boundary=2 -march=i686 -D__SMP__ -DCONFIG_SMP -DLINUX
-Wall -Wstrict-prototypes -fomit-frame-pointer -Wno-trigraphs -O2
-fno-strict-aliasing -fno-common -pipe -DALSA_BUILD -nostdinc -iwithprefix
include -DMODVERSIONS -include
/lib/modules/2.4.20-31.9smp/build/include/linux/modversions.h
-I/usr/src/alsa/alsa-driver-1.0.10rc1/alsa-kernel/core/oss
-fno-omit-frame-pointer -DEXPORT_SYMTAB -c mixer_oss.c
mixer_oss.c:397: unknown field `unlocked_ioctl' specified in initializer
mixer_oss.c:397: warning: initialization from incompatible pointer type
mixer_oss.c:398: unknown field `compat_ioctl' specified in initializer
make[2]: *** [mixer_oss.o] Error 1
make[2]: Leaving directory
`/usr/src/alsa/alsa-driver-1.0.10rc1/acore/oss'
make[1]: *** [_modsubdir_oss] Error 2
make[1]: Leaving directory `/usr/src/alsa/alsa-driver-1.0.10rc1/acore'
make: *** [compile] Error 1
======================================================================
----------------------------------------------------------------------
perex - 11-14-05 10:20
----------------------------------------------------------------------
Could you try 1.0.10rc3 packages?
----------------------------------------------------------------------
rlrevell - 01-02-06 20:39
----------------------------------------------------------------------
No response
Issue History
Date Modified Username Field Change
======================================================================
09-23-05 13:31 slashlos New Issue
09-23-05 13:31 slashlos Kernel Version => 2.4.20-31smp
10-14-05 03:50 slashlos Issue Monitored: slashlos
11-14-05 10:20 perex Note Added: 0006702
11-14-05 10:20 perex Status assigned => feedback
01-02-06 20:39 rlrevell Status feedback => closed
01-02-06 20:39 rlrevell Note Added: 0007386
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-02 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 19:39 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-14 9:20 [ALSA - driver 0001444]: sb16: unable to compile driver and wrong build order bugtrack
2005-09-23 11:31 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=eb7dd26ec71a3175e598de2075df9ec2@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