From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0AEF1A04F5; Thu, 12 Dec 2019 17:05:21 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BBAD71BF95; Thu, 12 Dec 2019 17:05:20 +0100 (CET) Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) by dpdk.org (Postfix) with ESMTP id CDCAB1BF93 for ; Thu, 12 Dec 2019 17:05:19 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id B4A40748; Thu, 12 Dec 2019 11:05:18 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Thu, 12 Dec 2019 11:05:19 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=Lmps7dlaFLz0Ta5A3Ubhy6U0v5XoHKRD2jIqLq0q94c=; b=WSHruoX+l/YZ DKYC2nQvd2nPYRxwWrHq2OHUtGvN7+qPT1KYOAFKNGLVlnFH1tCDbESHfc4t3p4L 6wkJn82O7wPMh36v/STrMBkDTtEnTCi1Eht+GjI4F6Te5eOqezdtrEL4I0TBzbtI d9WokB89PGxG+SkK8RYC1Nx/USthETE= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=Lmps7dlaFLz0Ta5A3Ubhy6U0v5XoHKRD2jIqLq0q9 4c=; b=TtlKAML7cObG+fRGPedcIxD7p9KhjM/hfiBG99LA0XMQV5smJ8xQIfmn7 RMhg6sHbu/fKOPZsRuc0xfsTyHHf6UgWYPCrr8NIXqhBdRxoPIhdNBZnwQfVTVjs xIpQ16TE+pQjIkDNqPVpXnVXSU7WorJH8nNaE7Rwjb+jYs0MImHmm2yUIF96SJag YpXTqFXmVJMRMr/8U0g4BZj9Oq3nZ+axiDfHh60mKAd+jaiL5llfFn/mVwEH4pxe HPH1FJyEsEBZgoeGMyQcHK7oV3oEbCjuDogOXcwGfEzIj1zHqkrfIm/SUakwc62B Q6x0CZXZbhieDFWX1rZ79q5u1iJWA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeljedgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtqhertddttddunecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpehllhhvmhdrohhrghenucfkphepjeejrddufeegrddvtdefrddukeegnecu rfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 8FA5730600DC; Thu, 12 Dec 2019 11:05:17 -0500 (EST) From: Thomas Monjalon To: Rafael =?ISO-8859-1?Q?=C1vila_de_Esp=EDndola?= Cc: dev@dpdk.org Date: Thu, 12 Dec 2019 17:05:16 +0100 Message-ID: <10040104.KzNOl4Vb3s@xps> In-Reply-To: <20191025012013.118919-1-espindola@scylladb.com> References: <20191025012013.118919-1-espindola@scylladb.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" Subject: Re: [dpdk-dev] [PATCH] Don't combine '-r' and '--export-dynamic' linker options X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 25/10/2019 03:20, Rafael =C1vila de Esp=EDndola: > Running ld with '-r' switches the linker to a very special mode where > some other linker options don't make sense. >=20 > 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. >=20 > When given both options it looks like the gnu linker just ignores > '--export-dynamic'. >=20 > 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=3D43552). Current (git) version > of lld now issues an error. >=20 > This patch drops $(LDFLAGS) when using -r. With this patch I can build > dpdk with lld. [...] > -PMDINFO_LD =3D $(CROSS)ld $(LDFLAGS) -r -o $@.o $@.pmd.o $@ > +PMDINFO_LD =3D $(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? And what about meson? Is there some similar issue?