public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] [PATCH v2 2/4] kernel-build.eclass: Build logic for dist-kernels
Date: Mon, 6 Jan 2020 12:43:04 -0500	[thread overview]
Message-ID: <CAJ0EP40Rf2LirCmwjjB4Vqbu2Snm5irnXjM_B2byM8RBcqhQOw@mail.gmail.com> (raw)
In-Reply-To: <20200105062741.82357-2-mgorny@gentoo.org>

On Sun, Jan 5, 2020 at 1:27 AM Michał Górny <mgorny@gentoo.org> wrote:
> +# @FUNCTION: kernel-build_src_configure
> +# @DESCRIPTION:
> +# Prepare the toolchain for building the kernel, get the default .config
> +# or restore savedconfig, and get build tree configured for modprep.
> +kernel-build_src_configure() {
> +       debug-print-function ${FUNCNAME} "${@}"
> +
> +       # force ld.bfd if we can find it easily
> +       local LD="$(tc-getLD)"
> +       if type -P "${LD}.bfd" &>/dev/null; then
> +               LD+=.bfd
> +       fi

Is there some reason not to use the tc-ld-disable-gold function?


  reply	other threads:[~2020-01-06 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05  6:27 [gentoo-dev] [PATCH v2 1/4] kernel-install.eclass: Install logic for dist-kernels Michał Górny
2020-01-05  6:27 ` [gentoo-dev] [PATCH v2 2/4] kernel-build.eclass: Build " Michał Górny
2020-01-06 17:43   ` Mike Gilbert [this message]
2020-01-06 17:54     ` Michał Górny
2020-01-06 18:07       ` Mike Gilbert
2020-01-06 18:13         ` Michał Górny
2020-01-05  6:27 ` [gentoo-dev] [PATCH v2 3/4] sys-kernel/vanilla-kernel: Migrate to kernel-build.eclass Michał Górny
2020-01-05  6:27 ` [gentoo-dev] [PATCH v2 4/4] sys-kernel/vanilla-kernel-bin: Migrate to kernel-install.eclass Michał Górny
2020-01-05  7:30 ` [gentoo-dev] [PATCH v2 1/4] kernel-install.eclass: Install logic for dist-kernels Robin H. Johnson
2020-01-07  6:11   ` Michał Górny

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=CAJ0EP40Rf2LirCmwjjB4Vqbu2Snm5irnXjM_B2byM8RBcqhQOw@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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