From: Adrian Bunk <bunk@fs.tum.de>
To: Eyal Lebedinsky <eyal@eyal.emu.id.au>, Gerd Knorr <kraxel@bytesex.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: 2.6.6-rc3: gcc 2.95: cx88 __ucmpdi2 error
Date: Sat, 1 May 2004 13:24:32 +0200 [thread overview]
Message-ID: <20040501112432.GE2541@fs.tum.de> (raw)
In-Reply-To: <408F9BD8.8000203@eyal.emu.id.au>
On Wed, Apr 28, 2004 at 09:56:08PM +1000, Eyal Lebedinsky wrote:
> Linus Torvalds wrote:
> >s390, cifs, ntfs, ppc, ppc64, cpufreq upates. Oh, and DVB and USB.
> >
> >I'm hoping to do a final 2.6.6 later this week, so I'm hoping as many
> >people as possible will test this.
>
> OK, I'll bite. Building using :
> # gcc --version
> 2.95.4
>
> depmod says:
>
>...
> WARNING: /lib/modules/2.6.6-rc3/kernel/drivers/media/video/cx88/cx8800.ko
> needs unknown symbol __ucmpdi2
I'm also seeing this, but only with gcc 2.95, not with gcc 3.3.3 .
It comes from drivers/media/video/cx88/cx88-video.c, more exactly from
the switch in set_tvaudio.
But I have to admit I don't understand why exactly it does happen.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2004-05-01 11:24 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 2:03 Linux 2.6.6-rc3 Linus Torvalds
2004-04-28 8:48 ` Måns Rullgård
2004-04-28 9:16 ` Florian Schirmer
2004-04-28 9:52 ` Armin Schindler
2004-04-28 11:56 ` Eyal Lebedinsky
2004-05-01 11:24 ` Adrian Bunk [this message]
2004-05-01 17:45 ` 2.6.6-rc3: gcc 2.95: cx88 __ucmpdi2 error Linus Torvalds
2004-05-01 18:38 ` Andreas Schwab
2004-05-01 18:57 ` Linus Torvalds
2004-05-04 17:13 ` Gerd Knorr
2004-05-01 20:13 ` 2.6.6-rc3: modular DVB tda1004x broken Adrian Bunk
2004-05-01 22:02 ` Johannes Stezenbach
2004-05-01 22:14 ` Andrew Morton
2004-05-01 22:37 ` Linus Torvalds
2004-05-01 23:10 ` Andrew Morton
2004-05-01 23:55 ` Linus Torvalds
2004-05-02 0:00 ` Chris Wedgwood
2004-05-02 0:03 ` Andrew Morton
2004-05-02 0:28 ` Linus Torvalds
2004-05-02 0:51 ` Andrew Morton
2004-05-02 1:16 ` Paul Mackerras
2004-05-03 18:06 ` David Mosberger
2004-05-03 18:20 ` Linus Torvalds
2004-05-03 18:30 ` David Mosberger
2004-05-03 18:37 ` Linus Torvalds
2004-05-03 20:42 ` Linus Torvalds
2004-05-03 20:56 ` David Mosberger
2004-05-03 21:07 ` Arjan van de Ven
2004-05-03 22:39 ` David Mosberger
2004-05-04 7:55 ` Arjan van de Ven
2004-05-04 16:44 ` David Mosberger
2004-05-04 16:47 ` Arjan van de Ven
2004-05-03 21:02 ` Andrew Morton
2004-05-03 21:06 ` Arjan van de Ven
2004-05-03 21:16 ` viro
2004-05-03 21:24 ` Jörn Engel
2004-05-03 21:54 ` viro
2004-05-03 22:01 ` viro
2004-05-03 22:33 ` Jörn Engel
2004-05-04 0:14 ` viro
2004-05-04 9:23 ` Jörn Engel
2004-05-04 12:13 ` Stephen Smalley
2004-04-28 14:34 ` Linux 2.6.6-rc3 (compile stats) John Cherry
2004-04-28 17:28 ` Linux 2.6.6-rc3 Maciej Soltysiak
2004-04-29 1:02 ` Craig Thomas
2004-04-29 0:59 ` CaT
2004-04-29 17:10 ` Craig Thomas
2004-04-29 2:11 ` Andrew Morton
2004-04-29 15:59 ` Craig Thomas
2004-04-29 17:01 ` Jacek Kawa
2004-04-29 17:32 ` Sam Ravnborg
2004-04-30 1:05 ` Jacek Kawa
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=20040501112432.GE2541@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=eyal@eyal.emu.id.au \
--cc=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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