public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Guillaume REMBERT <guillaume.rembert@euryecetelecom.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] openrisc: updating build tools naming convention
Date: Fri, 5 Feb 2016 14:04:20 +0100	[thread overview]
Message-ID: <56B49DD4.6090307@euryecetelecom.com> (raw)
In-Reply-To: <CAEUhbmW4sjFeGbHv3Z-hQwVB-sMHVFA0MSE8e57OS3951v8fdA@mail.gmail.com>

Hi Bin,

Please use following repository with all needed software: linux / gcc / ...
https://github.com/openrisc

The current toolchain is called or1k-toolchain (or32-toolchain is the
old name).

I used  the toolchain from there (and I also used latest gcc from that
time). My version:
# /home/or1k-toolchain/bin/or1k-elf-c++ -v
Utilisation des specs internes.
COLLECT_GCC=/home/or1k-toolchain/bin/or1k-elf-c++
COLLECT_LTO_WRAPPER=/home/or1k-toolchain/libexec/gcc/or1k-elf/4.9.2/lto-wrapper
Target: or1k-elf
Configur? avec: ../or1k-gcc/configure --target=or1k-elf
--prefix=/home/or1k-toolchain --enable-languages=c,c++ --disable-shared
--disable-libssp --with-newlib
Mod?le de thread: single
gcc version 4.9.2 (GCC)

Kind regards,

Guillaume


Le 25/01/2016 10:50, Bin Meng a ?crit :
> Hi Guillaume,
>
> On Sun, Nov 8, 2015 at 10:37 PM, Guillaume REMBERT
> <guillaume.rembert@euryecetelecom.com> wrote:
>> Dear u-boot community,
>>
>> I just made a small change on the openrisc-generic platform
>> configuration to take in account the new naming convention (or1k instead
>> of or32, so the build process gets fine).
>>
>> Could you take care to review and approve the following patch, please?
>>
>> Kind regards,
>>
>> --
>> ____________________________________________
>>
>> Guillaume REMBERT
>> Phone/Fax: 0033 9 72 32 55 76
>> Mobile: 0033 6 83 27 98 19
>> E-Mail: guillaume.rembert at euryecetelecom.com
>> ____________________________________________
>>
>> On Earth and Space...
>>           EURYECE TELECOM
>> ... where failure is not an option
>> http://www.euryecetelecom.com
>> __________________________________
>>
>>
>>
>>
>>
>>
>>
>>
>> 51d13f5355943e14db4b95a7f8ae4cd87eba1fe1
>>  arch/openrisc/config.mk      | 2 +-
>>  arch/openrisc/cpu/u-boot.lds | 2 +-
>>  2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/openrisc/config.mk b/arch/openrisc/config.mk
>> index cd95f24..bfdb71f 100644
>> --- a/arch/openrisc/config.mk
>> +++ b/arch/openrisc/config.mk
>> @@ -6,7 +6,7 @@
>>  #
>>
>>  ifeq ($(CROSS_COMPILE),)
>> -CROSS_COMPILE := or32-elf-
>> +CROSS_COMPILE := or1k-elf-
>>  endif
>>
>>  # r10 used for global object pointer, already set in OR32 GCC but just
>> to be
>> diff --git a/arch/openrisc/cpu/u-boot.lds b/arch/openrisc/cpu/u-boot.lds
>> index d9bb7b7..854088b 100644
>> --- a/arch/openrisc/cpu/u-boot.lds
>> +++ b/arch/openrisc/cpu/u-boot.lds
>> @@ -1,5 +1,5 @@
>>  #include <config.h>
>> -OUTPUT_ARCH(or32)
>> +OUTPUT_ARCH(or1k)
>>  __DYNAMIC  =  0;
>>
> Can you please mention which toolchain are you using for or1k?
> Currently the kernel.org or32 toolchain cannot build U-Boot anymore
> with your patch.
>
> Regards,
> Bin

  reply	other threads:[~2016-02-05 13:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-08 14:37 [U-Boot] [PATCH] openrisc: updating build tools naming convention Guillaume REMBERT
2015-11-13  1:31 ` [U-Boot] " Tom Rini
2016-01-25  9:50 ` [U-Boot] [PATCH] " Bin Meng
2016-02-05 13:04   ` Guillaume REMBERT [this message]
2016-02-06  4:11     ` Bin Meng
2016-02-13 17:35       ` Guillaume REMBERT

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=56B49DD4.6090307@euryecetelecom.com \
    --to=guillaume.rembert@euryecetelecom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox