From: Gustavo Zacarias <gustavo.zacarias@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] openssl: change sed expression delimiter
Date: Thu, 24 Sep 2015 07:40:47 -0300 [thread overview]
Message-ID: <5603D32F.4090200@free-electrons.com> (raw)
In-Reply-To: <20150924115817.51306b11@free-electrons.com>
On 24/09/15 06:58, Thomas Petazzoni wrote:
> Actually, I am wondering of -Wl,-rpath,/lib:/usr/lib is the legal of
> doing things, and if it shouldn't be -Wl,-rpath,/lib
> -Wl,-rpath,/usr/lib. The first solution makes the assumption that ':'
> is the RPATH separator, while the latter does not make such assumption.
Hi, they're equivalent, if you build a dummy C program:
gcc -Wl,-rpath,/lib -Wl,-rpath,/usr/lib -o x1 x.c
And:
gcc -Wl,-rpath,/lib:/usr/lib -o x2 x.c
They result in the same RPATH entry in the binary (actually even the
same sha256sum).
There are other gcc options that might go bad with : like using
-std=iso9899:2011 instead of -std=c11.
With # only -### comes to mind which would hardly be useful in a real
project.
Regards.
prev parent reply other threads:[~2015-09-24 10:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 21:27 [Buildroot] [git commit] openssl: change sed expression delimiter Peter Korsgaard
2015-09-24 9:58 ` Thomas Petazzoni
2015-09-24 10:40 ` Gustavo Zacarias [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=5603D32F.4090200@free-electrons.com \
--to=gustavo.zacarias@free-electrons.com \
--cc=buildroot@busybox.net \
/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.