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
> wrote:
>> Hi Bin,
>>
>> Please use following repository with all needed software: linux / gcc / ...
>> https://github.com/openrisc
> Is that https://github.com/openrisc/or1k-gc
Hi Guillaume,
On Fri, Feb 5, 2016 at 9:04 PM, Guillaume REMBERT
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-too
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-
Hi Guillaume,
On Sun, Nov 8, 2015 at 10:37 PM, 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 tak
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,
--
5 matches
Mail list logo