All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v9 00/17] Re-introduce h8300 architecture
Date: Tue, 28 Apr 2015 21:33:12 -0700	[thread overview]
Message-ID: <55405F08.7020508@roeck-us.net> (raw)
In-Reply-To: <87pp6oi2qy.wl-ysato@users.sourceforge.jp>

On 04/28/2015 10:25 AM, Yoshinori Sato wrote:
> At Tue, 28 Apr 2015 06:22:10 -0700,
> Guenter Roeck wrote:
>>
>> On Mon, Apr 27, 2015 at 02:35:07PM +0900, Yoshinori Sato wrote:
>>> Hello.
>>> I will re-introducing h8300.
>>>
>>
>> Hi,
>>
>> can you provide a link to a working toolchain, or provide directions
>> on how to build one ?
>
> h8300-unknown-linux in gcc / binutils development version.
> Patch of a release version has not been prepared yet.
>

Hi,

With a toolchain based on binutils 2.25 (patched), gcc 5.1 (unpatched), and newlib 1.20
(unpatched), I get for both h8300h-sim_defconfig and h8s-sim_defconfig:

./arch/h8300/kernel/vmlinux.lds:247: undefined symbol `jiffies_64' referenced in expression

I had to modify arch/h8300/Makefile a bit since the linker does not understand
-mh8300helf_linux and -mh8300self_linux; I had to use -mh8300helf and -mh8300self
instead. Maybe I am missing a binutils patch. I also had to use h8300-linux-elf
as target to convince gcc to accept it as valid target. Both should not result
in the undefined symbol error, though.

Guenter

  reply	other threads:[~2015-04-29  4:33 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  5:35 [PATCH v9 00/17] Re-introduce h8300 architecture Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 01/17] h8300: Assembly headers Yoshinori Sato
2015-04-27  7:42   ` Tobias Klauser
2015-04-27  7:48     ` Arnd Bergmann
2015-04-27  9:26       ` Tobias Klauser
2015-04-27  9:33         ` Arnd Bergmann
2015-04-28 11:19     ` Yoshinori Sato
2015-04-27  8:40   ` Arnd Bergmann
2015-04-28 11:31     ` Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 02/17] h8300: UAPI headers Yoshinori Sato
2015-04-27  8:43   ` Arnd Bergmann
2015-04-28  9:25     ` Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 03/17] h8300: Exception and Interrupt handling Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 04/17] h8300: kernel booting Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 05/17] h8300: process and signals Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 06/17] h8300: CPU depend helpers Yoshinori Sato
2015-04-27  8:54   ` Arnd Bergmann
2015-04-28  9:22     ` Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 07/17] h8300: miscellaneous functions Yoshinori Sato
2015-04-27  8:57   ` Arnd Bergmann
2015-04-28  8:54     ` Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 08/17] h8300: Memory management Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 09/17] h8300: library functions Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 10/17] h8300: Build scripts Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 11/17] h8300: clock driver Yoshinori Sato
2015-04-27  9:04   ` Arnd Bergmann
2015-04-28  9:43     ` Yoshinori Sato
2015-04-28 10:03       ` Geert Uytterhoeven
2015-04-28 17:40         ` Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 12/17] h8300: clocksource Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 13/17] h8300: configs Yoshinori Sato
2015-04-28  3:27   ` Guenter Roeck
2015-04-28  8:05     ` Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 14/17] serial: Add H8300 Yoshinori Sato
2015-04-29 16:47   ` [v9,14/17] " Guenter Roeck
2015-04-27  5:35 ` [PATCH v9 15/17] Add ELF machine Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 16/17] mksysmap: Add h8300 local symbol pattern Yoshinori Sato
2015-04-27  5:35 ` [PATCH v9 17/17] Add H8/300 entry Yoshinori Sato
2015-04-27  9:11 ` [PATCH v9 00/17] Re-introduce h8300 architecture Arnd Bergmann
2015-04-28  9:09   ` Yoshinori Sato
2015-04-28 13:22 ` Guenter Roeck
2015-04-28 17:25   ` Yoshinori Sato
2015-04-29  4:33     ` Guenter Roeck [this message]
2015-04-29  4:44       ` Guenter Roeck
2015-04-29  6:22       ` Yoshinori Sato
2015-04-29 13:24         ` Guenter Roeck
2015-04-29 17:07         ` Guenter Roeck
2015-04-30  3:50           ` Yoshinori Sato

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55405F08.7020508@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.