From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v2 2/4] kernel-build.eclass: Build logic for dist-kernels
Date: Mon, 06 Jan 2020 19:13:48 +0100 [thread overview]
Message-ID: <760bc1e5f08a133ae661fadcb5f46e7e68ac3754.camel@gentoo.org> (raw)
In-Reply-To: <CAJ0EP433awN4PtjDumiGVtybJ-=m19iku6KCLqUmfY87ZP+Seg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1579 bytes --]
On Mon, 2020-01-06 at 13:07 -0500, Mike Gilbert wrote:
> On Mon, Jan 6, 2020 at 12:54 PM Michał Górny <mgorny@gentoo.org> wrote:
> > On Mon, 2020-01-06 at 12:43 -0500, Mike Gilbert wrote:
> > > 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?
> > >
> >
> > Yes. As the name says, it covers gold usage only and not lld.
>
> It might be a good idea to copy this logic to handle multi-word LD values.
>
> https://gitweb.gentoo.org/repo/gentoo.git/tree/eclass/toolchain-funcs.eclass#n498
>
> Or, a nicer alternative would be to refactor tc-ld-disable-gold into 2
> functions: move most of the logic into a new function
> "tc-ld-force-bfd", and update tc-ld-disable-gold to call the former if
> tc-ld-is-gold is true. I can write a patch for that if you agree.
>
Sure, that sounds like a good idea. Please also replace which(1) with
'type' while at it.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2020-01-06 18:13 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
2020-01-06 17:54 ` Michał Górny
2020-01-06 18:07 ` Mike Gilbert
2020-01-06 18:13 ` Michał Górny [this message]
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=760bc1e5f08a133ae661fadcb5f46e7e68ac3754.camel@gentoo.org \
--to=mgorny@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