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