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