Skip to contentSkip to conversation

openrisc: updating build tools naming convention

PATCH In review Guillaume REMBERT 3 participants 6 messages Nov 8, 2015 – Feb 13, 2016 Openrisc architecture

lore
Share & tools
lore

Guillaume REMBERT

author
#0 lore raw

PATCH 1/1 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,

Signature · 25 lines
____________________________________________

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(-)
arch/openrisc/config.mk +1 -1
index cd95f24..bfdb71f 100644
@@ -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

arch/openrisc/cpu/u-boot.lds +1 -1
index d9bb7b7..854088b 100644
@@ -1,5 +1,5 @@
 #include <config.h>
-OUTPUT_ARCH(or32)
+OUTPUT_ARCH(or1k)
 __DYNAMIC  =  0;
 
 MEMORY

-------------- next part --------------
A non-text attachment was scrubbed...
Name: guillaume_rembert.vcf
Type: text/x-vcard
Size: 381 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151108/578edcf7/attachment.vcf>

#1 lore raw

arch/openrisc/config.mk

Quoted 12 lines · Guillaume REMBERT

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,

arch/openrisc/config.mk +0 -0
index cd95f24..bfdb71f 100644

Applied to u-boot/master, thanks!

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20151112/f901cd0b/attachment.sig>
#2 lore raw

PATCH 1/1 openrisc: updating build tools naming convention

In reply to Guillaume REMBERT

Hi Guillaume,

Quoted 56 lines · Guillaume REMBERT

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(-)
arch/openrisc/config.mk +1 -1
index cd95f24..bfdb71f 100644
@@ -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

arch/openrisc/cpu/u-boot.lds +0 -0
index d9bb7b7..854088b 100644

arch/openrisc/cpu/u-boot.lds line 4

Quoted 5 lines
arch/openrisc/cpu/u-boot.lds +1 -1
@@ -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

author
#3 lore raw

PATCH 1/1 openrisc: updating build tools naming convention

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 :

Quoted 71 lines

Hi Guillaume,

Quoted 56 lines · Guillaume REMBERT

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(-)
arch/openrisc/config.mk +1 -1
index cd95f24..bfdb71f 100644
@@ -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

arch/openrisc/cpu/u-boot.lds +0 -0
index d9bb7b7..854088b 100644

arch/openrisc/cpu/u-boot.lds line 4

Quoted 5 lines
arch/openrisc/cpu/u-boot.lds +1 -1
@@ -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

#4 lore raw

PATCH 1/1 openrisc: updating build tools naming convention

Hi Guillaume,

Quoted 4 lines · Guillaume REMBERT

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?

Quoted 7 lines

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?

Quoted 10 lines

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)

Quoted 4 lines

Kind regards,

Guillaume

Please avoid top-posting.

Quoted 17 lines

Le 25/01/2016 10:50, Bin Meng a ?crit :

Quoted 15 lines

Hi Guillaume,

Quoted 11 lines · Guillaume REMBERT

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

author
#5 lore raw

PATCH 1/1 openrisc: updating build tools naming convention

Hi Bin,

Le 06/02/2016 05:11, Bin Meng a ?crit :

Quoted 9 lines

Hi Guillaume,

Quoted 4 lines · Guillaume REMBERT

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

Quoted 8 lines
Quoted 6 lines

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

Quoted 10 lines
Quoted 10 lines

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)

Quoted 5 lines
Quoted 4 lines

Kind regards,

Guillaume

Please avoid top-posting.

Is it better like this?

Quoted 13 lines
Quoted 13 lines

Le 25/01/2016 10:50, Bin Meng a ?crit :

Quoted 12 lines

Hi Guillaume,

Quoted 8 lines · Guillaume REMBERT

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?

Quoted 7 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

Kind regards,

--

[snip]

Regards,
Bin

Cheers,

Guillaume