From: jason.wessel@windriver.com (Jason Wessel)
Subject: [ltt-dev] [UST PATCH 1/2] add mips support
Date: Tue, 26 Apr 2011 16:55:55 -0500 [thread overview]
Message-ID: <1303854956-2787-1-git-send-email-jason.wessel@windriver.com> (raw)
The recent changes to UST make it trivial to add MIPS support.
The trick for MIPS is that there are many different library formats
and the gcc 4.x compiler will correctly choose the default one so long
as the libust.ldscript.in does not not make a reference to the library
format.
Signed-off-by: Jason Wessel <jason.wessel at windriver.com>
---
Makefile.am | 2 +-
configure.ac | 1 +
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/Makefile.am b/Makefile.am
index 6957f07..9e16546 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -16,7 +16,7 @@ ldscripts_DATA = libust.so libust-initializer.o
CLEANFILES = $(ldscripts_DATA) ./tests/libust-initializer.Po
libust.so: libust.ldscript.in
- $(SED) -e "s@\@FORMAT\@@$(LIBFORMAT)@" < $< > $@
+ $(SED) -e $(if $(LIBFORMAT),"s@\@FORMAT\@@$(LIBFORMAT)@","s at .*\@FORMAT\@.*@@") < $< > $@
# It is very important to compile the initializer with PIC otherwise we
# may get obscure errors when linking to shared libraries.
diff --git a/configure.ac b/configure.ac
index bebc1ab..8ca32ff 100644
--- a/configure.ac
+++ b/configure.ac
@@ -109,6 +109,7 @@ changequote([,])dnl
s390) LIBFORMAT="elf32-s390" ;;
s390x) LIBFORMAT="elf64-s390" ;;
arm) LIBFORMAT="elf32-littlearm" ;;
+ mips*) LIBFORMAT="" ;;
*) AC_MSG_ERROR([unable to detect library format (unsupported architecture ($host_cpu)?)]) ;;
esac
AC_SUBST(LIBFORMAT)
--
1.7.1
next reply other threads:[~2011-04-26 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 21:55 Jason Wessel [this message]
2011-04-26 21:55 ` [ltt-dev] [UST PATCH 2/2] fork and malloc test fixes Jason Wessel
2011-04-27 14:23 ` Yannick Brosseau
2011-04-28 13:33 ` Nils Carlson
2011-04-28 13:33 ` [ltt-dev] [UST PATCH 1/2] add mips support Nils Carlson
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=1303854956-2787-1-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.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