All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Rasmus Villemoes <rasmus.villemoes@prevas.dk>,
	OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: glibc and LDFLAGS
Date: Sat, 18 Jan 2020 23:32:06 +0000	[thread overview]
Message-ID: <4e7244df21e0c47712976ad72bc53aab51236724.camel@linuxfoundation.org> (raw)
In-Reply-To: <2aedfee9-2985-e246-6a8c-7ec673039704@prevas.dk>

On Sat, 2020-01-18 at 22:25 +0000, Rasmus Villemoes wrote:
> I've added a custom setting to TARGET_LDFLAGS, but then I noticed
> that
> the glibc build ignored that. The glibc do_compile did
> 
>  LDFLAGS = ""
> 
> for a very long time, with the explanation that "# -Wl,-rpath-link
> <staging>/lib in LDFLAGS can cause breakage if another glibc is in
> staging". Is that actually still relevant with per-recipe staging?

It is obsolete now, correct.

> If that is indeed moot, can we do
> 
>          CPPFLAGS="" oe_runconf
>  }
> 
> +LDFLAGS += "-fuse-ld=bfd"

Its worth a try...

Cheers,

Richard



  reply	other threads:[~2020-01-18 23:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-18 22:25 glibc and LDFLAGS Rasmus Villemoes
2020-01-18 23:32 ` Richard Purdie [this message]
2020-01-20  7:28   ` [PATCH] glibc: don't ignore global LDFLAGS settings Rasmus Villemoes
2020-01-20  9:23     ` [PATCH v2] " Rasmus Villemoes
2020-01-20 15:42       ` Khem Raj
2020-01-20 15:53         ` Rasmus Villemoes
2020-02-03 18:55         ` Rasmus Villemoes
2020-01-20  7:32   ` ✗ patchtest: failure for " Patchwork

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=4e7244df21e0c47712976ad72bc53aab51236724.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rasmus.villemoes@prevas.dk \
    /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.