From: Mattia Dongili <malattia@linux.it>
To: Ritesh Raj Sarraf <rrs@debian.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML static linking and embedded library
Date: Fri, 6 Apr 2012 07:21:01 +0900 [thread overview]
Message-ID: <20120405222100.GA6372@kamineko.org> (raw)
In-Reply-To: <4F7B53DC.1040602@debian.org>
On Wed, Apr 04, 2012 at 01:17:40AM +0530, Ritesh Raj Sarraf wrote:
> On Tuesday 03 April 2012 10:35 PM, richard -rw- weinberger wrote:
> > Solving the first issue is straight forward.
> > For the second one I've to think a bit why Jeff took the current
> > static linking approach.
> >
> > Expect patches for both issues in 3.5. :-)
>
> Thanks. Can you prepare the patch?
>
> We are going to ship Debian 7 (Wheezy) with kernel v3.2. Based on what
> you prepare, I will backport it.
the rpath one should be as simple as the attached one but honestly I
kind of recall there was a reason for RPATH to be defined. Maybe that
reason is no longer valid though...
---
commit ea13ff7608ea92df6ffa41e1124e5d3e6d7984fb
Author: Mattia Dongili <malattia@linux.it>
Date: Fri Apr 6 07:18:17 2012 +0900
Remove unnecessary RPATH definition
Signed-off-by: Mattia Dongili <malattia@linux.it>
diff --git a/arch/um/Makefile b/arch/um/Makefile
index 55c0661..b836776 100644
--- a/arch/um/Makefile
+++ b/arch/um/Makefile
@@ -105,7 +105,6 @@ archheaders:
archprepare: include/generated/user_constants.h
LINK-$(CONFIG_LD_SCRIPT_STATIC) += -static
-LINK-$(CONFIG_LD_SCRIPT_DYN) += -Wl,-rpath,/lib
CFLAGS_NO_HARDENING := $(call cc-option, -fno-PIC,) $(call cc-option, -fno-pic,) \
$(call cc-option, -fno-stack-protector,) \
diff --git a/arch/x86/Makefile.um b/arch/x86/Makefile.um
index 4be406a..8368350 100644
--- a/arch/x86/Makefile.um
+++ b/arch/x86/Makefile.um
@@ -47,9 +47,6 @@ KBUILD_CPPFLAGS += -m64
ELF_ARCH := i386:x86-64
ELF_FORMAT := elf64-x86-64
-# Not on all 64-bit distros /lib is a symlink to /lib64. PLD is an example.
-
-LINK-$(CONFIG_LD_SCRIPT_DYN) += -Wl,-rpath,/lib64
LINK-y += -m64
# Do unit-at-a-time unconditionally on x86_64, following the host
--
mattia
:wq!
------------------------------------------------------------------------------
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
http://p.sf.net/sfu/Boundary-d2dvs2
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2012-04-05 22:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1SEjI8-0007kU-RE@franck.debian.org>
2012-04-03 13:26 ` [uml-devel] UML static linking and embedded library Ritesh Raj Sarraf
2012-04-03 17:05 ` richard -rw- weinberger
2012-04-03 19:47 ` Ritesh Raj Sarraf
2012-04-05 22:21 ` Mattia Dongili [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=20120405222100.GA6372@kamineko.org \
--to=malattia@linux.it \
--cc=rrs@debian.org \
--cc=user-mode-linux-devel@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox