linux-arch.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yoshinori Sato <ysato@users.sourceforge.jp>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH v10 00/19] Re-introduce h8300 architecture
Date: Thu, 07 May 2015 13:22:36 +0900	[thread overview]
Message-ID: <87d22dxbhv.wl-ysato@users.sourceforge.jp> (raw)
In-Reply-To: <20150505022700.GA26383@roeck-us.net>

At Mon, 4 May 2015 19:27:00 -0700,
Guenter Roeck wrote:
> 
> On Mon, May 04, 2015 at 07:41:43PM +0900, Yoshinori Sato wrote:
> > Hello.
> > I will re-introducing h8300.
> > 
> 
> Hi,
> 
> With "make ARCH=h8300 edosk2674_defconfig; make ARCH=h8300",
> I see the following build error:
> 
> scripts/Makefile.build:44: arch/h8300/boot/dtb/Makefile: No such file or directory
> make[1]: *** No rule to make target 'arch/h8300/boot/dtb/Makefile'.  Stop.
> 
> After fixing this up with
> 
> diff --git a/arch/h8300/Makefile b/arch/h8300/Makefile
> index c2b24c9..f547870 100644
> --- a/arch/h8300/Makefile
> +++ b/arch/h8300/Makefile
> @@ -26,7 +26,7 @@ CROSS_COMPILE := h8300-unknown-linux-
> 
>  core-y += arch/$(ARCH)/kernel/ arch/$(ARCH)/mm/ arch/h8300/boot/dts/
>  ifneq '$(CONFIG_H8300_BUILTIN_DTB)' '""'
> -core-y += arch/h8300/boot/dtb/
> +core-y += arch/h8300/boot/dts/
>  endif
>      
>  libs-y += arch/$(ARCH)/lib/
> 
> I get
> 
> arch/h8300/boot/dts/built-in.o: In function `__dtb_edosk2674_end':
> (.dtb.init.rodata+0x8fb): multiple definition of `__dtb_edosk2674_end'
> arch/h8300/boot/dts/built-in.o:(.dtb.init.rodata+0x8fb): first defined here
> arch/h8300/boot/dts/built-in.o: In function `__dtb_edosk2674_begin':
> (.dtb.init.rodata+0x0): multiple definition of `__dtb_edosk2674_begin'
> arch/h8300/boot/dts/built-in.o:(.dtb.init.rodata+0x0): first defined here
> Makefile:932: recipe for target 'vmlinux' failed
> 
> This is with compiler and binutils built as you had provided earlier.
> 
> ---
> 
> Other configurations fail to build with
> 
> h8300-unknown-linux-ld: cannot find arch/h8300/boot/dts/built-in.o: No such file or directory
> Makefile:932: recipe for target 'vmlinux' failed
> make: *** [vmlinux] Error 1
> 
> ---
> 
> Switching from edosk2674_defconfig to h8300h-sim_defconfig without "make
> mrproper" results in:
> 
> h8300-unknown-linux-ld: h8300s architecture of input file
> `arch/h8300/boot/dts/built-in.o' is incompatible with h8300h output
> 
> ---
> 
> Results are with git://git.sourceforge.jp/gitroot/uclinux-h8/linux.git,
> branch h8300.
> 
> Guenter

Thanks testing.
It looks Makefile and defconfig problem.

I'll fix next release.

-- 
Yoshinori Sato
<ysato@users.sourceforge.jp>

      reply	other threads:[~2015-05-07  4:22 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 10:41 [PATCH v10 00/19] Re-introduce h8300 architecture Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 01/19] MAINTENRS: Add h8300 Yoshinori Sato
2015-05-04 10:41   ` Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 02/19] Add H8/300 ELF Machine Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 03/19] mksysmap: Avoid h8300's local symbol Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 04/19] sh-sci: Add H8/300 SCI Yoshinori Sato
2015-05-04 13:58   ` Geert Uytterhoeven
2015-05-04 10:41 ` [PATCH v10 05/19] Add common asm-offsets.h Yoshinori Sato
2015-05-04 10:41   ` Yoshinori Sato
2015-05-04 14:46   ` Arnd Bergmann
2015-05-07  4:24     ` Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 06/19] h8300: Assembly headers Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 07/19] h8300: UAPI assembly headers Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 08/19] h8300: Exception and Interrupt handling Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 09/19] h8300: kernel booting Yoshinori Sato
2015-05-04 10:41   ` Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 10/19] h8300: process and signals Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 11/19] h8300: CPU depend helpers Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 12/19] h8300: miscellaneous functions Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 13/19] h8300: Memory management Yoshinori Sato
2015-05-04 10:41   ` Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 14/19] h8300: Library functions Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 15/19] h8300: Build scripts Yoshinori Sato
2015-05-04 10:41 ` [PATCH v10 16/19] h8300: clock driver Yoshinori Sato
2015-05-04 10:42 ` [PATCH v10 17/19] h8300: clocksource Yoshinori Sato
2015-05-04 10:42   ` Yoshinori Sato
2015-05-04 10:42 ` [PATCH v10 18/19] h8300: configs Yoshinori Sato
2015-05-04 10:42 ` [PATCH v10 19/19] h8300: devicetree source Yoshinori Sato
     [not found]   ` <1430736122-20929-21-git-send-email-ysato-Rn4VEauK+AKRv+LV9MX5uooqe+aC9MnS@public.gmane.org>
2015-05-04 12:40     ` Geert Uytterhoeven
2015-05-04 12:40       ` Geert Uytterhoeven
2015-05-04 15:09   ` Arnd Bergmann
2015-05-07  4:47     ` Yoshinori Sato
2015-05-04 15:28 ` [PATCH v10 00/19] Re-introduce h8300 architecture Arnd Bergmann
2015-05-05  2:27 ` Guenter Roeck
2015-05-07  4:22   ` Yoshinori Sato [this message]

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=87d22dxbhv.wl-ysato@users.sourceforge.jp \
    --to=ysato@users.sourceforge.jp \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).