[lkml]   [2011]   [Aug]   [8]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Build failure: bisected: v3.1-rc1 with config ARCH_OMAP && !ARCH_OMAP4 fails with linker error

    On Mon, 8 Aug 2011, Daniel Morsing wrote:

    > Building the v3.1-rc1 kernel with ARCH_OMAP && !ARCH_OMAP4 support fails
    > on linking with the following error
    > ...
    > LD .tmp_vmlinux1
    > arch/arm/mach-omap2/built-in.o:(.data+0xf7d8): undefined reference to `omap4430_phy_init'
    > arch/arm/mach-omap2/built-in.o:(.data+0xf7dc): undefined reference to `omap4430_phy_exit'
    > arch/arm/mach-omap2/built-in.o:(.data+0xf7e0): undefined reference to `omap4430_phy_power'
    > arch/arm/mach-omap2/built-in.o:(.data+0xf7e4): undefined reference to `omap4430_phy_set_clk'
    > arch/arm/mach-omap2/built-in.o:(.data+0xf7e8): undefined reference to `omap4430_phy_suspend'
    > I've bisected the first bad commit to "OMAP4: Move common twl6030
    > configuration to twl-common" (commit-id
    > b22f954bae35be115a10c6426dc070f7d652b32e). The problem seems to be
    > unconditionally taking a function pointer to an omap4430 specific
    > function in arch/arm/mach-omap2/twl-common.c. The definition for
    > omap4430_phy_init and friends is in
    > arch/arm/mach-omap2/omap_phy_internal.c, which is only compiled when
    > building with support for one of the omap4430 boards.

    Thanks for the bisect; this should be fixed by

    - Paul

     \ /
      Last update: 2011-08-08 22:39    [W:0.020 / U:41.348 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site