All of lore.kernel.org
 help / color / mirror / Atom feed
From: Raymond <rayau@netvigator.com>
To: alsa-devel@lists.sourceforge.net
Subject: Re: Disagreement about versions following CVS update
Date: Sat, 20 Aug 2005 15:17:37 +0800	[thread overview]
Message-ID: <4306D911.70101@netvigator.com> (raw)
In-Reply-To: <43063408.60402@redfish-solutions.com>

Philip Prindeville wrote:
> I did a CVS update yesterday, and a rebuild and tried to reinstall, and
> I'm seeing:
> 
> WARNING: Error inserting snd_seq_device 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/seq/snd-seq-device.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_rawmidi 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-rawmidi.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_mpu401_uart 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_timer 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-timer.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> WARNING: Error inserting snd_timer 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-timer.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting snd_pcm 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/acore/snd-pcm.ko): Unknown 
> symbol in module, or unknown parameter (see dmesg)
> WARNING: Error running install command for snd_pcm
> WARNING: Error inserting snd_ac97_codec 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/pci/ac97/snd-ac97-codec.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> FATAL: Error inserting snd_via82xx 
> (/lib/modules/2.6.12-1.1372_FC3/kernel/sound/pci/snd-via82xx.ko): 
> Unknown symbol in module, or unknown parameter (see dmesg)
> 
> Stupid question:  did a version number get changed somewhere?  And if
> so, what's the fix?  I did a:
> 
> % make -C alsa-driver clean
> 
> and a rebuild, but I'm still seeing these.  What did I miss?
> 
> -Philip

It seem that ALSA version has been changed from 1.0.9b to 1.10.0-rc1 on CVS.

alsa-driver and alsa-lib can be rebuilded except alsa-utils.
I follow the instruction but cannot compile alsa-utils (CVS) on FC1.


cvs/alsa-utils]# ./cvscompile
Copying file ABOUT-NLS
Copying file config.rpath
Copying file mkinstalldirs
Not copying intl/ directory.
Copying file po/Makefile.in.in
Copying file po/boldquot.sed
Copying file po/en@boldquot.header
Copying file po/en@quot.header
Copying file po/insert-header.sin
Copying file po/Makevars.template
Copying file po/quot.sed
Copying file po/remove-potcdate.sin
Copying file po/Rules-quot
Copying file m4/codeset.m4
Copying file m4/gettext.m4
Copying file m4/glibc21.m4
Copying file m4/iconv.m4
Copying file m4/intdiv0.m4
Copying file m4/inttypes.m4
Copying file m4/inttypes_h.m4
Copying file m4/inttypes-pri.m4
Copying file m4/isc-posix.m4
Copying file m4/lcmessage.m4
Copying file m4/lib-ld.m4
Copying file m4/lib-link.m4
Copying file m4/lib-prefix.m4
Copying file m4/nls.m4
Copying file m4/po.m4
Copying file m4/progtest.m4
Copying file m4/stdint_h.m4
Copying file m4/uintmax_t.m4
Copying file m4/ulonglong.m4
Updating configure.in (backup is in configure.in~)

Please use AM_GNU_GETTEXT([external]) in order to cause autoconfiguration
to look for an external libintl.

Please run 'aclocal -I m4' to regenerate the aclocal.m4 file.
You need aclocal from GNU automake 1.5 (or newer) to do this.
Then run 'autoconf' to regenerate the configure file.

You might also want to copy the convenience header file gettext.h
from the /usr/share/gettext directory into your package.
It is a wrapper around <libintl.h> that implements the configure 
--disable-nls
option.

Press Return to acknowledge the previous three paragraphs.

CFLAGS=-O2 -Wall -pipe -g
./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU
checking for gcc... gcc32
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc32 accepts -g... yes
checking for gcc32 option to accept ANSI C... none needed
checking dependency style of gcc32... gcc3
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
./configure: line 4415: syntax error near unexpected token `<<<'
./configure: line 4415: `<<<<<<< configure.in'


cvs/alsa-utils]# aclocal --version
aclocal (GNU automake) 1.7.8

cvs/alsa-utils]# aclocal -I m4

cvs/alsa-utils]# autoconf --version
autoconf (GNU Autoconf) 2.57

cvs/alsa-utils]# autoconf

cvs/alsa-utils]# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether NLS is requested... yes
checking for msgfmt... /usr/bin/msgfmt
checking for gmsgfmt... /usr/bin/msgfmt
checking for xgettext... /usr/bin/xgettext
checking for msgmerge... /usr/bin/msgmerge
checking for style of include used by make... GNU
checking for gcc... gcc32
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc32 accepts -g... yes
checking for gcc32 option to accept ANSI C... none needed
checking dependency style of gcc32... gcc3
checking build system type... i686-redhat-linux-gnu
checking host system type... i686-redhat-linux-gnu
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for shared library run path origin... done
checking whether NLS is requested... yes
checking for GNU gettext in libc... yes
checking whether to use NLS... yes
checking where the gettext function comes from... libc
./configure: line 4415: syntax error near unexpected token `<<<'
./configure: line 4415: `<<<<<<< configure.in'







-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  parent reply	other threads:[~2005-08-20  7:17 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19 19:33 Disagreement about versions following CVS update Philip Prindeville
2005-08-19 20:36 ` Lee Revell
2005-08-19 21:11   ` Philip Prindeville
2005-08-19 21:14     ` Lee Revell
2005-08-19 22:17       ` Philip Prindeville
2005-08-19 22:25         ` Lee Revell
2005-08-19 23:20           ` Philip Prindeville
2005-08-19 23:28             ` Lee Revell
2005-08-19 23:43               ` Philip Prindeville
2005-08-19 23:47                 ` Lee Revell
2005-08-19 23:53                   ` Philip Prindeville
2005-08-19 23:56                     ` Lee Revell
2005-08-20  0:06                       ` Philip Prindeville
2005-08-22 12:12                         ` Takashi Iwai
2005-08-22 16:30                           ` Philip Prindeville
2005-08-22 16:33                             ` Takashi Iwai
2005-08-20  7:17 ` Raymond [this message]
2005-08-20 21:06   ` Lee Revell
2005-08-21  0:55     ` Raymond
2005-08-22 12:09       ` Takashi Iwai
2005-08-22 15:13         ` Raymond
2005-08-22 15:29           ` Takashi Iwai
2005-08-22 12:14 ` Takashi Iwai
2005-08-22 16:27   ` Philip Prindeville
2005-08-22 16:29     ` 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=4306D911.70101@netvigator.com \
    --to=rayau@netvigator.com \
    --cc=alsa-devel@lists.sourceforge.net \
    /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.