From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000665]: Build failure in /usr/src/alsa/alsa-driver/acore/init.c
Date: Mon, 27 Dec 2004 15:48:26 +0100 [thread overview]
Message-ID: <cb85b005bd18b6f0760317c9e31c229b@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=665>
======================================================================
Reported By: ronis
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 665
Category: 0_compilation problem_!!!
Reproducibility: always
Severity: block
Priority: normal
Status: closed
Distribution:
Kernel Version:
Resolution: not an issue
Fixed in Version:
======================================================================
Date Submitted: 11-22-2004 19:31 CET
Last Modified: 12-27-2004 15:48 CET
======================================================================
Summary: Build failure in
/usr/src/alsa/alsa-driver/acore/init.c
Description:
There's an unterminated #ifdef in init.c. (PM_CONFIG or more likely
CONFIG_PCI). Here's the log:
CC [M] /usr/src/alsa/alsa-driver/acore/init.o
/usr/src/alsa/alsa-driver/acore/init.c:680:1: unterminated #ifdef
make[4]: *** [/usr/src/alsa/alsa-driver/acore/init.o] Error 1
make[3]: *** [/usr/src/alsa/alsa-driver/acore] Error 2
make[2]: *** [_module_/usr/src/alsa/alsa-driver] Error 2
make[1]: *** [modules] Error 2
make[1]: Leaving directory `/usr/src/linux-2.6.9'
make: *** [compile] Error 2
Adding an extra #endif at the end of the file fixes things, although, I'm
not 100% sure that this is the right place top put things.
(BTW, I'm now running 2.6.9 but didn't have a chance to midify my
profile)
======================================================================
----------------------------------------------------------------------
ronis - 11-23-04 22:15
----------------------------------------------------------------------
OK I moved all the alsa-* directories out of the way, did cvs -z3 update
-dP, followed by my usual build script. The build now completes fully
and there are no
rejected patch files. Better yet, the driver works.
As you thought, my CVS tree must have been corrupted somehow.
I guess this can be closed.
Thanks for your help.
----------------------------------------------------------------------
tiwai - 11-24-04 12:19
----------------------------------------------------------------------
Ok, closed now.
Issue History
Date Modified Username Field Change
======================================================================
11-22-04 19:31 ronis New Issue
11-23-04 15:59 tiwai Note Added: 0002517
11-23-04 16:52 ronis Note Added: 0002523
11-23-04 17:44 tiwai Note Added: 0002524
11-23-04 18:20 ronis Note Added: 0002525
11-23-04 18:27 tiwai Note Added: 0002526
11-23-04 22:15 ronis Note Added: 0002535
11-24-04 12:19 tiwai Status assigned => resolved
11-24-04 12:19 tiwai Resolution open => not an issue
11-24-04 12:19 tiwai Note Added: 0002548
12-27-04 15:48 tiwai Status resolved => closed
======================================================================
-------------------------------------------------------
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-27 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-27 14:48 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-11-24 11:19 [ALSA - driver 0000665]: Build failure in /usr/src/alsa/alsa-driver/acore/init.c bugtrack
2004-11-23 21:15 bugtrack
2004-11-23 17:27 bugtrack
2004-11-23 17:20 bugtrack
2004-11-23 16:44 bugtrack
2004-11-23 15:52 bugtrack
2004-11-23 14:59 bugtrack
2004-11-22 18: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=cb85b005bd18b6f0760317c9e31c229b@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