From: Martin Habets <errandir_news@mph.eclipse.co.uk>
To: alsa-devel@alsa-project.org
Subject: How to build alsa-driver for sparc?
Date: Mon, 27 Sep 2004 20:14:38 +0100 [thread overview]
Message-ID: <20040927191437.GA436@palantir8> (raw)
I'm trying to build alsa-driver-1.0.7rc1 for SPARC32, but have
found that CONFIG_SPARC32 is not set in toplevel.config.
After initial failure, I have tried the steps from cvscompile, and rebuild
utils/mod-deps.
After I hand-edit toplevel.config and apply the patch attached, it does
start building. But the whole generation of toplevel.config leaves my
wondering how to make it work properly.
Any hints?
--
Martin
---------------------------------------------------------------------------
30 years from now GNU/Linux will be as redundant a term as UNIX/MERT is
today. - Martin Habets
---------------------------------------------------------------------------
--- alsa-driver-1.0.7rc1/Makefile.orig 2004-09-27 17:34:05.000000000 +0100
+++ alsa-driver-1.0.7rc1/Makefile 2004-09-27 17:35:21.000000000 +0100
@@ -65,6 +65,12 @@
ifeq (y,$(CONFIG_PARISC))
SUBDIRS += parisc
endif
+ifeq (y,$(CONFIG_SPARC32))
+SUBDIRS += sparc
+endif
+ifeq (y,$(CONFIG_SPARC64))
+SUBDIRS += sparc
+endif
CSUBDIRS += include test utils
KCONFIG_FILES = $(shell find $(SND_TOPDIR) -name Kconfig) $(shell find $(SND_TOPDIR)/alsa-kernel/ -name Kconfig)
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php
next reply other threads:[~2004-09-27 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-27 19:14 Martin Habets [this message]
2004-09-27 20:01 ` How to build alsa-driver for sparc? Takashi Iwai
2004-09-28 0:25 ` Martin Habets
2004-09-28 16:51 ` Takashi Iwai
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=20040927191437.GA436@palantir8 \
--to=errandir_news@mph.eclipse.co.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.