All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: lftan@altera.com, waltergoossens@home.nl,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 3/8] linux-yocto: depend on libgcc for nios2
Date: Fri, 18 Sep 2015 03:48:30 +0200	[thread overview]
Message-ID: <201509180348.30142.marex@denx.de> (raw)
In-Reply-To: <B830C8CE-354B-428D-81E5-440EF548A557@gmail.com>

On Friday, September 18, 2015 at 03:43:50 AM, Khem Raj wrote:
> > On Sep 17, 2015, at 6:41 PM, Marek Vasut <marex@denx.de> wrote:
> > 
> > On Friday, September 18, 2015 at 03:40:11 AM, Khem Raj wrote:
> > 
> > Hi!
> > 
> >>> On Sep 17, 2015, at 7:31 AM, Marek Vasut <marex@denx.de> wrote:
> >>> 
> >>> Make nios2 kernel depend on libgcc.
> >>> 
> >>> In arch/nios2/Makefile, it adds LIBGCC to libs-y:
> >>> 
> >>> LIBGCC          := $(shell $(CC) $(KBUILD_CFLAGS)
> >>> -print-libgcc-file-name) libs-y          += $(LIBGCC)
> >>> 
> >>> In file Makefile in top directory, libs-y is assigned to to var
> >>> KBUILD_VMLINUX_MAIN. It uses script link-vmlinux.sh to link vmlinux.o,
> >>> and when execute function vmlinux_link() in link-vmlinux.sh,
> >>> KBUILD_VMLINUX_MAIN is passed to ${LD}.
> >>> 
> >>> If build without libgcc, the value of LIBGCC is just libgcc.a without
> >>> 
> >>> parent directory. linux-yocto fails to build:
> >>> |   LD      vmlinux.o
> >>> | 
> >>> | nios2-poky-linux-ld.bfd: cannot find libgcc.a: No such file or
> >>> | directory
> >>> 
> >>> Add libgcc to nios2 kernel dependency.
> >>> 
> >>> Signed-off-by: Marek Vasut <marex@denx.de>
> >>> ---
> >>> meta/recipes-kernel/linux/linux-yocto.inc | 4 ++++
> >>> 1 file changed, 4 insertions(+)
> >>> 
> >>> diff --git a/meta/recipes-kernel/linux/linux-yocto.inc
> >>> b/meta/recipes-kernel/linux/linux-yocto.inc index 3b41a61..81ffa24
> >>> 100644
> >>> --- a/meta/recipes-kernel/linux/linux-yocto.inc
> >>> +++ b/meta/recipes-kernel/linux/linux-yocto.inc
> >>> @@ -11,6 +11,10 @@ DEPENDS_append_aarch64 = " libgcc"
> >>> KERNEL_CC_append_aarch64 = " ${TOOLCHAIN_OPTIONS}"
> >>> KERNEL_LD_append_aarch64 = " ${TOOLCHAIN_OPTIONS}"
> >>> 
> >>> +DEPENDS_append_nios2 = " libgcc"
> >>> +KERNEL_CC_append_nios2 = " ${TOOLCHAIN_OPTIONS}"
> >>> +KERNEL_LD_append_nios2 = " ${TOOLCHAIN_OPTIONS}”
> >> 
> >> Please try bitbake virtual/kernel build from scratch with this change.
> > 
> > What do you mean, does it break anything or what should I expect ?
> 
> I am not sure if there is a race, with this dependency between libgcc and
> gcc-cross hopefully there is not but this will prove it.

Wouldn't arm64 explode in the same way then ? I'll set up the build shortly.

Best regards,
Marek Vasut


  reply	other threads:[~2015-09-18  1:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17 14:31 [PATCH 0/8] nios2 fixes Marek Vasut
2015-09-17 14:31 ` [PATCH 1/8] insane: Add nios2 support Marek Vasut
2015-09-17 14:31 ` [PATCH 2/8] kernel-arch: Add nios2 to valid archs Marek Vasut
2015-09-17 14:31 ` [PATCH 3/8] linux-yocto: depend on libgcc for nios2 Marek Vasut
2015-09-18  1:40   ` Khem Raj
2015-09-18  1:41     ` Marek Vasut
2015-09-18  1:43       ` Khem Raj
2015-09-18  1:48         ` Marek Vasut [this message]
2015-09-18  1:51           ` Khem Raj
2015-09-18  2:11             ` Marek Vasut
2015-09-18  2:28               ` Khem Raj
2015-09-17 14:31 ` [PATCH 4/8] openssl: Add nios2 configuration Marek Vasut
2015-09-17 14:31 ` [PATCH 5/8] siteinfo: Add nios2-linux Marek Vasut
2015-09-17 14:31 ` [PATCH 6/8] libtool: Fix nios2 support Marek Vasut
2015-09-17 14:31 ` [PATCH 7/8] pixman: Fix missing FE_DIVBYZERO on nios2 Marek Vasut
2015-09-17 14:31 ` [PATCH 8/8] libgpg-error: Add support for nios2 Marek Vasut
2015-09-18  1:41   ` Khem Raj
2015-09-18  1:53     ` Marek Vasut
2015-09-18  2:29       ` Khem Raj
2015-09-17 19:54 ` [PATCH 0/8] nios2 fixes Burton, Ross
2015-09-19 21:38   ` Marek Vasut
2015-09-18  1:44 ` Khem Raj
2015-09-18  1:47   ` Marek Vasut

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=201509180348.30142.marex@denx.de \
    --to=marex@denx.de \
    --cc=lftan@altera.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=waltergoossens@home.nl \
    /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.