OpenCores
no use no use 1/1 no use no use
Problem faced when building the latest kernel ( 3.3.0-rc3 ) for ARCH=or32 and CROSS_COMPILE=or32-elf-
by Shreesha on Apr 3, 2012
Shreesha
Posts: 4
Joined: Mar 26, 2012
Last seen: Apr 17, 2012
Hi All,

1 > I have the following things installed in my machine

a > Latest GNU toolchain ie Newlib toolchain 1.0rc1
b > Or1ksim 0.5.0 release candidate 2
c > Linux kernel from GIT ie version 3.3.0-rc3
d > Uclibc from GIT

2 > I have built the simulator for target = or32-uclinux

3 > I have built the GNU tool chain by specifying all as the option (ie both Newlib and Uclibc toolchains)

4 > I have followed the standard path convention as mentioned in the guide

With these configurations I am able to simulate a simple C program with GDB on the simulator,I am also able to build the kernel with default configuration and run it on the simulator,but the problem I am facing is when I try building the kernel specifically for ARCH=or32 and CROSS_COMPILE=or32-elf-,it gives me an make error stating or32 architecture is not part of arch directory. By looking at similar posts I found that OpenRISC patch for kernel version 3.3.0-rc3 is not available yet (Please correct me if I am wrong),I tried reverting back to kernel version 2.6.34 (with the necessary patch being applied) and building it again by specifying all as the option,its giving me an error stating openrisc architecture is not part of arch directory.

Kindly suggest me a way forward,so that I can build the latest kernel for ARCH=or32 and CROSS_COMPILE=or32-elf-

Regards,
Shreesha Rao P
RE: Problem faced when building the latest kernel ( 3.3.0-rc3 ) for ARCH=or32 and CROSS_COMPILE=or32-elf-
by jeremybennett on Apr 3, 2012
jeremybennett
Posts: 815
Joined: May 29, 2008
Last seen: Jun 13, 2019
Hi All,

1 > I have the following things installed in my machine

a > Latest GNU toolchain ie Newlib toolchain 1.0rc1
b > Or1ksim 0.5.0 release candidate 2
c > Linux kernel from GIT ie version 3.3.0-rc3
d > Uclibc from GIT

2 > I have built the simulator for target = or32-uclinux

3 > I have built the GNU tool chain by specifying all as the option (ie both Newlib and Uclibc toolchains)

4 > I have followed the standard path convention as mentioned in the guide

With these configurations I am able to simulate a simple C program with GDB on the simulator,I am also able to build the kernel with default configuration and run it on the simulator,but the problem I am facing is when I try building the kernel specifically for ARCH=or32 and CROSS_COMPILE=or32-elf-,it gives me an make error stating or32 architecture is not part of arch directory. By looking at similar posts I found that OpenRISC patch for kernel version 3.3.0-rc3 is not available yet (Please correct me if I am wrong),I tried reverting back to kernel version 2.6.34 (with the necessary patch being applied) and building it again by specifying all as the option,its giving me an error stating openrisc architecture is not part of arch directory.

Kindly suggest me a way forward,so that I can build the latest kernel for ARCH=or32 and CROSS_COMPILE=or32-elf-

Regards,
Shreesha Rao P

Hi Shreesha

For Linux the architecture is "openrisc", even though the tool chain is "or32". So you need

    ARCH=openrisc CROSS_COMPILE=or32-elf-
    

Jonas Bonn (author of the modern OpenRISC Linux port) explains that the port will work not just with the existing OpenRISC 1000 tool chain (known as or32) but with future OpenRISC architectures, hence the naming "openrisc".

HTH

Jeremy

--
Tel: +44 (1590) 610184
Cell: +44 (7970) 676050
SkypeID: jeremybennett
Email: jeremy.bennett@embecosm.com
Web: www.embecosm.com

RE: Problem faced when building the latest kernel ( 3.3.0-rc3 ) for ARCH=or32 and CROSS_COMPILE=or32-elf-
by Shreesha on Apr 3, 2012
Shreesha
Posts: 4
Joined: Mar 26, 2012
Last seen: Apr 17, 2012
Hello Jeremy,

Thanks a lot for helping me out,I am now able to build the kernel successfully.

Regards,
Shreesha Rao P
no use no use 1/1 no use no use
© copyright 1999-2026 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.