From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jay Shah <jay.shah1@rockwellcollins.com>
Cc: netfilter-devel@vger.kernel.org,
Yogesh Prasad <yogesh.prasad@rockwellcollins.com>,
Matt Weber <matthew.weber@rockwellcollins.com>
Subject: Re: [PATCH 1/1] iptables: patch to correct linker flag sequence
Date: Mon, 4 Dec 2017 11:18:39 +0100 [thread overview]
Message-ID: <20171204101839.GA13724@salvia> (raw)
In-Reply-To: <1511935854-13005-1-git-send-email-jay.shah1@rockwellcollins.com>
On Wed, Nov 29, 2017 at 12:10:54AM -0600, Jay Shah wrote:
> From: Yogesh Prasad <yogesh.prasad@rockwellcollins.com>
>
> Description
> This patch will correct the sequence of -pie and -shared options.
> When used together, -pie should be provided to the linker before
> -shared. If -pie is provided after -shared, the linker throws an
> error shown below as example.
>
> -------------------------------------------------------------------------
> /host/lib/gcc/powerpc-buildroot-linux-gnu/6.4.0/../../../..
> /powerpc-buildroot-linux-gnu/bin/ld: BFD (GNU Binutils) 2.28.1
> assertion fail elf32-ppc.c:8923
> collect2: error: ld returned 1 exit status
> + ./libxt_SYNPROXY.man
> make[4]: *** [libxt_TCPOPTSTRIP.so] Error 1
> + ./libip6t_mh.man
> /host/powerpc-buildroot-linux-gnu/sysroot/usr/lib/Scrt1.o:(.data+0x4):
> undefined reference to `main'
> /host/lib/gcc/powerpc-buildroot-linux-gnu + ./libxt_TCPMSS.man
> /6.4.0/../../../../powerpc-buildroot-linux-gnu/bin/ld:
> BFD (GNU Binutils) 2.28.1 assertion fail elf32-ppc.c:8923
> collect2: error: ld returned 1 exit status
> -------------------------------------------------------------------------
Applied.
Out of curiosity: Does it say anywhere that the options need to be in
a specific order, eg. documentation.
prev parent reply other threads:[~2017-12-04 10:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 6:10 [PATCH 1/1] iptables: patch to correct linker flag sequence Jay Shah
2017-12-04 10:18 ` Pablo Neira Ayuso [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=20171204101839.GA13724@salvia \
--to=pablo@netfilter.org \
--cc=jay.shah1@rockwellcollins.com \
--cc=matthew.weber@rockwellcollins.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=yogesh.prasad@rockwellcollins.com \
/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).