public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3: EVM: Linker errors across tool chain versions
Date: Thu, 16 Dec 2010 17:55:57 +0100	[thread overview]
Message-ID: <4D0A449D.9000809@ahsoftware.de> (raw)
In-Reply-To: <4D0A2E3B.9090901@googlemail.com>

Am 16.12.2010 16:20, schrieb Dirk Behme:
> On 16.12.2010 14:47, Alexander Holler wrote:
>> I'm working with the master (f8689b9eb3a7f6925cd50404a12479889188c510)
>> on a beagleboard
>             ^^^^^^^^^^^^^^
>
> ?
>
> This thread is about a (linking) issue building 'omap3_evm'.
>
> The Beagle support in the master you mention above is said to be fine.
Sorry for going into this thread, but I've heard such a "fine" something 
like a dozens time before. And the beagleboard and the EVM are using the 
same start.S, so I thought I throw something into this thread about 
problems across tool chain versions. Even when it isn't about linker errors.

I will be silent again.

Regards,

Alexander

  reply	other threads:[~2010-12-16 16:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  8:25 [U-Boot] OMAP3: EVM: Linker errors across tool chain versions Dirk Behme
2010-12-12 10:08 ` Albert ARIBAUD
2010-12-12 10:32   ` Dirk Behme
2010-12-12 11:40     ` Albert ARIBAUD
2010-12-14 15:42       ` Dirk Behme
2010-12-14 16:01         ` Albert ARIBAUD
2010-12-14 16:14           ` Wolfgang Denk
2010-12-16 13:47           ` Alexander Holler
2010-12-16 14:31             ` Alexander Holler
2010-12-16 15:20             ` Dirk Behme
2010-12-16 16:55               ` Alexander Holler [this message]
2010-12-14 16:21         ` Wolfgang Denk
2010-12-16 10:10           ` Dirk Behme
2010-12-17 10:39             ` Dirk Behme
2010-12-30 12:04               ` Premi, Sanjeev

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=4D0A449D.9000809@ahsoftware.de \
    --to=holler@ahsoftware.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