public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Kai Kang <kai.kang@windriver.com>
To: <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: [PATCH 01/19] linux-yocto: depend on libgcc for aarch64
Date: Thu, 18 Dec 2014 16:50:57 +0800	[thread overview]
Message-ID: <5bf74cfd004ffdc09d42a0c0bb3cf4881e0fc634.1418885577.git.kai.kang@windriver.com> (raw)
In-Reply-To: <cover.1418885577.git.kai.kang@windriver.com>

Make aarch aarch64 kernel depend on libgcc.

In arch/arm64/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
| aarch64-poky-linux-ld.bfd: cannot find libgcc.a: No such file or directory

Add libgcc to aarch64 kernel dependency.

Signed-off-by: Kai Kang <kai.kang@windriver.com>
---
 meta/recipes-kernel/linux/linux-yocto.inc | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/recipes-kernel/linux/linux-yocto.inc b/meta/recipes-kernel/linux/linux-yocto.inc
index 4ed3188..9018985 100644
--- a/meta/recipes-kernel/linux/linux-yocto.inc
+++ b/meta/recipes-kernel/linux/linux-yocto.inc
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"
 INC_PR = "r4"
 
 DEPENDS += "xz-native bc-native"
+DEPENDS_append_aarch64 = " libgcc"
 
 # A KMACHINE is the mapping of a yocto $MACHINE to what is built
 # by the kernel. This is typically the branch that should be built,
-- 
1.9.1



  reply	other threads:[~2014-12-18  8:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-18  8:50 [PATCH 00/19] V3: Add machine qemuarm64 Kai Kang
2014-12-18  8:50 ` Kai Kang [this message]
2015-01-01  1:31   ` [PATCH 01/19] linux-yocto: depend on libgcc for aarch64 Khem Raj
2014-12-18  8:50 ` [PATCH 02/19] Add machine qemuarm64 Kai Kang
2014-12-18  8:50 ` [PATCH 03/19] siteinfo: account for 32 and 64 bit arm Kai Kang
2014-12-18  8:51 ` [PATCH 04/19] libc-package.bbclass: add aarch64 target to locale_arch_options Kai Kang
2014-12-18  8:51 ` [PATCH 05/19] glibc-locale.inc: add aarch64 to BINARY_LOCALE_ARCHES Kai Kang
2014-12-18  8:51 ` [PATCH 06/19] libatomics-ops: add aarch64 target iniitial support Kai Kang
2014-12-18  8:51 ` [PATCH 07/19] qt4: add aarch64 support Kai Kang
2014-12-18  8:51 ` [PATCH 08/19] libpng 1.6.13: fix build for aarch64 Kai Kang
2014-12-22  9:41   ` Richard Purdie
2014-12-22 10:57     ` Richard Purdie
2014-12-18  8:51 ` [PATCH 09/19] sysprof: disable " Kai Kang
2014-12-18  8:51 ` [PATCH 10/19] lttng: recognize aarch64 Kai Kang
2014-12-18  8:51 ` [PATCH 11/19] guile: allow compilation for aarch64 Kai Kang
2015-01-01  1:25   ` Khem Raj
2014-12-18  8:51 ` [PATCH 12/19] libunwind: add aarch64 support Kai Kang
2014-12-18  8:51 ` [PATCH 13/19] runqemu: add qemuarm64 support Kai Kang
2015-01-01  1:27   ` Khem Raj
2015-01-04  2:38     ` Kang Kai
2014-12-18  8:51 ` [PATCH 14/19] kexec-tools: add aarch64 support Kai Kang
2014-12-18  8:51 ` [PATCH 15/19] packagegroup-core-tools-profile: remove sysprof for aarch64 Kai Kang
2014-12-18  8:51 ` [PATCH 16/19] gcc: Disable aarch64 multilib options Kai Kang
2014-12-18  8:51 ` [PATCH 17/19] glibc-package: aarch64 enable symlink for ABI compliance Kai Kang
2014-12-18  8:51 ` [PATCH 18/19] aarch-arm64: Update tune files Kai Kang
2015-01-01  1:54   ` Khem Raj
2014-12-18  8:51 ` [PATCH 19/19] linux-yocto: Fixup linux-yocto for aarch64 Kai Kang

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=5bf74cfd004ffdc09d42a0c0bb3cf4881e0fc634.1418885577.git.kai.kang@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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