From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Tegra2 eldk4.2 builds
Date: Mon, 5 Mar 2012 18:34:57 +0100 [thread overview]
Message-ID: <201203051834.57403.marex@denx.de> (raw)
In-Reply-To: <5FBF8E85CA34454794F0F7ECBA79798F37971BB800@HQMAIL04.nvidia.com>
Dear Tom Warren,
> Marek,
>
> > -----Original Message-----
> > From: Marek Vasut [mailto:marex at denx.de]
> > Sent: Sunday, March 04, 2012 10:59 PM
> > To: Stephen Warren
> > Cc: albert.u.boot at aribaud.net; afleming at gmail.com; sjg at google.com; Tom
> > Warren; u-boot at lists.denx.de
> > Subject: Tegra2 eldk4.2 builds
> >
> > Dear Stephen Warren,
>
> I'm the Tegra U-Boot custodian. Stephen is a frequent & prolific
> contributor.
>
> > Tegra2 boards fail with gcc4.2.2 from eldk4.2:
> >
> > arm-linux-gcc (GCC) 4.2.2
> > 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 harmony board...
> > {standard input}: Assembler messages:
> > {standard input}:568: Error: bad expression -- `ldr sp,=#1073872896'
> > make[1]: *** [ap20.o] Error 1
> > make: *** [arch/arm/cpu/armv7/tegra2/libtegra2.o] Error 2
> > make: *** Waiting for unfinished jobs....
> > arm-linux-size: './u-boot': No such file
> >
> > Can you please check and submit a patch?
>
> Patch was submitted weeks ago - see
> http://patchwork.ozlabs.org/patch/141863/. I'm not sure if it's been
> pulled into mainline yet, but it will be in the next u-boot-tegra pull
> request I send (hopefully this week).
>
> Thanks,
>
Ok, thank you!
Best regards,
Marek Vasut
prev parent reply other threads:[~2012-03-05 17:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 5:59 [U-Boot] Tegra2 eldk4.2 builds Marek Vasut
2012-03-05 17:07 ` Tom Warren
2012-03-05 17:34 ` Marek Vasut [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=201203051834.57403.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