public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Undefined reference to `boot_relocate_fdt'
Date: Mon, 03 Nov 2008 19:43:15 -0500	[thread overview]
Message-ID: <490F9AA3.2050703@gmail.com> (raw)
In-Reply-To: <fd90355f0811031328n6f0ec0c4r124bcceccb99130d@mail.gmail.com>

Juan Pablo G?mez wrote:
> His I'm trying to build u-boot for a xupv2p board, but with the newest
> version this is appearing during the make :
> *
> $make xupv2p_config
> $make*
> 
> -Map u-boot.map -o u-boot
> common/libcommon.a(cmd_bootm.o): In function `do_bootm_subcommand':
> /home/juanwalker/software/projects/u-boot/common/cmd_bootm.c:505: undefined
> reference to `boot_relocate_fdt'
> make: *** [u-boot] Error 1

Hi Juan,

That is odd.  It works for me on a PowerPC target (I don't have 
microblaze support set up).  Your config has CONFIG_LIBFDT enabled, 
which is why do_bootm_subcommand is calling boot_relocate_fdt.  I don't 
see any obvious reason why boot_relocate_fdt isn't in your build (it is 
defined in common/image.c and enabled by CONFIG_LIBFDT).

One thing you could do is to save your make output into a log file
   make > make.log
and then find the line that compiles image.c (it likely will be the 
*second* time, the first time is making host tools).  Cut and paste it 
onto the command line (in the common/ subdirectory) BUT CHANGE the flags 
at the end of the gcc command from:
   -c -o image.o image.c
to:
   -C -E -o image.pp image.c
This stops after running the preprocessor and puts the result in 
"image.pp".  Maybe you can get a clue what happened to your 
boot_relocate_fdt() from that???

Best regards,
gvb

  reply	other threads:[~2008-11-04  0:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 21:28 [U-Boot] Undefined reference to `boot_relocate_fdt' Juan Pablo Gómez 
2008-11-04  0:43 ` Jerry Van Baren [this message]
2008-11-04 19:08 ` Michal Simek

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=490F9AA3.2050703@gmail.com \
    --to=gvb.uboot@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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