public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] cam_enc_4xx build failure
Date: Mon, 5 Mar 2012 07:13:51 +0100	[thread overview]
Message-ID: <201203050713.51779.marex@denx.de> (raw)

Dear Heiko Schocher,

cam_enc_4xx does not build with ELDK4.2 . Can you please come up with a patch?

Thanks in advance!

Copyright (C) 2007 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Configuring for cam_enc_4xx board...
cam_enc_4xx.c: In function 'menu_handle':
cam_enc_4xx.c:609: warning: dereferencing type-punned pointer will break strict-
aliasing rules
arm-linux-ld: u-boot-spl: Not enough room for program headers, try linking with 
-N
arm-linux-ld: final link failed: Bad value
make[1]: *** [/opt/work/jenkins/jobs/U-
Boot/workspace/workspace/compiler/eldk4.2/device/arm___cam_enc_4xx/spl/u-boot-
spl] Error 1
make: *** [spl/u-boot-spl.bin] Error 2
make: *** Waiting for unfinished jobs....
cmd_pxe.c: In function 'do_pxe_get':
cmd_pxe.c:334: warning: dereferencing type-punned pointer will break strict-
aliasing rules
cmd_pxe.c: In function 'get_relfile_envaddr':
cmd_pxe.c:374: warning: dereferencing type-punned pointer will break strict-
aliasing rules
arm-linux-size: './u-boot': No such file

--------------------- SUMMARY ----------------------------
Boards compiled: 1
Boards with warnings or errors: 1 ( cam_enc_4xx )
----------------------------------------------------------

Best regards,
Marek Vasut

             reply	other threads:[~2012-03-05  6:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05  6:13 Marek Vasut [this message]
2012-03-05  8:39 ` [U-Boot] cam_enc_4xx build failure Heiko Schocher
2012-03-05 14:30   ` Jason Hobbs
2012-03-05 15:36     ` Marek Vasut
2012-03-05 16:32   ` Wolfgang Denk
2012-03-07  7:10 ` Heiko Schocher

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=201203050713.51779.marex@denx.de \
    --to=marex@denx.de \
    --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