Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S964960AbWLMNVW (ORCPT ); Wed, 13 Dec 2006 08:21:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964956AbWLMNVW (ORCPT ); Wed, 13 Dec 2006 08:21:22 -0500 Received: from krak.alatek.krakow.pl ([217.96.2.229]:5940 "EHLO krak.alatek.krakow.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964960AbWLMNVV (ORCPT ); Wed, 13 Dec 2006 08:21:21 -0500 X-Greylist: delayed 1307 seconds by postgrey-1.27 at vger.kernel.org; Wed, 13 Dec 2006 08:21:21 EST Message-ID: <457FF939.6080504@agmk.net> Date: Wed, 13 Dec 2006 13:59:37 +0100 From: =?UTF-8?B?UGF3ZcWCIFNpa29yYQ==?= User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: Meelis Roos Cc: Linux Kernel list Subject: Re: V4L2: __ucmpdi2 undefined on ppc References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1030 Lines: 27 Meelis Roos napisał(a): > MODPOST 618 modules > WARNING: "__ucmpdi2" [drivers/media/video/v4l2-common.ko] undefined! > > This 32-bit ppc architecture, using gcc version 4.1.2 20061115 > (prerelease) (Debian 4.1.1-21). .config below if important. > > __ucmpdi2 seems to be 64-bit comparision. gcc seems to use it for switch > statements on 64-bit values. > > drivers/media/video/v4l2-common.c::v4l2_norm_to_name seems to be one > such switch statement - type of id is v4l2_std_id which is 64-bit. > > Should ppc have __ucmpdi2 defined in arch-specific lib? Some other > architectures seem to implement it (arm, arm26, frv, h8300). maybe it's new gcc bug. [ already fixed ] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21237 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25724 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/