All of lore.kernel.org
 help / color / mirror / Atom feed
* [U-Boot] [PATCH] openrisc: updating build tools naming convention
@ 2015-11-08 14:37 Guillaume REMBERT
  2015-11-13  1:31 ` [U-Boot] " Tom Rini
  2016-01-25  9:50 ` [U-Boot] [PATCH] " Bin Meng
  0 siblings, 2 replies; 6+ messages in thread
From: Guillaume REMBERT @ 2015-11-08 14:37 UTC (permalink / raw)
  To: u-boot

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;

 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>

^ permalink raw reply related	[flat|nested] 6+ messages in thread

* [U-Boot] openrisc: updating build tools naming convention
  2015-11-08 14:37 [U-Boot] [PATCH] openrisc: updating build tools naming convention Guillaume REMBERT
@ 2015-11-13  1:31 ` Tom Rini
  2016-01-25  9:50 ` [U-Boot] [PATCH] " Bin Meng
  1 sibling, 0 replies; 6+ messages in thread
From: Tom Rini @ 2015-11-13  1:31 UTC (permalink / raw)
  To: u-boot

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!

-- 
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>

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] [PATCH] openrisc: updating build tools naming convention
  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 ` Bin Meng
  2016-02-05 13:04   ` Guillaume REMBERT
  1 sibling, 1 reply; 6+ messages in thread
From: Bin Meng @ 2016-01-25  9:50 UTC (permalink / raw)
  To: u-boot

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] [PATCH] openrisc: updating build tools naming convention
  2016-01-25  9:50 ` [U-Boot] [PATCH] " Bin Meng
@ 2016-02-05 13:04   ` Guillaume REMBERT
  2016-02-06  4:11     ` Bin Meng
  0 siblings, 1 reply; 6+ messages in thread
From: Guillaume REMBERT @ 2016-02-05 13:04 UTC (permalink / raw)
  To: u-boot

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] [PATCH] openrisc: updating build tools naming convention
  2016-02-05 13:04   ` Guillaume REMBERT
@ 2016-02-06  4:11     ` Bin Meng
  2016-02-13 17:35       ` Guillaume REMBERT
  0 siblings, 1 reply; 6+ messages in thread
From: Bin Meng @ 2016-02-06  4:11 UTC (permalink / raw)
  To: u-boot

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

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [U-Boot] [PATCH] openrisc: updating build tools naming convention
  2016-02-06  4:11     ` Bin Meng
@ 2016-02-13 17:35       ` Guillaume REMBERT
  0 siblings, 0 replies; 6+ messages in thread
From: Guillaume REMBERT @ 2016-02-13 17:35 UTC (permalink / raw)
  To: u-boot


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

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2016-02-13 17:35 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2016-02-06  4:11     ` Bin Meng
2016-02-13 17:35       ` Guillaume REMBERT

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.