LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastien Dugue <sebastien.dugue@bull.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: 64-bit build failure without hugetlbfs
Date: Tue, 5 Aug 2008 15:10:55 +0200	[thread overview]
Message-ID: <20080805151055.5e2cdc21@bull.net> (raw)
In-Reply-To: <1217936390.3603.34.camel@johannes.berg>

On Tue, 05 Aug 2008 13:39:49 +0200 Johannes Berg <johannes@sipsolutions.net> wrote:

>   LD      vmlinux.o
> mm/built-in.o: In function `.arch_get_unmapped_area_topdown':
> (.text+0x1d084): multiple definition of `.arch_get_unmapped_area_topdown'
> arch/powerpc/mm/built-in.o:(.text+0x7240): first defined here
> mm/built-in.o: In function `arch_get_unmapped_area_topdown':
> (.opd+0x2730): multiple definition of `arch_get_unmapped_area_topdown'
> arch/powerpc/mm/built-in.o:(.opd+0x918): first defined here
> mm/built-in.o: In function `.arch_get_unmapped_area':
> (.text+0x1ce3c): multiple definition of `.arch_get_unmapped_area'
> arch/powerpc/mm/built-in.o:(.text+0x72b8): first defined here
> mm/built-in.o: In function `arch_get_unmapped_area':
> (.opd+0x2718): multiple definition of `arch_get_unmapped_area'
> arch/powerpc/mm/built-in.o:(.opd+0x930): first defined here
> make: *** [vmlinux.o] Error 1
> 
> enabling hugetlbfs cures it.
> 
> johannes

  Or disabling CONFIG_PPC_64K_PAGES if you do not want to enable hugetlbfs...

  Sebastien.

      reply	other threads:[~2008-08-05 13:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 11:39 64-bit build failure without hugetlbfs Johannes Berg
2008-08-05 13:10 ` Sebastien Dugue [this message]

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=20080805151055.5e2cdc21@bull.net \
    --to=sebastien.dugue@bull.net \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.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