From: Franck Jullien <franck.jullien@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: openrisc build problem
Date: Sun, 8 Feb 2015 20:35:40 +0100 [thread overview]
Message-ID: <CAJfOKBz5UuqQJtcuPP8nLwLymje7+mPkKDgDSC8yHfj_pbvD+w@mail.gmail.com> (raw)
In-Reply-To: <20150208232614.f704a8d152576f0c47ca9c50@gmail.com>
2015-02-08 20:26 GMT+01:00 Antony Pavlov <antonynpavlov@gmail.com>:
> Hi Franck !
>
> Here is sample openrisc barebox build error log :
>
> /opt/gcc-or1k-elf-4.8.1-x86_64/bin/or1k-elf-ld -Map barebox.map -o
> barebox -T arch/openrisc/cpu/barebox.lds --start-group
> common/built-in.o drivers/built-in.o commands/built-in.o
> lib/built-in.o crypto/built-in.o net/built-in.o fs/built-in.o
> arch/openrisc/boards/generic/built-in.o arch/openrisc/lib/built-in.o
> arch/openrisc/cpu/built-in.o arch/openrisc/dts/built-in.o
> defaultenv/built-in.o --end-group
> /opt/gcc-or1k-elf-4.8.1-x86_64/bin/or1k-elf-ld: target elf32-or32 not found
>
> $ /opt/gcc-or1k-elf-4.8.1-x86_64/bin/or1k-elf-ld --version
> GNU ld (GNU Binutils) 2.23.51.20121129
> Copyright 2012 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms
> of the GNU General Public License version 3 or (at your option) a later
> version.
> This program has absolutely no warranty.
>
>
> My current quick-and-dirty solution is :
>
> --- a/arch/openrisc/cpu/barebox.lds.S
> +++ b/arch/openrisc/cpu/barebox.lds.S
> @@ -16,7 +16,7 @@
> #include <config.h>
> #include <asm-generic/barebox.lds.h>
>
> -OUTPUT_FORMAT("elf32-or32", "elf32-or32", "elf32-or32")
> +/* OUTPUT_FORMAT("elf32-or32", "elf32-or32", "elf32-or32") */
> __DYNAMIC = 0;
>
> MEMORY
>
>
> Franck !
> Please comment this message !
>
> --
> Best regards,
> Antony Pavlov
Hi,
Yes I know :) Until now, the official openrisc toolchain was called or32.
However, the new one (and maintained one) is called or1k. So we need
to change "elf32-or32" to "elf32-or1k" in barebox.lds.S.
Feel free to send a patch. Or I'll do that later.
Franck.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-02-08 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-08 19:26 Antony Pavlov
2015-02-08 19:35 ` Franck Jullien [this message]
2015-02-09 7:40 ` Sascha Hauer
2015-02-09 11:26 ` Franck Jullien
2015-02-09 11:49 ` Antony Pavlov
2015-02-09 19:24 ` Franck Jullien
2015-02-10 23:16 ` Antony Pavlov
2015-02-11 9:44 ` Sascha Hauer
2015-02-13 19:06 ` Sascha Hauer
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=CAJfOKBz5UuqQJtcuPP8nLwLymje7+mPkKDgDSC8yHfj_pbvD+w@mail.gmail.com \
--to=franck.jullien@gmail.com \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
/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