[U-Boot] [PATCH] openrisc: updating build tools naming convention
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,
On Sun, Nov 08, 2015 at 02:37:15PM +0000, Guillaume REMBERT 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,
diff --git a/arch/openrisc/config.mk b/arch/openrisc/config.mk index cd95f24..bfdb71f 100644
Applied to u-boot/master, thanks!
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@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
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@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
Hi Guillaume,
On Fri, Feb 5, 2016 at 9:04 PM, Guillaume REMBERT guillaume.rembert@euryecetelecom.com wrote:
Hi Bin,
Please use following repository with all needed software: linux / gcc / ... https://github.com/openrisc
Is that https://github.com/openrisc/or1k-gcc you are using?
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
I cannot find any pre-built toolchain on github. Did you build the toolchain on your own?
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
Please avoid top-posting.
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,
--
[snip]
Regards, Bin
Hi Bin,
Le 06/02/2016 05:11, Bin Meng a écrit :
Hi Guillaume,
On Fri, Feb 5, 2016 at 9:04 PM, Guillaume REMBERT guillaume.rembert@euryecetelecom.com wrote:
Hi Bin,
Please use following repository with all needed software: linux / gcc / ... https://github.com/openrisc
Is that https://github.com/openrisc/or1k-gcc you are using?
YES
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
I cannot find any pre-built toolchain on github. Did you build the toolchain on your own?
YES
Instructions to do it or to download prebuilt binaries can be found on Or1k wiki : http://opencores.org/or1k/OpenRISC_GNU_tool_chain
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
Please avoid top-posting.
Is it better like this?
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,
--
[snip]
Regards, Bin
Cheers,
Guillaume
participants (3)
-
Bin Meng -
Guillaume REMBERT -
Tom Rini