From: Ray Kinsella <mdr@ashroe.eu>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] Don't combine '-r' and '--export-dynamic' linker options
Date: Fri, 13 Dec 2019 10:07:44 +0000 [thread overview]
Message-ID: <033d4ee5-6ddf-5033-cb65-5a8d83070b55@ashroe.eu> (raw)
In-Reply-To: <10040104.KzNOl4Vb3s@xps>
On 12/12/2019 16:05, Thomas Monjalon wrote:
> 25/10/2019 03:20, Rafael Ávila de Espíndola:
>> Running ld with '-r' switches the linker to a very special mode where
>> some other linker options don't make sense.
>>
>> In particular, '--export-dynamic' normally requires that all global
>> symbols be included in the dynamic symbol table, but a .o file doesn't
>> even have a dynamic symbol table.
>>
>> When given both options it looks like the gnu linker just ignores
>> '--export-dynamic'.
>>
>> Unfortunately some versions of lld (https://lld.llvm.org/) have a bug
>> that causes it to try to create a dynamic symbol table in the output
>> .o file and ends up corrupting it
>> (https://bugs.llvm.org/show_bug.cgi?id=43552). Current (git) version
>> of lld now issues an error.
>>
>> This patch drops $(LDFLAGS) when using -r. With this patch I can build
>> dpdk with lld.
> [...]
>> -PMDINFO_LD = $(CROSS)ld $(LDFLAGS) -r -o $@.o $@.pmd.o $@
>> +PMDINFO_LD = $(CROSS)ld -r -o $@.o $@.pmd.o $@
>
> Dealing with compiler bugs is really annoying.
> I'm afraid removing LDFLAGS may break in some environments.
> Could you just filter-out some incompatible options?
Right, detect that LLD is the linker and change LDFLAGS accordingly.
Painful, but the right approach.
>
> And what about meson? Is there some similar issue?
>
>
>
prev parent reply other threads:[~2019-12-13 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 1:20 Rafael Ávila de Espíndola
2019-12-06 22:51 ` Rafael Avila de Espindola
2019-12-12 16:05 ` Thomas Monjalon
2019-12-12 17:44 ` Rafael Avila de Espindola
2019-12-13 10:07 ` Ray Kinsella [this message]
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=033d4ee5-6ddf-5033-cb65-5a8d83070b55@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).