From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755950AbbFPGYs (ORCPT ); Tue, 16 Jun 2015 02:24:48 -0400 Received: from mail-ob0-f177.google.com ([209.85.214.177]:34172 "EHLO mail-ob0-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753815AbbFPGYm (ORCPT ); Tue, 16 Jun 2015 02:24:42 -0400 MIME-Version: 1.0 In-Reply-To: <20150615202357.GD11429@waldemar-brodkorb.de> References: <20150615202357.GD11429@waldemar-brodkorb.de> Date: Tue, 16 Jun 2015 08:24:41 +0200 X-Google-Sender-Auth: zU9tvhu0JYlOZvu-6QJVUhN8KfY Message-ID: Subject: Re: m68k compile issue with 4.0.5 From: Geert Uytterhoeven To: Waldemar Brodkorb Cc: "linux-kernel@vger.kernel.org" , uClinux development list Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Waldemar, On Mon, Jun 15, 2015 at 10:23 PM, Waldemar Brodkorb wrote: > I am trying to build a M68K (Coldfire no-MMU) kernel for Qemu-system-m68k. > > With 4.0.4 everything is fine. With 4.0.5 I get following compile > error: > adk-uclinux-gcc -Wp,-MD,mm/.nommu.o.d -nostdinc -isystem > /home/wbx/m68k/toolchain_qemu-m68k_uclibc-ng_m68k_nommu/usr/lib/gcc/m68k-openadk-uclinux-uclibc/4.9.2/include > -I./arch/m68k/include -Iarch/m68k/include/generated/uapi > -Iarch/m68k/include/generated -Iinclude -I./arch/m68k/include/uapi > -Iarch/m68k/include/generated/uapi -I./include/uapi > -Iinclude/generated/uapi -include ./include/linux/kconfig.h > -D__KERNEL__ -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs > -fno-strict-aliasing -fno-common > -Werror-implicit-function-declaration -Wno-format-security > -std=gnu89 -mcpu=5208 -pipe -DUTS_SYSNAME=\"uClinux\" -D__uClinux__ > -fno-delete-null-pointer-checks -Os -Wno-maybe-uninitialized > --param=allow-store-data-races=0 -Wframe-larger-than=1024 > -fno-stack-protector -Wno-unused-but-set-variable > -fomit-frame-pointer -fno-var-tracking-assignments > -Wdeclaration-after-statement -Wno-pointer-sign -fno-strict-overflow > -fconserve-stack -Werror=implicit-int -Werror=strict-prototypes > -Werror=date-time -DCC_HAVE_ASM_GOTO -D"KBUILD_STR(s)=#s" > -D"KBUILD_BASENAME=KBUILD_STR(nommu)" > -D"KBUILD_MODNAME=KBUILD_STR(nommu)" -c -o mm/nommu.o mm/nommu.c > mm/nommu.c: In function 'delete_vma': > mm/nommu.c:861:3: error: implicit declaration of function 'vma_fput' > [-Werror=implicit-function-declaration] > vma_fput(vma); > ^ > cc1: some warnings being treated as errors > > Any idea what change breaks the compile? I tried a few m68knommu defconfigs, but can't reproduce it. Is this a plain v4.0.5? I can't find the offending call to vma_fput(). "git grep vma_fput" tells me there's no "vma_fput" in the kernel sources? Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds