All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Weber <matthew.weber@rockwellcollins.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 07/11] package/busybox: fix applets runtime issue when building with clang cross-compiler
Date: Fri, 6 Sep 2019 22:11:44 -0500	[thread overview]
Message-ID: <CANQCQpYDyAcV6HkabqzVOBVPAgs9GA=ZtfronrAV=r=nt9LYVQ@mail.gmail.com> (raw)
In-Reply-To: <20190906090947.5476-8-romain.naour@smile.fr>

Romain,

On Fri, Sep 6, 2019 at 4:10 AM Romain Naour <romain.naour@smile.fr> wrote:
>
> Apply a patch contributed by Luis Marques on the Busybox mailing list [1]
> fixing a runtime issue (segfault) when busybox is compiled by Clang.
>
> The patch disable the compiler optimizations for Clang/LLVM only.
>
> Without this patch, busybox segfault with several applets
> (login on aarch64 using Clang 8.0.1, init on x86_64 using Clang 9.0.0rc3)
>
> [1] http://lists.busybox.net/pipermail/busybox/2019-June/087337.html
>

Got a "crtbegin.o no such file or directory" error when I setup a
build using master with qemu_aarch64_virt_defconfig (updated for
prebuilt external toolchain and enabling clang as cross-compiler).
https://paste.ubuntu.com/p/wxrmVTGVvp/

From your comment earlier on irc that you tested with 9.0.1 (x86_64
and aarch64), I wonder if this error is a difference between building
with clang 8.0.1 and 9.

I was able to build compiler-rt & libfuzzer with your series applied
and pass a runtime test (system still cross compiled with gcc but
using "[01/11] package/clang: help host-clang to find our external
toolchain" to find the sysroot).  This was instead of using the -B
option when building libfuzzer as part of the runtime test.

Matt

  reply	other threads:[~2019-09-07  3:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-06  9:09 [Buildroot] [PATCH 00/11] Add the support for Clang cross-compiler Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 01/11] package/clang: help host-clang to find our external toolchain Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 02/11] package/llvm: add the version major variable Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 03/11] package/clang: " Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 04/11] package/clang: install a toolchain-wrapper for the host clang cross-compiler Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 05/11] linux: override CC for the case CC is not GCC Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 06/11] package/meson: use TARGET_{CC, CXX} instead of TARGET_CROSS Romain Naour
2019-09-06 15:58   ` Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 07/11] package/busybox: fix applets runtime issue when building with clang cross-compiler Romain Naour
2019-09-07  3:11   ` Matthew Weber [this message]
2019-09-07  3:17     ` Matthew Weber
2019-09-07  8:02     ` Romain Naour
2019-09-09 13:49       ` [Buildroot] [External] " Matthew Weber
2019-09-06  9:09 ` [Buildroot] [PATCH 08/11] package/clang: add a host entry for clang Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 09/11] core: allow to use Clang as cross-compiler Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 10/11] toolchain: add a warning when Clang is used " Romain Naour
2019-09-06  9:09 ` [Buildroot] [PATCH 11/11] linux: don't set -Wno-attribute-alias flag " Romain Naour

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='CANQCQpYDyAcV6HkabqzVOBVPAgs9GA=ZtfronrAV=r=nt9LYVQ@mail.gmail.com' \
    --to=matthew.weber@rockwellcollins.com \
    --cc=buildroot@busybox.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 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.