From: Simon Schwarz <simonschwarzcor@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Latest SPL pushed to omapzoom
Date: Tue, 19 Jul 2011 12:49:31 +0200 [thread overview]
Message-ID: <20110719124931.2fa64fba@Zitronenbaum> (raw)
In-Reply-To: <4E251560.7090506@ti.com>
Hi Aneesh,
If I use your omap_upstream the build fails with:
make ARCH=arm CROSS_COMPILE=$CROSS_COMPILE omap4_panda_config
Configuring for omap4_panda board...
simon at Zitronenbaum:~/tmp/test/u-boot$ make ARCH=arm
CROSS_COMPILE=$CROSS_COMPILE all Generating include/autoconf.mk
cc1: error: bad value (armv5) for -march= switch
Generating include/autoconf.mk.dep
cc1: error: bad value (armv5) for -march= switch
gcc -DDO_DEPS_ONLY \
-g -Os -fno-common -ffixed-r8 -msoft-float
-D__KERNEL__ -I/home/simon/tmp/test/u-boot/include -fno-builtin
-ffreestanding -nostdinc
-isystem /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/include
-pipe -DCONFIG_ARM -D__ARM__ -march=armv5 -Wall
-Wstrict-prototypes \ -o lib/asm-offsets.s lib/asm-offsets.c -c -S
lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch
make: *** [lib/asm-offsets.s] Error 1
Any idea?
Regards
Simon
On Tue, 19 Jul 2011 10:55:52 +0530
Aneesh V <aneesh@ti.com> wrote:
> Aargh.. That was a newly added file for which I forgot to do 'git
> add', so it didn't get included in the patch.
>
> It's fixed now and updated in the same branch(again in a
> non-fast-forward manner as my patches are not yet upstream).
>
> I have created another branch 'omap_upstream_wip' with the same
> content. I will now try to keep the 'omap_upstream' branch stable
> until my patches are up-stream and I rebase again. Until then any
> updates I have will be added to omap_upstream_wip in a
> non-fastforward manner.
>
> best regards,
> Aneesh
>
>
> On Monday 18 July 2011 11:44 PM, John Rigby wrote:
> > With this latest, the file omap_gpio.h seems to have gone missing.
> > Looks like most of it has moved to cpu.h but
> > arch/arm/cpu/armv7/omap-common/gpio.c still includes it. If it just
> > remove the include then METHOD_GPIO_24XX is not defined anywhere.
> >
> > --john
> >
> > On Mon, Jul 18, 2011 at 7:48 AM, Aneesh V<aneesh@ti.com> wrote:
> >> I have deleted this branch and re-created it with the latest
> >> patches I have submitted in the new SPL framework including 4460
> >> support.
> >>
> >> On Friday 08 July 2011 07:41 PM, Aneesh V wrote:
> >>>
> >>>
> >>> http://dev.omapzoom.org/?p=bootloader/u-boot.git;a=shortlog;h=refs/heads/omap_upstream
> >>>
> >>>
> >>> This is for interim use since some of you asked. SPL framework is
> >>> getting re-designed in the list. I will be updating with the new
> >>> framework shortly.
> >>>
> >>> Also, 4460 support will be pushed shortly.
> >>>
> >>> br,
> >>> Aneesh
> >>
next parent reply other threads:[~2011-07-19 10:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E17100D.2000804@ti.com>
[not found] ` <4E2439AB.7090706@ti.com>
[not found] ` <CADDGHU9TVe8zdp0w3-fCzueGCF07zghdQ-6ppJBGGiyi9T9KWw@mail.gmail.com>
[not found] ` <4E251560.7090506@ti.com>
2011-07-19 10:49 ` Simon Schwarz [this message]
2011-07-19 11:26 ` [U-Boot] Latest SPL pushed to omapzoom Aneesh V
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=20110719124931.2fa64fba@Zitronenbaum \
--to=simonschwarzcor@googlemail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.