public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Introduce a new linker flag LDFLAGS_FINAL
Date: Tue, 22 Feb 2011 20:39:20 +0100	[thread overview]
Message-ID: <20110222193920.C2CE1D52302@gemini.denx.de> (raw)
In-Reply-To: <1297975097.1973.20.camel@haiying-laptop>

Dear Haiying Wang,

In message <1297975097.1973.20.camel@haiying-laptop> you wrote:
>
> > Your scripts works fine. Now I only get one pair of diff which are
> > System.map.mpc7448hpc2.diff  u-boot.map.mpc7448hpc2.diff, because
> > mpc7448hpc2 failed to build:
> > "
> > Configuring for mpc7448hpc2 board...
> > cc1: error: AltiVec and E500 instructions cannot coexist
> > cc1: error: AltiVec and E500 instructions cannot coexist
> > lib/asm-offsets.c:1: error: AltiVec and E500 instructions cannot coexist
> > make: *** [lib/asm-offsets.s] Error 1
> > make: *** Waiting for unfinished jobs....

You are using a broken or incorrectly configured (for the purpose)
tool chain then.  I don't see such problems with ELDK.


> Sorry, I ignored some other info just now. Not only 7448 but also some
> other boards failed to build, you can get the failed info from the
> beforepatch.txt and afterpatch.txt I sent yesterday. The final result
> should be:
> 
> haiying at haiying-laptop:~/Opensource/Denx/u-boot$ ls -s *.diff
> 0 System.map.ESTEEM192E.diff         0 System.map.P2020DS.diff
> 0 System.map.ETX094.diff             0 System.map.sbc8641d.diff
> 0 System.map.LANTEC.diff             0 System.map.SPD823TS.diff
> 0 System.map.mpc7448hpc2.diff        0 System.map.xpedite517x.diff
> 0 System.map.MPC8610HPCD.diff        0 u-boot.map.mpc7448hpc2.diff
> 0 System.map.MPC8641HPCN_36BIT.diff  0 u-boot.map.MPC8610HPCD.diff
> 0 System.map.MPC8641HPCN.diff        0 u-boot.map.MPC8641HPCN_36BIT.diff
> 0 System.map.mpq101.diff             0 u-boot.map.MPC8641HPCN.diff
> 0 System.map.P2020DS_36BIT.diff      0 u-boot.map.sbc8641d.diff
> 0 System.map.P2020DS_DDR2.diff       0 u-boot.map.xpedite517x.diff
> 
> The above boards failed to build thus the diff files were generated but the contents are all 0. 

All these boards build fine for me.

> All the other boards should not have difference in System.map/u-boot.map before and after applying the LDFLAGS_FINAL patch.

As it's mostly unmaintained and/or Freescale boards that are untested
because of your tool chain issues I guess we can assume the test
passed.

Thanks.

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
To get something done, a committee should consist  of  no  more  than
three men, two of them absent.

      reply	other threads:[~2011-02-22 19:39 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-31 18:32 [U-Boot] [PATCH] Introduce a new linker flag LDFLAGS_FINAL Haiying.Wang at freescale.com
2011-01-31 19:33 ` Wolfgang Denk
2011-01-31 19:55   ` Scott Wood
2011-02-01  7:34     ` Wolfgang Denk
2011-02-01 14:59       ` Haiying Wang
2011-02-01 16:24       ` Scott Wood
2011-02-01 19:32         ` Wolfgang Denk
2011-02-01 19:51           ` Scott Wood
2011-02-01 20:20             ` Wolfgang Denk
2011-02-01 20:40               ` Scott Wood
2011-02-04 15:52                 ` Haiying Wang
2011-02-15  9:02                 ` Mike Frysinger
2011-02-16  0:51                   ` Scott Wood
2011-02-17  5:01                     ` Mike Frysinger
2011-02-04 22:56             ` Graeme Russ
2011-01-31 20:14   ` Haiying Wang
2011-01-31 20:30     ` Wolfgang Denk
     [not found]       ` <1297878184.1977.18.camel@haiying-laptop>
2011-02-16 18:29         ` Wolfgang Denk
2011-02-16 18:40           ` Haiying Wang
2011-02-16 18:58             ` Wolfgang Denk
2011-02-17  5:37               ` Mike Frysinger
2011-02-17  8:33                 ` Wolfgang Denk
2011-02-17 19:28               ` Haiying Wang
2011-02-17 20:38                 ` Haiying Wang
2011-02-22 19:39                   ` Wolfgang Denk [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=20110222193920.C2CE1D52302@gemini.denx.de \
    --to=wd@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